This would help enterprise customers greatly. At the moment if an email cannot be sent by the email server then an error is logged in JIRA and the email is retried 10 (ten) times. That's a lot of noise in the logs and quite the extra load in large systems. JEMH is fine inbound but for outbound email it needs code changes in JIRA.

I would imagine this as an admin page for Mail with a White list and a Black list. If the To address for an email matches the white list then it is passed and no further checking occurs. If it matches the blacklist then it fails. This would allow an admin to add their domain to the white list and a "match all" to the black list to support email servers that don't relay mail. The black list should start with a default set of domains from http://www.ietf.org/rfc/rfc2606.txt

Hi,

This is a bulk update to specific issues in the JIRA (JRA) project

As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

Best regards
Josh Devenny and Roy Krishna
JIRA Product Management

The mail handler JEMH will give you the inbound half, you can blacklist domains, specific accounts and even subjects via regexp. Blacklisting outbound users is something that can only be done through the default mail listener. Coincidentally JDigest provides a mechanism for replacing that, and I can see the value, so I'll add it to the future-feature list.

It would be nice if there were a way to implement filter rules on both incoming and outgoing email, both globally and either per project or per notification scheme.

Anton, ideally both. The former would stop one end of injection into the loop, the latter would close the other entry point. The ability to at least stop the queue flushing would be useful; the ability to blacklist incoming email would be extremely so.

Rob,

Do you mean that you would like to be able to remove Mail items from the queue before they are sent, and be able to black list e-mail addresses, such that JIRA does not create issues or comments from e-mail messages coming from these email addresses?

Thanks,
Anton