DSNs and NDRs in Exchange Server
When there's a problem delivering a message, Exchange sends an NDR to the message sender that indicates there was a problem. NDRs include a code that indicates why the message wasn't delivered, and possible solutions to help get the message delivered.
The information that's included in NDRs is designed to be easy to read and helpful for both users and administrators. In some cases, senders can identify and fix their own problems (for example, when there's a typo in the recipient's email address). In other cases, an administrator may need to fix an issue in the Exchange environment, or notify the administrators in the destination domain about problems in their messaging environment.
For procedures related to NDRs in Exchange Server, see Procedures for DSNs and NDRs in Exchange Server.
If you need help with NDRs in Microsoft 365, Office 365, or Exchange Online, see Email non-delivery reports in Exchange Online.
Information in NDRs
This is an example of an NDR:
The information in an NDR is separated into two sections:
User information section: This section appears first and attempts to explain (in non-technical terms) why delivery of the message failed, and possible steps to successfully deliver the message.
The text that's displayed in this section is inserted by the Exchange server that generated the NDR.
When applicable, the fully qualified domain name (FQDN) of the server that rejected the message is included in the user information section (for example mbx01.contoso.com).
If delivery failed for multiple recipients, the email address and reason for failure is listed for each recipient is listed..
Diagnostic information for administrators section: This section provides deeper technical information to help administrators troubleshoot the issues that caused the delivery failure.
A key piece of information in this section is the enhanced status code (for example, 4.4.7).
The enhanced status code is returned by the server that generated the NDR (the source server that couldn't deliver the message, or the destination server that rejected the message).
The enhanced status code determines the text that's displayed in the user information section (the code value isn't altered by Exchange).
You can use the New-SystemMessage cmdlet in the Exchange Management Shell to modify the text that appears in user information section for a given enhanced status code (including different text in different languages). By creating custom explanations, you can provide specific content for your environment, such as contact information for your help desk, or links to your Intranet for self-service support. For more information, see Procedures for DSNs and NDRs in Exchange Server.
- The Common enhanced status codes section in this topic explains what the numbers mean, the codes that you're likely to encounter, and suggestions to fix the underlying problem that prevented the message from being delivered.
The following information is also available in this section:
Generating server: The messaging server that created the NDR. If a remote server isn't listed below the sender's email address, the generating server is also the server that rejected the original email message. If message delivery fails between senders and recipients in the Exchange organization, the same server typically rejects the original message and generates the NDR.
The rejected recipients: The recipient's email address in the original message that couldn't be delivered. If delivery fails for multiple recipients, the email address of each recipient is listed. This field also contains the following sub-fields for each email address:
Remote server: The FQDN of the server that rejected the original message during SMTP transmission (delivery failed after the message body was sent, but before the server acknowledged receiving the message). This field isn't present when:
The server that rejected the message also generated the NDR. This is typical for delivery failures between senders and recipients in the same Exchange organization.
The remote server acknowledged receiving the original message, but the message was rejected for other reasons (for example, content restrictions).
Enhanced status code
SMTP response: The US-ASCII text string that's returned by the messaging server that rejected the original message. This is typically a short explanation of the enhanced status code. This string is not rewritten by Exchange.
Original message headers: This area contains the message header of the rejected message. These header fields can provide useful diagnostic information (for example, server hops in the message routing path, or whether the To field matches the email address of the rejected recipient).
Common enhanced status codes
Enhanced status codes are defined in RFC 3463, and use the syntax <class>. <subject>. <detail>:
<class>: 4 indicates a temporary delivery error. 5 indicates a permanent delivery error.
<subject>: The RFC categorizes the values like this:
2: Mailbox (the recipient)
3: Mail system (the destination mail system)
4: Network and routing
5: Mail delivery protocol
7: Security or policy
<detail>: A 1 to 3 digit number that further classifies the error.
The following tables contain the enhanced status codes that are returned in NDRs for the most common message delivery failures.
For information about enhanced status codes in Microsoft 365 or Office 365 and hybrid environments, see Email non-delivery reports in Exchange Online.
Temporary delivery failures
|Enhanced status code||Description||Possible causes and solutions|
||Free disk space is low (for example, the disk that holds the queue database doesn't have the required amount of free space). For more information, see Understanding back pressure. To move the queue database to a different disk, see Change the location of the queue database.
Available memory is low (for example, Exchange installed on a virtual machine that's configured to use dynamic memory). Always use static memory on Exchange virtual machines. For more information, see Exchange memory requirements and recommendations.
|You've configured a custom Receive connector in the Transport (Hub) service on a Mailbox server that listens on port 25. Typically, custom Receive connectors that listen on port 25 belong in the Front End Transport service on the Mailbox server.
Important Exchange server components are inactive. You can confirm this by running the following command in the Exchange Management Shell:
To restart all inactive components, run the following command:
Incompatible transport agents (in particular, after an Exchange update). After you identify the transport agent, disable it or uninstall it. For more information, see Troubleshoot transport agents.
||Transient network issues that might eventually correct themselves. The Exchange server periodically tries to connect to the destination server to deliver the message. After multiple failures, the message is returned to the sender in an NDR with a permanent failure code.
For more information about configuring the queue retry and failure intervals, see Configure message retry, resubmit, and expiration intervals.
To manually retry a queue, see Retry queues.
Firewall or Internet service provider (ISP) restrictions on TCP port 25.
||Transient network issues or server problems that might eventually correct themselves. The sending server will retry delivery of the message, and will generate further status reports.
The message size limit for the connection has been reached, or the message submission rate for the source IP address has exceeded the configured limit. For more information, see Message rate limits and throttling.
Antispam, SMTP proxy, or firewall configuration issues are blocking email from the Exchange server.
|Send connector configuration issues. For example:
• The Send connector is configured to use DNS routing when it should be using smart host routing, or vice-versa. Use nslookup to verify that the destination domain is reachable from the Exchange server.
• The FQDN that the Send connector provides to HELO or EHLO requests doesn't match the host name in your MX record (for example, mail.contoso.com). Some messaging systems are configured to compare these values in an effort to reduce spam. The default value on a Send connector is blank, which means the FQDN of the Exchange server is used (for example, exchange01.contoso.com).
The Mailbox Transport Delivery service isn't started on the destination server (which prevents the delivery of the message to the mailbox).
The destination messaging system has issues with Transport Neutral Encryption Format (TNEF) messages (also known as rich text format or RTF in Outlook). For example, meeting requests or messages with images embedded in the message body.
If the destination domain uses the Sender Policy Framework (SPF) to check message sources, there may be SPF issues with your domain (for example, your SPF record doesn't include all email sources for your domain).
Permanent delivery failures
|Enhanced status code||Description||Possible causes and solutions.|
||Replying to old messages, or messages that were exported as files (important recipient attributes might have changed). Verify that the recipient's email address is correct.
Malformed or missing attributes in contact entries.
The sender is blocked by sender filtering (directly, or the sender is on a user's Blocked Senders list, and the Sender Filter agent is configured to use safelist aggregation. For more information, see Sender filtering and Safelist aggregation.
|The recipient's email address is incorrect (the recipient doesn't exist in the destination messaging system). Verify the recipient's email address.
You recreated a deleted mailbox, and internal users are addressing email messages in Outlook or Outlook on the web using old entries in their autocomplete cache (the X.500 values or LegacyExchangeDN values for the recipient are now different). Tell users to delete the entry from their autocomplete cache and select the recipient again.
||The recipient's email address is incorrect (for example, it contains unsupported characters or invalid formatting).|
||Receive connectors reject SMTP connections that contain the top level domains defined in RFC 2606 (.test, .example, .invalid, or .localhost), This behavior is controlled by the RejectReservedTopLevelRecipientDomains parameter on the New-ReceiveConnector and Set-ReceiveConnector cmdlets.|
||Receive connectors reject SMTP connections that contain the second level domains defined in RFC 2606 (example.com, example.net, or example.org). This behavior is controlled by the RejectReservedSecondLevelRecipientDomains parameter on the New-ReceiveConnector and Set-ReceiveConnector cmdlets.|
||Receive connectors reject SMTP connections that contain single label domains (for example, chris@contoso instead of email@example.com) This behavior is controlled by the RejectSingleLabelRecipientDomains parameter on the New-ReceiveConnector and Set-ReceiveConnector cmdlets.|
|There's a problem with the sender's email address. Verify the sender's email address.|
||The sender has exceeded a message rate limit (for example, an application server is configured to relay a large number of messages through Exchange. For more information, see Message rate limits and throttling and Allow anonymous relay on Exchange servers.|
||The message was quarantined by content filtering. To configure exceptions to content filtering, see Use the Exchange Management Shell to configure recipient and sender exceptions for content filtering.|
||The recipient's mailbox has exceeded its storage quota and is no longer able to accept new messages. For more information about configuring mailbox quotas, see Configure storage quotas for a mailbox.|
||The message is too large. Send the message again without any attachments, or configure a larger message size limit for the recipient. For more information, see Recipient limits.|
||The message was determined to be malformed, and was moved to the poison message queue. For more information, see Types of queues.|
||You're using the ABP Routing agent, and the recipient isn't a member of the global address list that's specified in their address book policy (ABP). For more information, see Use the Exchange Management Shell to install and configure the Address Book Policy Routing Agent and Address book policies in Exchange Server.|
||Receive connectors that are used for internal mail flow are missing the required Exchange Server authentication mechanism. For more information about authentication on Receive connectors, see Receive connector authentication mechanisms.|
||The message is too large. This error can be generated by the source or destination messaging system. Send the message again without any attachments, or configure a larger message size limit. For more information, see Message size and recipient limits in Exchange Server.|
||A mail loop was detected. Verify that the FQDN property on the Receive connector doesn't match the FQDN of another server, service, or device that's used in mail flow in your organization (by default, the Receive connector uses the FQDN of the Exchange server).|
||There's a DNS or network adapter configuration issue on the Exchange server.
• Verify the internal and external DNS lookup settings for the Exchange by running these commands in the Exchange Management Shell:
Get-TransportService | Format-List Name,ExternalDNS*,InternalDNS*
Get-FrontEndTransportService | Format-List Name,ExternalDNS*,InternalDNS*
You can configure these settings by using the InternalDNS* and ExternalDNS* parameters on the Get-TransportService and Get-FrontEndTransportService cmdlets.
By default, these settings are used by Send connectors (the default value of the UseExternalDNSServersEnabled parameter value is
• Check the priority (order) of the network adapters in the operating system of the Exchange server.
||A configuration error has caused an email loop. By default, after 20 iterations of an email loop, Exchange interrupts the loop and generates an NDR.
Verify that Inbox rules for the recipient and sender, or forwarding rules on the recipient 's mailbox aren't causing this (the message generates a message, which generates another message, and the process continues indefinitely).
Verify the mailbox doesn't have a targetAddress property value in Active Directory (this property corresponds to the ExternalEmailAddress parameter for mail users in Exchange).
If you remove Exchange servers, or modify settings related to mail routing an mail flow, be sure to restart the Microsoft Exchange Transport and Exchange Frontend Transport services.
||SMTP commands are sent out of sequence (for example, a server sends an SMTP command like AUTH or MAIL FROM before identifying itself with the EHLO command). After establishing a connection to a messaging server, the first SMTP command must always be EHLO or HELO.|
||The combined total of recipients on the To, Cc, and Bcc lines of the message exceeds the total number of recipients allowed in a single message for the organization, Receive connector, or sender. For more information, see Message size and recipient limits in Exchange Server.|
|You have an application server or device that's trying to relay messages through Exchange. For more information, see Allow anonymous relay on Exchange servers.
The recipient is configured to only accept messages from authenticated (typically, internal) senders. For more information, see Configure message delivery restrictions for a mailbox.
|A firewall or other device is blocking the Extended SMTP command that's required for Exchange Server authentication (X-EXPS).
Internal email traffic is flowing through connectors that aren't configured to use the Exchange Server authentication method . Verify the remote IP address ranges on any custom Receive connectors.
||The message was rejected by a mail flow rule (also known as a transport rule). This enhanced status code range is available when the rule is configured to reject messages (otherwise, the default code that's used is 5.7.1). For more information, see Mail flow rule actions in Exchange Server.|