Troubleshoot Email Rejection in Jira Service Management Cloud
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
Emails sent by JSM customers are rejected with one of the below error messages in the processing logs:
Auto-reply mail
Bulk mail
Automated delivery status message
Diagnosis
Rejected customer emails are diagnosed at Space Settings > Channels & self-service > Email > Processing logs, which shows one of three rejection reasons: Auto-reply mail, Bulk mail, or Automated delivery status message.
Cause
The meaning of each filter
Jira Service Management Email processor filters emails based on the content of the auto-generated headers:
Auto-replies |
|
Bulk mail | Filters out emails that the mail server marks as spam. An email with this in the header means it is telling the receiver's mail server that this email is intended to be sent to many subscribers. The header contains |
Delivery status | filter out emails if the multipart/report header contains report-type-delivery-status, or if the return-path header has a null email address. |
If the email sent by the customer contains any of those headers, it will be rejected by the Jira Service Management email processor. In the processing log, click the three dots > Download raw email message beside the rejected email to confirm which header triggered the filter before asking the sender to adjust their mail system.
Solution
Avoiding email rejection with the allowlist
To avoid the rejection of the emails sent from your customers, you can add their domain to the allowlist. Messages received from domains in the allowlist are never filtered out, regardless of the content of the message. Add trusted domains to the allowlist so you'll always receive their messages.
You must be a project admin and have product access to Jira Service Management to add, edit, and remove domains from the allowlist. Have a look at Global and project permissions and How to update product access settings to learn more.
To add a domain to your allowlist:
From your service project, go to Space settings > Channels & self service > Email.
Select More (...) > Manage allowlist.
Select + Add domain name.
Enter the domain name (do not include @).
Select Save.
Currently, allowlists only support exact domain matching. For example, adding 'example.com' will match 'anyuser@example.com' but not 'anyuser@example.com.au' or 'anyuser@mail.example.com'.
The allowlist does not currently support individual email addresses, wildcards, or pattern matching.
If a message appears to be spam or phishing because it fails DMARC sender verification, it will be filtered out regardless of your allowlist settings.
Was this helpful?