Ready electronic mail delivery problems for error code 550 five.7.ane in Exchange Online

  • Article
  • 9 minutes to read

Important

Mail flow rules are now bachelor in the new Exchange admin center. Effort it now!

Information technology's frustrating when you get an error after sending an email message. This topic describes what you lot can do if you encounter error code 5.7.i in a non-commitment report (too known as an NDR, bounce message, delivery status notification, or DSN). This information also applies to error codes 5.seven.0 through 5.seven.999.
Email user icon. I got this bounce bulletin. How do I fix this event? Email admin icon I'thou an email admin. How can I fix this upshot?

This data also applies to fault codes 5.seven.0 through v.7.999 in Commutation Online and Microsoft 365 or Office 365. There tin exist several causes for dsn error lawmaking 5.vii.i, for which solutions are provided later in this topic.

Why did I get this bounce bulletin?

Typically, this error indicates a security setting in your system or the recipient'southward organization is preventing your message from reaching the recipient. For example:

  • You lot don't accept permission to ship to the recipient.
  • The recipient is a group, and yous don't have permission to send to the group or ane of its subgroups.
  • Yous don't accept permission to send email through an email server that's between you and the recipient.
  • Your message was routed to the wrong electronic mail server.

I got this bounce bulletin. How do I fix this issue?

Typically, you can't fix the trouble yourself. Y'all'll need the recipient or the recipient's email admin to fix the configuration on their end. However, hither are some steps that you lot can effort:

  • If the recipient is external (outside of your organization): Contact the recipient (by telephone, in person, etc.) and inquire them to tell their e-mail admin nigh your email delivery problem. Their email admin might demand to reconfigure the recipient's mailbox and so information technology 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. Enquire the owner of the restricted group to grant you permission to transport messages to the grouping. If you don't know the grouping'south owner, you can detect 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 grouping name on the To line, then cull Contact.
    • Outlook on the web: Select the NDR, cull the group proper name on the To line, and and then choose Possessor.

  • If you're sending to a large distribution group: Groups with more than than v,000 members have the following restrictions automatically applied to them:

    • Letters sent to the grouping crave approval by a moderator.
    • Large messages tin't exist sent to the group. Still, senders of big letters volition receive a different NDR. For more information well-nigh large messages, see Distribution group limits.

    To resolve the issue, join the group, or ask the grouping'south possessor or moderator to corroborate your message. Refer them to the I'one thousand the possessor of a restricted group. What can I practise? section later on in this topic.

If none of the previous steps use or solve your issue, contact the recipient'south email administrator, and refer them to the I'k an e-mail admin. How tin I gear up this effect? section afterwards in this topic.

I'chiliad the possessor of a restricted group. What tin can I do?

If a bulletin 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, endeavour ane of the post-obit steps:

  • Remove the sender restriction: Change your group settings to unblock the sender in one of the following means:

    • Add the sender to the group'southward allowed senders list. Note that you must create a mail contact or a mail service user to stand for the external sender in your system.
    • If the sender is restricted considering they're external (outside your system), configure the group to accept messages from external senders.
    • If you've configured a mail service menstruation rule (also known a a transport rule) to restrict certain senders or groups of senders, you lot can modify the dominion to have messages from the sender.

  • Restrictions on large groups: Groups with more 5,000 members have the post-obit restrictions automatically applied:

    • Messages sent to the grouping crave blessing past a moderator.
    • Large messages can't be sent to the group (only yous'll receive a different NDR from this one if that'due south the issue). See Substitution Online Limits.

    To resolve the issue for the sender, approve their message, or add them to the group.

  • Managing distribution groups

    • Configure moderated recipients in Exchange Online
    • Create and manage distribution groups in Exchange Online

I'm an email admin. How tin can I prepare this issue?

If the steps in the earlier sections don't solve the upshot for the sender, the solution likely requires action by the recipient'south 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 letters from external senders, configure the recipient or your e-mail servers to accept messages from external or anonymous senders.

The recipient is a public folder in your Commutation Online organization

When the recipient is a postal service-enabled public folder in your Commutation Online organization, an external sender will receive an NDR with the following error code:

Remote Server returned '<xxxxxxxx> #5.7.1 smtp;550 v.7.1 RESOLVER.RST.AuthRequired; authentication required [Phase: CreateMessage]'

To configure the public binder to accept messages from external senders, follow these steps:

New EAC

  1. Open the Exchange admin heart (EAC). For more information, see Exchange admin middle in Substitution Online.

  2. Go to Public folders > Public folders.

  3. Choose a public folder from the listing, and then click Edit Edit icon..

    The screen on which the details of a public folder can be edited.

  4. Click Mail catamenia settings.

  5. Under Message Delivery Restrictions > Accept messages from, perform the following tasks:

    • Clear the check box for Crave that all senders are authenticated.
    • Select All senders.

    The screen on which the users configure all the senders to send messages to the public folder.

  6. Click Relieve.

