...
What are mail loops
Mail loops are when an Email email from JEMHC ends up back in a JEMHC mailbox. This is bad because it consumes your capacity plan for no useful outcome.
...
All JEMHC mail is ‘tagged’ with a header Precedence: bulk which by default JEMHC will block. This action stop the loop and prevents it from creating a comment/update that would trigger a further notification - such a case would be a runaway loop - JEMHC detects and blocks that. Yes, this still This consumes a ‘msg’ message from your Plan , but is an awful lot better than consuming ALL your planallowance. You can use find these problem messages via JEMHC > Auditing > Inbound Messages to find these messages, scan , then view the source Jira issue to see where this comes from and fix.
...
Profile > Catch Email Addresses defines what your Mailbox addresses are, configuring this and maintaining it is needed to prevent JEMHC considering given catchemail’s as ‘user addresses’.
| Note |
|---|
If you do not set you Catchemail addresses, JEMHC will not know what your mailbox |
...
addresses are. This can lead to them being included on an issue, or even creating users with that address, causing a mail loop. |
Portal / Jira users with email address matching your mailbox
...
JEMHC will (by default) automatically block all Precedence: Bulk tagged mail, each . Each message still deducts from your Plan allowance, but runaway loops are prevented. Its on you to diagnose the source and prevent (see Support later).
Manual Actions by you
Mailbox filtering of sender
Sender addresses are not aren’t ignored by default as some customers use JEMHC Adhoc functionality to deliberately send mail to other mailboxes to create issues in other Projects. If you want It’s possible to block senders, if done within sender addresses in JEMHC, however the ‘mail’ email would still be read, its . It's more efficient for you to create a server-side rule in on incoming mailboxes to route/drop messages differentlyfilter out emails as needed. Configuration of your mail server for this is out of scope for support.
...
Its common to see scenarios where a group email address eg ‘alerts@blahe.g. ‘alerts@example.com’ is comprised of many users to ‘actually notify’ notify as well as JEMHC mailbox to ‘track’for tracking purposes. In such cases, JEMHC will may treat this address ‘as’ a user address or email only user addressas a notification candidate. Subsequent notifications to that address will resolve to the inbound mailbox, causing a loop. This is not caused by JEMHC and is hard to detect. Typically JEMHC depends on Precedence: Bulk handling to block the processing of such mails, but , will have to process the mail, so it still affects your monthly capacity plan - its a consequence of your environmentplan allowance.
Group sender addresses on incoming mail
In the same way, the sender of mail may be a ‘group’ address. If that user exists in Jira already, it would be set as the reporter , and notified, again. Again, your mailserver mail server would expand that address and deliver, again, JEMHC will block based on Precedence: bulk, and again consume mail. This also is a consequence of your environment.
...
We plan to develop scripting support, which is already in the DC version (JEMH)self-hosted version of the app. When this is available, we will have more custom capabilities on handling and processing mail recipients (tracked internally as JEMHC-2177)will be possible.
Cloud mail service providers typically offer some way to lookup group addresses, as/when we are able to integrate with those services, we can dissolve derive recipients from the group into actual recipients. Then, then pre-existing catchemail checks would be usable to block some delivery (tracked internally as JEMHC-2234)prevent a loop.
Related to (2) in JEMH for DC had the capability to point 2, the self-hosted version of the app can use Exchange to expand distribution group address via LDAP queries. With Single Sign-On services such as Atlassian ID and so on, we’re unsure whether this case feature is still needed, . You can let us know by giving feedback through our support , thanks!channel.
Getting support
We are happy to help and will typically need an example email and/or issue screenshot to clarify how the loop occurs. Use Navigating to JEMHC > Auditing > Incoming Messages will allow you to get and provide us with:
The incoming email via Export
. Note that currently only the most recent 100 messages are retained and exportable, so you have to be quick!A screenshot of processing details via View Report
...