Jira sends emails that result in bounces and it does not deal cleanly with them

We see the following pattern in On Demand:

An email is sent to JIRA which JIRA is not able to process because the username is not on the system. This is typically due to a mistyped email address in the admin Gui, a message from an autoreply or other automata to JIRA.

JIRA then replies to that email with a notification that the user is not in the system. When this reply notification hits the On Demand external MX servers, a delivery attempt is made and this fails (eg, if the message was from postmaster@ and the demote system is misconfigured and does not accept postmaster email). This email then bounces and JIRA does not deal with the bounce, leaving it in the mailbox, or worse it generates another notification causing a mail loop.

Suggested Resolutions:

• Have JIRA only email an invalid address once
• Have JIRA set a hashed reply to address to monitor the source of bounces and use it to tie it back to the sent email and disable the user/notify the admin.
  • Note, this will require work from Hosted Infrastructure in order to support