Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

Currently, JEMHC does not prevent the Forward Email being set if it matches against the catch email address.

Jira Legacy
serverSystem

...

Jira
serverId31e1f342-5dce-3979-a43c-85899d565476
keyJEMHC-2639

When an inbound mail fails to be processed, a forward email can be sent to the ‘Forward User Email Addresses'. If any of the email addresses listed match against the 'Catch Email Addresses’, you will see an advisory in your Profile similar to the image below:

Image Modified

Why your Forward user email address(es) should not match the catch email address

...

The error shown in the auditing report when the forward user email address matches a catch email is similar to the image shown below:

Image Modified

To prevent this, we are forced to not send the forward notification email, whilst the original mail that caused the processing error is left unprocessed in the inbound source mailbox. (This can block the mail handler, requiring a manual release - at present, this solution is not perfect, but the thought process is this scenario is less problematic than a mail loop continuously polling, processing and sending error messages to the same address.)

...

Prior to

Jira Legacy
serverSystem JIRAJira
serverId31e1f342-5dce-3979-a43c-85899d565476
keyJEMHC-2639
, setting the forward user email address to match against the catch email address was possible. If this is the case, you will need to change your forward user email address, or change your catch email address/catch email regex.(If your catch email address is using regex to match, you may also consider filtering the regex match further - this will only work if the catch email is not a direct match to a forward user email address supplied).

...