...
If comment counts reaches more than a given number, they are forwarded rather than added to the issue (that would trigger a comment notification), this doesn't stop other users adding comments, but ensures that email sourced traffic is stopped.
If comment size reaches more than a given number, the same happens.
...
...
Blocklisting
...
Blocklisting by sender
Many common 'bounce' emails are not going to be useful to Jira, for example, anything coming from your local Mail Server 'postmaster'. JEMH supports outright blacklisting blocklisting of email domains (e.g. postmaster@.*) that can be dropped silently without creating issues. This configuration is done per-Profile.
...
...
Blocklisting by subject (Out of Office blocker)
When senders cannot be blacklistedblocklisted, perhaps because they are valid Jira users, JEMH can filter emails based on subject, blacklisting blocklisting and dropping matches, this is especially useful for those Out of Office notifications that even SPAM up the Atlassian servers from time to time...
...
| Filter by label (Content by label) | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|