...
This value defines an incoming mailbox Address that must be found from the recipients of the email in order to be processed by JEMH .
If left unspecified then JEMH will not know your Mailbox to address and will not filter from being added to the issue, which can cause mail loops.
...
in order to avoid mail loops (see How to prevent Mail Loops
...
). If left unspecified this will mean that all emails will be processed even if they do not contain a Catch Email Address.
JEMH can also use Project Mapping Domain Rules for the purposes of identifying inbound mailbox addresses - it does not need to be double entered as a CatchEmail Address also (How Catchemail mailbox addresses are identified).
| Info |
|---|
Catchemail address can be a plain address (user@domain.com) or a regular expression, we have a bootstrapping page (Regex Bootcamp ) with some examples. |
| Note |
|---|
Catchemail addresses must not match Profile > Notification > Forward User/email as this causes a mail loop. As of JEMH v.4.2.11., entering a match will result in an edit time error: |
...
Project Mapping Domain Rules (addressee matches)
| Status | ||||
|---|---|---|---|---|
|
Historically, the only way to identify a mailbox Address was through the Profile > Email > CatchEmail Address field shown here. JEMH will automatically use all Domain Rule addressees as Catchemail addresses, the benefit of this is that data doesn’t need to be entered twice.
...
This means that Catchemails become optional to be defined when Domain Rules are present with addressee values.
| Info |
|---|
Catchemail address can be a plain address (user@domain.com) or a regular expression, we have a bootstrapping page (Regex Bootcamp ) with some examples. |
| Note |
|---|
Catchemail addresses must not match Profile > Notification > Forward User/email as this causes a mail loop. As of JEMH v.4.2.11., entering a match will result in an edit time error: |
...
Catch Email Headers
CSV list of Email Headers that JEMH should check for a Catch Email Address within.
...