Email Selection

Summary

This section is used to configure the Operating Mode of the Profile, the Catch Email Addresses that need at least one needs to match and the Email Headers that needs to be checked for a Catch Email Address.

Configuration Options

Operating Mode

This defines how the Profile will operate. Whether it will only create issues, will only comment on issues or both. The Current options are:

  • Create

  • Comment

  • Create and Comment

Catch Email Address

This value defines an incoming mailbox Address that must be found from the recipients of the email in order to be processed by JEMH.

Project Mapping Domain Rules (addressee matches)

since 4.1.12

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.

Notes

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:

Catchemail address can be a plain address (user@domain.com) or a regular expression, we have a bootstrapping page (https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/1148092417 ) with some examples.

image-20240613-133205.png

Catch Email Headers

CSV list of Email Headers that JEMH should check for a Catch Email Address within.

This is useful when you receive emails through BCC as the address would not appear in the To/Cc/Bcc headers, It may be present within the Delivered-To header or a system dependant header. If so then add that header so that the email can be processed.