Health Check: Mail Error Queue
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
To use the health check for a mail error queue, upgrade the ATST plugin to at least version 1.53.2.
About the health check
This health check ensures the healthiness of email sending in Jira Data Center. Emails that couldn't be delivered to a recipient will appear in a mail error queue. Email sending is unhealthy when a mail error queue has any emails.
Understanding the results
Jira Server
Icon | Result | What this means |
|---|---|---|
| There are no emails in an error queue. | All emails have been delivered to recipients. |
| There is a number of emails in the error queue. | An exact number of emails couldn't be delivered to recipients, and Jira won't retry sending. An administrator should troubleshoot the issue. Learn more in Troubleshooting. |
Jira Data Center
Icon | Result | What this means |
|---|---|---|
| There are no emails in the error queue on a particular node. If you get a notification about a failing health check for a mail error queue, verify the other nodes. | All emails have been delivered to recipients from this particular node. |
| There is a number of emails in an error queue on a particular node. | An exact number couldn't be delivered to recipients from this particular node, and Jira won't retry sending. An administrator should troubleshoot the issue. Learn more in Troubleshooting. |
What happens if I ignore the warning?
Emails in a mail error queue won't be sent to recipients. This means that some users may never get a Jira email notification intended for them.
Troubleshooting
As an immediate mitigation step, you might consider resending the mail error queue. To do so, go to Administration 
and select System. Then, go to Mail queue and Error queue. Emails in a mail error queue won't be sent to recipients. This means that some users may never get a Jira email notification intended for them.
Take this step only as a temporary workaround since it won't resolve the underlying issue with sending emails.
In some situations, manually resending the mail error queue won't help, and emails might still pile up in the error queue. In these cases, don't try to resend the error queue several times. This action will generate more threads for Jira to process, causing potential performance issues.
To investigate the reason why issues are piling up in the Mail Error queue, we recommend checking the atlassian-jira-outgoing-mail.log file and check the KB articles listed below based on the errors found in these logs:
- The Jira "Mail Error Queue" Health Check fails due to the errors "Domain contains illegal character in string", "Invalid Addresses" or "Illegal address in string"
- The Jira "Mail Error Queue" Health Check fails due to the error "service proxy has been destroyed"
- Jira notification emails fail to be sent due to read timed out error
- Unable to Send Email with SMTP Server via SSL '530 5.7.0 Must issue a STARTTLS command first' Due to 'mail.smtp.starttls.enable' Property
- Jira notification emails intermittently fail to be sent due to the error "OAUTH2 asked for more" when using Gmail with Oauth 2.0
- Jira notification emails fail to be sent due to the "Unrecognized SSL message" error
Providing data to Atlassian Support
If you still can't troubleshoot and fix the problem, create a support ticket at support.atlassian.com and attach the requested information. To get support:
Go to Administration
> System > Logging and profiling.In the Outgoing mail section, select Enable.
Select Enable debugging.
Select Configure logging level for another package.
Use com.atlassian.jira.service as the package name and select "DEBUG" for the Logging level.
Wait for about 15 minutes so that we can collect enough logs.
Go to Administration
> System > Troubleshooting and support tools > Create support zip.Select Customize zip, then select Thread dumps, and select Save.
Select Create zip and download the support zip. In case you have a Data Center cluster, repeat this step for each node.
Run the following SQL query on the Jira database:
select * from rundetails where job_id = 'com.atlassian.jira.service.JiraService:10000';Attach to the support ticket:
The support zips.
The result of the SQL query.
*To disable the additional logging, select Configure logging level for another package. > Use com.atlassian.jira.service as the package name and select "ERROR" for the logging level