Notification email logs and diagnostics
Use logs and diagnostics to monitor notification email delivery, identify issues with individual emails, and check recipient details.
Diagnostics help monitor the overall health of the system and troubleshoot general problems, such as not receiving any incoming mail. Logs help identify problems with individual emails, and different logs are useful for diagnosing different types of problems.
Log checking scenarios
|
Problem |
Log |
|---|---|
|
Need to check whether an individual notification email was successfully sent |
Check the Sent System Mailbox for that email. Also check the Failed System Mailbox for failure notifications. |
|
Individual email failed |
Warning: Some email servers do not return error strings. |
|
Email not received by end user |
Warning: Some email servers do not return error strings.
|
See the following resources on troubleshooting inbound and outbound email problems.
|
Error or symptom |
Solution |
|---|---|
|
Inbound Email FAQ | |
|
Instance not receiving inbound email |
See Inbound email troubleshooting, ServiceNow Inbound email troubleshooting [KB0524472] and Inbound Email overview and troubleshooting [KB0520595]. These KB articles also provide links to a video series on troubleshooting inbound emails. |
|
Instance not sending outbound email |
See Troubleshooting Outbound email, ServiceNow Troubleshooting outbound email [KB0521382]. This KB article also provides links to a video series on troubleshooting outbound emails. |
|
Email from Outlook produces an empty Incident record containing an attachment named winmail.dat. |
Configure the local Outlook client or Exchange server not to send Rich Text formatted (RTF) data to the instance. |
|
Emails are getting set to type send-ignored for no obvious reason |
See How to resolve email notifications marked as send-ignored [KB0790932]. |
|
Duplicate emails generated by the instance |
See Troubleshooting duplicate emails generated by the instance, Troubleshooting duplicate emails generated by the instance [KB0529413]. |
|
SMTP Sender Job Stuck |
See SMTP Sender Job Stuck > 30 Mins alert, Your instance has generated a "SMTP Sender Job Stuck" alert [KB0755061]. |
|
Connection to smtp.office365.com failed | |
|
IMAP with OAuth error AUTHENTICATE failed |
See IMAP OAuth AUTHENTICATE failed error when connecting to Microsoft 365 [KB0963959]. |
|
Error connecting the POP email account on secure port |
See Error connecting to POP/IMAP/SMTP Email Account Server on secure port [KB0829289]. |
|
Inbound email processing is stuck alerts |
See Inbound email processing is stuck or delayed [KB0855277]. |
|
Email Reader / SMTP Sender job stuck | |
|
Email Reader Job stuck/running for more than 2 hours alerts |
See Email Reader Job stuck/running for more than 2 hours alerts [KB0755063]. |
|
SMTP retries |
The SMTPSender job is responsible for sending emails from the instance and sometimes delivery failures can occur during transmission. Emails that aren't successfully delivered might need retries. Exponential back-off retries are a mechanism to redeliver them in the interval (1, 5, 10, 20, 40, 60, 120, 120) between the retries. The exponential retries continue until the lookback period mentioned in the glide.email.smtp.claim.lookback.hrs system property is lapsed. The retries are attempted for 4xx status codes and for all other status codes such as 5xx are considered as permanent failure. The glide.smtp.fail_message_ids and glide.smtp.defer_retry_ids system properties aren't considered. Retried emails type is set to send-retry-backoff. |
Emails that aren't successfully delivered might need retries. Exponential back-off retries are a mechanism to redeliver them in the interval (1, 5, 10, 20, 40, 60, 120, 120) between the retries. The exponential retries continue until the lookback period mentioned in the glide.email.smtp.claim.lookback.hrs system property is lapsed.
The retries are attempted for 4xx status codes and fail for 5xx status codes during the email delivery. The glide.smtp.fail_message_ids and glide.smtp.defer_retry_ids system properties aren't considered.
Retried emails type is set to send-retry-backoff.
Note: Address validation errors that occur during the email delivery are handled differently. The type of email record is set to send-retry-delayed and the email delivery is retried in fixed intervals of 30 minutes until the lookback period is lapsed.
- Email diagnostics
The Diagnostics and Connection page provides information on the current state of your email configuration. This page includes status on email properties, scheduled jobs, and email account connections that affect how your instance receives and sends email. - System email log and mailboxes
The system email log records all emails that the instance creates or receives. System mailboxes are filtered views of this log. - Message logs for individual emails
The email log entries for an individual notification email are accessible as a related list in the email record. The Error string field in the email record can provide additional information.
Parent Topic:Email and SMS notifications
Related topics
Create notification categories
--- title: Notification email logs and diagnostics description: Use logs and diagnostics to monitor notification email delivery, identify issues with individual emails, and check recipient details. locale: en-US canonical_url: https://www.servicenow.com/docs/r/platform-administration/troubleshooting-notification-emails.html release: brazil topic_type: concept last_updated: "2026-09-10" reading_time_minutes: 5 keywords: [support-video] breadcrumb: [Email and SMS notifications, System notifications, Notifications, Configure core features, Administer the ServiceNow AI Platform] --- # Notification email logs and diagnostics Use logs and diagnostics to monitor notification email delivery, identify issues with individual emails, and check recipient details. Diagnostics help monitor the overall health of the system and troubleshoot general problems, such as not receiving any incoming mail. Logs help identify problems with individual emails, and different logs are useful for diagnosing different types of problems. ## Log checking scenarios <table id="table_wfc_dfh_2gb"><thead><tr><th> Problem </th><th> Log </th></tr></thead><tbody><tr><td> Need to check whether an individual notification email was successfully sent </td><td> Check the **Sent** System Mailbox for that email. Also check the **Failed** System Mailbox for failure notifications. </td></tr><tr><td> Individual email failed </td><td> - Check the message log of the individual email. - Check the **Error string** field of the email record. **Warning:** Some email servers do not return error strings. </td></tr><tr><td> Email not received by end user </td><td> - Check the **Junk** System Mailbox for notifications about returned emails. These emails also appear in the Emails log with a **Type** of received-ignored. - Check the **Error string** field of the email record. **Warning:** Some email servers do not return error strings. - Check the message log of the individual email for the reasons different recipients were included or excluded. </td></tr></tbody> </table>## Troubleshooting resources See the following resources on troubleshooting inbound and outbound email problems. <table id="table_rhh_2tr_n4"><thead><tr><th> Error or symptom </th><th> Solution </th></tr></thead><tbody><tr><td> Inbound Email FAQ </td><td> See [Inbound Email FAQ \[KB0957760\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0957760). </td></tr><tr><td> Instance not receiving inbound email </td><td> See Inbound email troubleshooting, ServiceNow [Inbound email troubleshooting \[KB0524472\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0524472) and [Inbound Email overview and troubleshooting \[KB0520595\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0520595). These KB articles also provide links to a video series on troubleshooting inbound emails. </td></tr><tr><td> Instance not sending outbound email </td><td> See Troubleshooting Outbound email, ServiceNow [Troubleshooting outbound email \[KB0521382\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0521382). This KB article also provides links to a video series on troubleshooting outbound emails. </td></tr><tr><td> Email from Outlook produces an empty Incident record containing an attachment named winmail.dat. </td><td> Configure the local Outlook client or Exchange server not to send Rich Text formatted \(RTF\) data to the instance. </td></tr><tr><td> Emails are getting set to type send-ignored for no obvious reason </td><td> See [How to resolve email notifications marked as send-ignored \[KB0790932\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0790932). </td></tr><tr><td> Duplicate emails generated by the instance </td><td> See Troubleshooting duplicate emails generated by the instance, [Troubleshooting duplicate emails generated by the instance \[KB0529413\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0529413). </td></tr><tr><td> SMTP Sender Job Stuck </td><td> See SMTP Sender Job Stuck > 30 Mins alert, [Your instance has generated a "SMTP Sender Job Stuck" alert \[KB0755061\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0755061). </td></tr><tr><td> Connection to smtp.office365.com failed </td><td> See [Connection to smtp.office365.com fails with error "535 5.7.3 Authentication unsuccessful" due to ServiceNow source IP addresses blocked on Office365 \[KB0825391\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0825391). </td></tr><tr><td> IMAP with OAuth error AUTHENTICATE failed </td><td> See [IMAP OAuth AUTHENTICATE failed error when connecting to Microsoft 365 \[KB0963959\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0963959). </td></tr><tr><td> Error connecting the POP email account on secure port </td><td> See [Error connecting to POP/IMAP/SMTP Email Account Server on secure port \[KB0829289\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0829289). </td></tr><tr><td> Inbound email processing is stuck alerts </td><td> See [Inbound email processing is stuck or delayed \[KB0855277\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0855277). </td></tr><tr><td> Email Reader / SMTP Sender job stuck </td><td> See [Email Reader / SMTP Sender job stuck \[KB0679998\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0679998). </td></tr><tr><td> Email Reader Job stuck/running for more than 2 hours alerts </td><td> See [Email Reader Job stuck/running for more than 2 hours alerts \[KB0755063\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0755063). </td></tr><tr><td> SMTP retries </td><td> The SMTPSender job is responsible for sending emails from the instance and sometimes delivery failures can occur during transmission. Emails that aren't successfully delivered might need retries. Exponential back-off retries are a mechanism to redeliver them in the interval \(1, 5, 10, 20, 40, 60, 120, 120\) between the retries. The exponential retries continue until the lookback period mentioned in the **glide.email.smtp.claim.lookback.hrs** system property is lapsed. The retries are attempted for 4xx status codes and for all other status codes such as 5xx are considered as permanent failure. The **glide.smtp.fail\_message\_ids** and **glide.smtp.defer\_retry\_ids** system properties aren't considered. Retried emails type is set to **send-retry-backoff**. </td></tr></tbody> </table>## Exponential back-off retries Emails that aren't successfully delivered might need retries. Exponential back-off retries are a mechanism to redeliver them in the interval \(1, 5, 10, 20, 40, 60, 120, 120\) between the retries. The exponential retries continue until the lookback period mentioned in the **glide.email.smtp.claim.lookback.hrs** system property is lapsed. The retries are attempted for 4xx status codes and fail for 5xx status codes during the email delivery. The **glide.smtp.fail\_message\_ids** and **glide.smtp.defer\_retry\_ids** system properties aren't considered. Retried emails type is set to **send-retry-backoff**. **Note:** Address validation errors that occur during the email delivery are handled differently. The type of email record is set to **send-retry-delayed** and the email delivery is retried in fixed intervals of 30 minutes until the lookback period is lapsed. - **[Email diagnostics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-administration/r_MailDiagnostics.md)** The Diagnostics and Connection page provides information on the current state of your email configuration. This page includes status on email properties, scheduled jobs, and email account connections that affect how your instance receives and sends email. - **[System email log and mailboxes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-administration/r_EmailLogs.md)** The system email log records all emails that the instance creates or receives. System mailboxes are filtered views of this log. - **[Message logs for individual emails](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-administration/message-logs-individual-emails.md)** The email log entries for an individual notification email are accessible as a related list in the email record. The **Error string** field in the email record can provide additional information. **Parent Topic:**[Email and SMS notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-administration/c_EmailNotifications.md) **Related topics** [Create notification categories]() [Create an email notification]() [Email notifications dashboard]() [Email diagnostics dashboard]() [Email templates]() [Email layouts]() [Email retention]() [Watermarks on notification emails]() [Parse an email thread]() [Email digests]() [Domain separation and Notifications]()
| title | Notification email logs and diagnostics |
| description | Use logs and diagnostics to monitor notification email delivery, identify issues with individual emails, and check recipient details. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/platform-administration/troubleshooting-notification-emails.html |
| release | brazil |
| topic_type | concept |
| last_updated | 2026-09-10 |
| reading_time_minutes | 5 |
| keywords | support-video |
| breadcrumb | Email and SMS notificationsSystem notificationsNotificationsConfigure core featuresAdminister the ServiceNow AI Platform |