Using Google Groups as a Inbound Mail Server

Summary

When using google groups there may be some differences between the email that send to the google group and the email that gets processed by JEMHC. This is due to Google Groups modifying the Email when it is received.

Using DMARC Quarantine or Reject

For more info about these policies see: https://dmarc.org/overview/

When you using DMARC "p=quarantine" policy or DMARC "p=reject" policy then it will result in the original Sender being replaced with the Google Group address. This means that when the mail is processed by JEMHC it will see the sender as the Catch Email Address and will result in the Issue being created as “Enterprise Email Handler for Jira (JEMH)” instead of the sender to prevent Mail loops from occurring.

JEMHC Options

One option to set the reporter as the original Sender is to set the Sender address headers as “Reply-To”. This means that JEMHC will check within the “Reply-To” header for the original Sender as the Google Group does not modify this and as a result JEMHC is able to find the original sender.

Note: If the Reply-To is not found it will result in an error and the issue will not be created/updated.

Another option would be to set the Sender address headers as “Reply-To,From” as this will mean that if the “Reply-To” header is not found then JEMHC will attempt to use the address within “From” header which if found will result in the issue being created/updated.

Note: If the first header in the list (Reply-To) contains an address that is a Catch Email Address then the issue will be created as “Enterprise Email Handler for Jira (JEMH)” even if there is an address within the other headers (From).