Fix email delivery issues for error code 550 5.7.1 in Exchange Online
It's frustrating when you get an error after sending an email message. This topic describes what you can do if you see error code 5.7.1 in a non-delivery report (also known as an NDR, bounce message, delivery status notification, or DSN). This information also applies to error codes 5.7.0 through 5.7.999.
|I got this bounce message. How do I fix it?||I'm an email admin. How can I fix this?|
This information also applies to error codes 5.7.0 through 5.7.999 in Exchange Online and Office 365. There can be several causes for dsn error code 5.7.1, for which solutions are provided later in this topic.
Why did I get this bounce message?
Typically, this error indicates a security setting in your organization or the recipient's organization is preventing your message from reaching the recipient. For example:
You don't have permission to send to the recipient.
The recipient is a group, and you don't have permission to send to the group or one of its subgroups.
You don't have permission to send email through an email server that's between you and the recipient.
Your message was routed to the wrong email server.
I got this bounce message. How do I fix it?
Typically, you can't fix the problem yourself. You'll need the recipient or the recipient's email admin to fix the configuration on their end. However, here are some steps that you can try:
If the recipient is external (outside of your organization): Contact the recipient (by phone, in person, etc.) and ask them to tell their email admin about your email delivery problem. Their email admin might need to reconfigure the recipient's mailbox so it accepts email from you.
If the recipient is an internal group: You might not have permission to send to the group or to one of its subgroups. In this case, the NDR will include the names of the restricted groups that you don't have permission to send to. Ask the owner of the restricted group to grant you permission to send messages to the. If you don't know the group's owner, you can find it in Outlook or Outlook on the web (formerly known as Outlook Web App) by doing the following steps:
Outlook: Select the NDR, double-click the group name on the To line, and then choose Contact.
- Outlook on the web: Select the NDR, choose the group name on the To line, and then choose Owner.
If you're sending to a large distribution group: Groups with more than 5,000 members have the following restrictions automatically applied to them:
Messages sent to the group require approval by a moderator.
Large messages can't be sent to the group. However, senders of large messages will receive a different NDR. For more information about large messages, see Distribution group limits.
To resolve the issue, join the group, or ask the group's owner or moderator to approve your message. Refer them to the I'm the owner of a restricted group. What can I do? section later in this topic.
If none of the previous steps apply or solve your issue, contact the recipient's email administrator, and refer them to the I'm an email admin. How can I fix this? section later in this topic.
I'm the owner of a restricted group. What can I do?
If a message sender received this NDR when they attempted to send a message to your group, and you want them to successfully send messages to your group, try one of the following steps:
Remove the sender restriction: Change your group settings to unblock the sender in one of the following ways:
If the sender is restricted because they're external (outside your organization), configure the group to accept messages from external senders.
If you've configured a mail flow rule (also known a a transport rule) to restrict certain senders or groups of senders, you can modify the rule to accept messages from the sender.
Restrictions on large groups: Groups with more than 5,000 members have the following restrictions automatically applied:
Messages sent to the group require approval by a moderator.
Large messages can't be sent to the group (but you'll receive a different NDR from this one if that's the issue). See Exchange Online Limits.
To resolve the issue for the sender, approve their message, or add them to the group.
Managing distribution groups
I'm an email admin. How can I fix this?
If the steps in the earlier sections don't solve the issue for the sender, the solution likely requires action by the recipient's email admin. The scenarios and solutions are described in this section.
The sender is external (outside your organization)
If only this recipient is having difficulty accepting messages from external senders, configure the recipient or your email servers to accept messages from external or anonymous senders.
The recipient is a public folder in your Exchange Online organization
When the recipient is a mail-enabled public folder in your Exchange Online organization, an external sender will receive an NDR with the following error code:
Remote Server returned '<xxxxxxxx> #5.7.1 smtp;550 5.7.1 RESOLVER.RST.AuthRequired; authentication required [Stage: CreateMessage]'
To configure the public folder to accept messages from external senders, follow these steps:
Open the Exchange admin center (EAC). For more information, see Exchange admin center in Exchange Online.
In the EAC, go to Public folders > Public folders > select the public folder from the list, and then click Edit
In the public folder properties dialog box that opens, go to Mail flow settings, and configure the following settings in the Accept messages from section:
Clear the check box for Require that all senders are authenticated.
Select All senders.
The sender is external and their source IP address is on Microsoft's blocklist
In this cases, the NDR the sender receives would include information in the Diagnostics for administrators section similar to this:
5.7.1 Service unavailable; Client host [xxx.xxx.xxx.xxx] blocked using Blocklist 1; To request removal from this list please forward this message to firstname.lastname@example.org
To remove the restriction on the sender's source email system, forward the NDR message to email@example.com.
Your domain isn't fully enrolled in Office 365
If your domain isn't fully enrolled in Office 365, try the following steps:
Verify your domain appears as Active in the Microsoft 365 admin center at https://admin.microsoft.com.
For information about adding your domain to Office 365, see Domains in Office 365.
To troubleshoot domain verification issues, see Microsoft Knowledge Base article KB2515404.
Your domain's MX record has a problem
If you have an incorrect MX record, try the following steps:
Check the sender and recipient domains for incorrect or stale MX records by using the Advanced diagnostics > Exchange Online test in the Microsoft Support and Recovery Assistant for Office 365. For more information about the Support and Recovery Assistant, see Fix Outlook and Office 365 issues with Support and Recovery Assistant for Office 365.
Check with your domain registrar or DNS hosting service to verify the MX record for your domain is correct. The MX record for a domain that's enrolled in Exchange Online uses the syntax <domain>.mail.protection.outlook.com.
Verify MX Record and Outbound Connector Test at Office 365 > Mail Flow Configuration in the Microsoft Remote Connectivity Analyzer.
Verify you have only one MX record configured for your domain. Microsoft doesn't support using more than one MX record for a domain that's enrolled in Exchange Online.
Your domain's SPF record has a problem
The Sender Policy Framework (SPF) record for your domain might be incomplete, and might not include all email sources for your domain. For more information, see Set up SPF to help prevent spoofing.
Hybrid configuration issues
If your domain is part of a hybrid deployment between on-premises Exchange and Exchange Online, the Hybrid Configuration Wizard should automatically configure the required connectors for mail flow. Even so, you can use the steps in this section to verify the connector settings.
Open the Microsoft 365 admin center at https://portal.microsoftonline.com, and click Admin > Exchange.
In the Exchange admin center, click Mail Flow > Connectors. In the Outbound connectors section, select the connector that's used for hybrid, and choose Edit. Verify the following information:
Delivery: If Route mail through smart hosts is selected, confirm the correct IP address or FQDN is specified. If MX record associated with the recipient domain is selected, confirm the MX record for the domain points to the correct mail server.
You can test your MX record and your ability to send mail from your Exchange Online organization by using the Outbound SMTP Email test in the Microsoft Remote Connectivity Analyzer.
Scope: If you need to route inbound internet mail to your on-premises Exchange organization, Domains needs to include all email domains that are used in your on-premises organization. You can use the value asterisk (*) to also route all outbound internet mail through the on-premises organization.
If the connectors are configured incorrectly, your Exchange administrator needs to rerun the Hybrid Configuration Wizard in the on-premises Exchange organization.
If you disable an on-premises Active Directory account, you'll get the following error message:
Your message couldn't be delivered to the recipient because you don't have permission to send to it. Ask the recipient's email admin to add you to the accept list for the recipient. For more information, see DSN 5.7.129 Errors in Exchange Online and Office 365.
To cease all communication with the Exchange Online mailbox, you need to delete the on-premises user account instead of disabling it.
Another solution would be to remove the license, but then you would need to create a mail flow rule (also known as a transport rule) to prevent the user from receiving email messages. Otherwise, the user would continue to receive messages for about 30 days after removal of the license.
Consider this scenario as part of the workflow for disabling a user on Exchange Online.