Classic EAC

  1. Open up the Exchange admin eye (EAC). For more data, encounter exchange admin middle in exchange online.

  2. In the EAC, get to Public folders > Public folders > select the public binder from the listing, and so click Edit Edit icon.

    View public folders to help fix DSN 5.7.135.

  3. In the public folder properties dialog box that opens, become 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.

    Public folder delivery restrictions to help fix DSN 5.7.135.

  4. Click Save.

The sender is external and their source IP address is on Microsoft's blocklist

In this case, the NDR the sender receives would include information in the Diagnostics for administrators section similar to the following information:

5.7.1 Service unavailable; Client host [xxx.xxx.thirty.xxx] blocked using Blocklist 1; To asking removal from this list please forward this message to delist@messaging.microsoft.com

To remove the restriction on the sender's source e-mail system, forward the NDR message to delist@messaging.microsoft.com. Likewise see Apply the delist portal to remove yourself from the blocked senders list.

Your domain isn't fully enrolled in Microsoft 365 or Office 365

If your domain isn't fully enrolled in Microsoft 365 or Office 365, try the post-obit steps:

  • Verify your domain appears as Good for you in the Microsoft 365 admin heart at Settings > Domains.
  • For information about calculation your domain to Microsoft 365 or Office 365, run across Add a domain to Microsoft 365.
  • To troubleshoot domain verification problems, see Microsoft Noesis Base article KB2515404.

Your domain's MX record has a problem

If you lot have an wrong MX record, try the following steps:

  1. Bank check the sender and recipient domains for incorrect or stale MX records by using the Advanced diagnostics > Commutation Online examination in the Microsoft Back up and Recovery Banana. For more information about the Back up and Recovery Banana, run into Virtually the Microsoft Support and Recovery Assistant.

  2. Check with your domain registrar or DNS hosting service to verify the MX tape for your domain is correct. The MX record for a domain that's enrolled in Substitution Online uses the syntax <domain\ >.mail.protection.outlook.com.

  3. Verify Inbound SMTP Email and Outbound SMTP Email at Office 365 > Mail Flow Configuration in the Microsoft Remote Connectivity Analyzer.

  4. Verify y'all accept just 1 MX record configured for your domain. Microsoft doesn't back up using more than one MX record for a domain that's enrolled in Substitution Online.

Your domain's SPF tape 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 than information, come across Fix SPF to help preclude spoofing.

Hybrid configuration bug

  • If your domain is role of a hybrid deployment betwixt on-premises Exchange and Exchange Online, the Hybrid Configuration Magician should automatically configure the required connectors for mail menses. All the same, you tin can utilise the steps in this department to verify the connector settings.

    1. Open the Microsoft 365 admin eye at https://portal.microsoftonline.com, and click Admin > Exchange.

    2. In the Exchange admin center, click Mail service Flow > Connectors. Select the connector that's used for hybrid, and choose Edit. Verify the post-obit information:

      • Commitment: 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 power to transport mail from your Exchange Online organization by using the Outbound SMTP Email examination in the Microsoft Remote Connectivity Analyzer.

      • Scope: If you need to route inbound internet mail to your on-premises Substitution organization, Domains demand to include all email domains that are used in your on-premises organization. You tin can utilize the value asterisk (*) to also road all outbound internet mail through the on-premises organization.

    If the connectors are configured incorrectly, your Commutation ambassador needs to rerun the Hybrid Configuration Magician in the on-premises Exchange organization.

  • If you disable an on-bounds Agile Directory business relationship, you'll become the post-obit mistake message:

    Your message couldn't be delivered to the recipient considering you don't have permission to send to information technology. Ask the recipient's email admin to add y'all to the accept list for the recipient. For more data, come across DSN 5.7.129 Errors in Exchange Online and Microsoft 365 or Part 365.

    To cease all communication with the Substitution Online mailbox, you demand to delete the on-premises user business relationship instead of disabling it.

    Another solution would exist to remove the license, only so you would need to create a mail flow rule (also known as a transport rule) to prevent the user from receiving electronic mail messages. Otherwise, the user would continue to receive messages for about 30 days later removal of the license.

    Consider this scenario as function of the workflow for disabling a user on Exchange Online.

Notwithstanding demand help?

Get help from the community forums.

Admins: Sign in and create a service request.

Admins: Call Support.

Run across too

Email non-delivery reports in Commutation Online