Table of Contents |
---|
Info |
---|
In order to support multiple addressees from one mailbox, various strategies can be used (a) gmail supports mailbox Aliases (the Alias address is retained as a Delivered-To header), (b) o365 supports Aliases but sadly doesn"t yet retain it, (c) you may use a mailbox such as Postfix that supports "all" recipients in a subdomain to be retreivable through one account (eg tickets.yourco.net). From JEMH v4.1.12 (Jira9+) the _addressee_ values also act as catch email addresses and do not require duplicates in Profile > Email > Catch Email Address. Since JEMH v4.2.12, Domain rule addressees must not match Forward Users/emails |
Summary
This rule checks the sender or recipient addresses of an email for a match against the user-defined value. This value is regular expression capable, meaning that a pattern can be defined instead to allow matches to many different addresses.
...
A CSV list of Regular expressions that is used to match against the Sender or the Addressee (CatchEmail).
Info |
---|
From JEMH v4.1.12 (Jira9+) the addressee values also act as catch email addresses and do not require duplicates in Profile > Email > Catch Email Address. |
Catch email to match (Mailbox/sender)
...
Info |
---|
Note: Domain rules, which are matched against mailbox catchemail addressee(s), must not match Profile > Notifications > Forward User/email as this causes a mail loop. As of JEMH v4.2.12, entering a match will result in an edit time error: |
...
Multiple addressees from one mailbox
In order to support multiple addressees from one mailbox, various strategies can be used (a) gmail supports mailbox Aliases (the Alias address is retained as a Delivered-To header), (b) o365 supports Aliases but sadly doesn't yet retain it, (c) you may use a mailbox such as Postfix that supports "all" recipients in a subdomain to be retrievable through one account (eg tickets.yourco.net).