You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Exchange/ExchangeOnline/email-delivery/ndr/non-delivery-reports-in-exchange-online.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,15 +51,15 @@ The following table contains the error codes (also known as enhanced status code
51
51
|5.0.350|Generic error, `x-dg-ref header is too long`, or `Requested action not taken: policy violation detected (AS345)`|5.0.350 is a generic catch-all error code for a wide variety of nonspecific errors from the recipient's email organization. The specific `x-dg-ref header is too long` message is related to Rich Text-formatted messages. The specific `Requested action not taken: policy violation detected (AS345)` message is related to nested attachments.|For more information, see [Fix email delivery issues for error code 550 5.0.350 in Exchange Online](fix-error-code-550-5-0-350-in-exchange-online.md).|
52
52
|5.1.0|`Sender denied`|A common cause of this NDR is when you use Microsoft Outlook to save an email message as a file, and then someone opened the message offline and replied to it. The message property preserves only the **legacyExchangeDN** attribute when Outlook delivers the message. Therefore, the lookup could fail.|Either the recipient address is incorrectly formatted or the recipient couldn't be correctly resolved. The first step in resolving this error is to check the recipient address and send the message again. <br/><br/> For more information, see [Fix email delivery issues for error code 5.1.0 in Exchange Online](fix-error-code-550-5-1-0-in-exchange-online.md).|
53
53
|5.1.1|`Bad destination mailbox address`|This failure might be caused by the following conditions: <ul><li>The recipient's email address was entered incorrectly by the sender.</li><li>The recipient's email address doesn't exist in the destination email system.</li><li>The recipient's mailbox was moved and the Outlook recipient cache on the sender's computer hasn't updated.</li><li>An invalid legacy domain name (DN) exists for the recipient's mailbox Active Directory Domain Service.</li></ul>|This error typically occurs if the sender of the message enters an incorrect email address of the recipient. The sender should check the recipient's email address and send again. This error can also occur if the recipient email address was correct in the past but has changed or been removed from the destination email system. <br/><br/> If the sender of the message is in the same organization as the recipient, and the recipient's mailbox still exists, determine whether the recipient's mailbox was relocated to a new email server. If so, Outlook might not have updated the recipient cache correctly. Instruct the sender to remove the recipient's address from sender's Outlook recipient cache, and then create a new message. Resending the original message will cause the same failure. <br/><br/> For more information, see [Fix email delivery issues for error code 5.1.1 through 5.1.20 in Exchange Online](fix-error-code-550-5-1-1-through-5-1-20-in-exchange-online.md).|
54
-
|5.1.8|`Access denied, bad outbound sender`|The account was blocked for sending too much spam. Typically, this problem occurs because the account was compromised (hacked) by phishing or malware.|For more information, see [Fix email delivery issues for error code 5.1.8 in Exchange Online](fix-error-code-5-1-8-in-exchange-online.md).|
54
+
|5.1.8|`Access denied, bad outbound sender`|The account was blocked for sending too much spam. Typically, this problem occurs because the account was compromised (hacked) by phishing or malware.|For more information, see [Fix email delivery issues for error code 5.1.8 in Exchange Online](https://support.microsoft.com/topic/e323f21d-4460-4be1-999c-c9c0cc6be4b4).|
55
55
|5.1.10|`Recipient not found`|The recipient's `<SMTP Address>` wasn't found by SMTP address lookup. | For more information, see [Fix email delivery issues for error code 550 5.1.10 in Exchange Online](fix-error-code-550-5-1-10-in-exchange-online.md).|
56
56
|550 5.1.20|`Multiple From addresses are not allowed without Sender address`|An email message has multiple email addresses in the **From** field, but no email address in the **Sender** field.|For more information, see [Fix NDR error code 550 5.1.20 "Multiple From addresses are not allowed without Sender address"](/exchange/troubleshoot/email-delivery/ndr/fix-error-code-550-5-1-20-multiple-from-addresses).|
57
57
|5.1.90|`Your message can't be sent because you've reached your daily limit for message recipients`|The sender has exceeded the recipient rate limit, as described in [Sending limits](/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits).|This could indicate that the account was compromised and is being used to send spam. For more information, see [Responding to a compromised account](/defender-office-365/responding-to-a-compromised-email-account).|
58
58
|5.2.2|`Submission quota exceeded`|The sender has exceeded the recipient rate limit or the message rate limit as described in [Sending limits](/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits).|This could indicate the account was compromised and is being used to send spam. For more information, see [Responding to a compromised account](/defender-office-365/responding-to-a-compromised-email-account).|
59
59
|5.2.121|`Recipient's per hour message receive limit from specific sender exceeded`|The sender has exceeded the maximum number of messages that they're allowed to send per hour to a specific recipient in Exchange Online.|The automated mailer or sender should try again later, and reduce the number of messages that they send per hour to a specific recipient. <br/><br/> This limit helps protect Microsoft 365 or Office 365 users from rapidly filling their Inboxes with many messages from errant automated notification systems or other single-sender mail storms.|
60
60
|5.2.122|`Recipient's per hour message receive limit exceeded`|The Microsoft 365 or Office 365 recipient has exceeded the number of messages that they can receive per hour from all senders.|The automated mailer or sender should try again later, and reduce the number of messages that they send per hour to a specific recipient. <br/><br/> This limit helps protect Microsoft 365 and Office 365 users from rapidly filling their Inboxes with many messages from errant automated notification systems or other mail storms.|
61
61
|5.3.190|`Journaling on-premises messages to Microsoft 365 or Office 365 not supported when Journaling Archive is disabled`|Journaling on-premises messages to Microsoft 365 or Office 365 isn't supported for this organization because the organization hasn't turned on Journaling Archive in its settings.|A journaling rule is configured in the organization's on-premises environment to journal on-premises messages to Microsoft 365 or Office 365, but Journaling Archive is disabled. For this scenario to work, the organization's Office 365 administrator should either enable Journaling Archive or change the journaling rule to journal messages to a different location.|
62
-
|5.4.1|`Relay Access Denied`|The mail server that's generating the error doesn't accept mail for the recipient's domain. This error is caused by mail server or DNS misconfiguration.|For more information, see [Fix email delivery issues for error code 5.4.1 in Exchange Online](fix-error-code-550-5-4-1-in-exchange-online.md).|
62
+
|5.4.1|`Relay Access Denied`|The mail server that's generating the error doesn't accept mail for the recipient's domain. This error is caused by mail server or DNS misconfiguration.|For more information, see [Fix email delivery issues for error code 5.4.1 in Exchange Online](https://support.microsoft.com/topic/c0e98a8e-81db-49c2-9bf1-32a1734d3e77).|
63
63
|5.4.1|`Recipient address rejected: Access denied`|The recipient's address doesn't exist.|For more information, see [Use Directory Based Edge Blocking to reject messages sent to invalid recipients](/exchange/mail-flow-best-practices/use-directory-based-edge-blocking).|
64
64
|5.4.6 or 5.4.14|`Routing loop detected`|A configuration error has caused an email loop. 5.4.6 is generated by on-premises Exchange server (you'll see this code in hybrid environments). 5.4.14 is generated by Exchange Online. <br/><br/> By default, after 20 iterations of an email loop, Exchange interrupts the loop and generates an NDR to the sender of the message.|This error occurs if the delivery of a message generates another message in response. That message then generates a third message, and the process is repeated, creating a loop. To help protect against exhausting system resources, Exchange interrupts the mail loop after 20 iterations. Mail loops are typically created because of a configuration error on the sending mail server, the receiving mail server, or both. Check the sender's and recipient's mailbox rules configuration to determine whether automatic message forwarding is enabled. <br/><br/> For more information, see [Fix email delivery issues for error code 5.4.6 or 5.4.14 in Exchange Online](fix-error-code-5-4-6-through-5-4-20-in-exchange-online.md).|
65
65
|5.4.8|`MX hosts of <domain> failed MTA-STS validation`|The destination MX host was not the host expected per the domain's STS policy.|This error usually indicates that the destination domain's MTA-STS policy doesn't contain the MX host. For more information, see [Enhancing mail flow with MTA-STS](/purview/enhancing-mail-flow-with-mta-sts).|
@@ -102,8 +102,8 @@ The following table contains the error codes (also known as enhanced status code
102
102
|5.7.513|`Service unavailable, Client host [$ConnectingIP] blocked by $recipientDomain using Customer Block list (AS16012607)`|The recipient domain added your sending IP address to its custom blocklist.|The domain that received the email message blocked your sender's IP address. If you believe that your IP address was added to the recipient domain's custom blocklist by error, contact the recipient directly and ask them to remove it.|
103
103
|5.7.606-649|`Access denied, banned sending IP [IP1.IP2.IP3.IP4]`|The IP that you're trying to send from was banned.|Verify that you're following the [best practices for email deliverability](/dynamics365/marketing/get-ready-email-marketing), and make sure that your IP's reputations aren't degraded because of compromise or malicious traffic. If you believe that you're receiving this message in error, you can use the self-service portal to request that your IP address be removed from this list. <br/><br/> For more information, see [Use the delist portal to remove yourself from the blocked senders list](/microsoft-365/security/office-365-security/use-the-delist-portal-to-remove-yourself-from-the-office-365-blocked-senders-lis).|
104
104
|5.7.703|`Your message can't be delivered because messages to XXX, YYY are blocked by your organization using Tenant Allow Block List.`|Someone in your organization sent mail to an email address or domain that's blocked in the [Tenant Allow/Block List](/microsoft-365/security/office-365-security/tenant-allow-block-list-about#block-entries-in-the-tenant-allowblock-list). The whole message is blocked for all internal and external recipients of the message, even if only one recipient email address or domain is defined in a block entry.|
105
-
|5.7.705 <br/><br/> 5.7.708|`5.7.705 Access denied, tenant has exceeded threshold`, `5.7.708 Access denied, traffic not accepted from this IP`|Most of the traffic from this tenant is detected as suspicious. Therefore, a ban is put on the sending ability of the tenant.|Make sure that any compromises or open relays were resolved, and then contact support through your regular channel. <br/><br/> For more information, see [Fix email delivery issues for error codes 5.7.700 through 5.7.750 in Exchange Online](fix-error-code-5-7-700-through-5-7-750.md).|
106
-
|5.7.750|`Service unavailable. Client blocked from sending from unregistered domains`|A suspicious number of messages from unprovisioned domains is coming from this tenant.|Add and validate any or all domains that you use to send email from Microsoft 365 or Office 365. <br/><br/> For more information, see [Fix email delivery issues for error codes 5.7.700 through 5.7.750 in Exchange Online](fix-error-code-5-7-700-through-5-7-750.md).|
105
+
|5.7.705 <br/><br/> 5.7.708|`5.7.705 Access denied, tenant has exceeded threshold`, `5.7.708 Access denied, traffic not accepted from this IP`|Most of the traffic from this tenant is detected as suspicious. Therefore, a ban is put on the sending ability of the tenant.|Make sure that any compromises or open relays were resolved, and then contact support through your regular channel. <br/><br/> For more information, see [Fix email delivery issues for error codes 5.7.700 through 5.7.750 in Exchange Online](https://support.microsoft.com/topic/f5675801-1846-4d1c-9599-5b4e26a9175d).|
106
+
|5.7.750|`Service unavailable. Client blocked from sending from unregistered domains`|A suspicious number of messages from unprovisioned domains is coming from this tenant.|Add and validate any or all domains that you use to send email from Microsoft 365 or Office 365. <br/><br/> For more information, see [Fix email delivery issues for error codes 5.7.700 through 5.7.750 in Exchange Online](/exchange/mail-flow-best-practices/non-delivery-reports-in-exchange-online/fix-error-code-5-7-700-through-5-7-750).|
107
107
|5.7.800|`Access denied, banned sender`|The EHLO, P1, or P2 sender domain of this message was banned because of detected spam activity.|To restore this domain's ability to send mail, contact Microsoft support.|
108
108
|n/a|`The message can't be submitted because the sender's submission quota was exceeded`|The user account exceeded the recipient rate limit (10,000 recipients per day).|The account was likely compromised. For more information, see [Fix email delivery issues for error 'the sender's submission quota was exceeded' in Exchange Online](fix-error-for-submission-quota-exceeded-in-exchange-online.md).|
0 commit comments