Fix email commitment issues for error code 550 5.7.ane in Exchange Online

  • Commodity
  • 9 minutes to read

Important

Mail period rules are at present available in the new Exchange admin center. Endeavor it at present!

It'southward frustrating when you become an fault after sending an electronic mail message. This topic describes what you tin can do if you come across error lawmaking 5.7.1 in a non-delivery study (also known as an NDR, bounciness message, delivery status notification, or DSN). This information also applies to mistake codes five.7.0 through 5.7.999.

Icon Message Icon Message
Email user icon. I got this bounce message. How do I fix this issue? Email admin icon I'm an email admin. How can I fix this issue?

This information also applies to error codes 5.7.0 through v.vii.999 in Commutation Online and Microsoft 365 or Office 365. In that location can be several causes for dsn error lawmaking 5.7.1, for which solutions are provided later in this topic.

Why did I become this bounciness message?

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

  • You don't have permission to transport to the recipient.
  • The recipient is a grouping, and y'all don't have permission to send to the group or one of its subgroups.
  • You don't take permission to send email through an email server that'due south betwixt you lot and the recipient.
  • Your message was routed to the wrong electronic mail server.

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

Typically, you lot tin can't prepare the trouble yourself. Y'all'll need the recipient or the recipient's email admin to ready the configuration on their stop. However, here are some steps that y'all can try:

  • If the recipient is external (outside of your organisation): Contact the recipient (past phone, in person, etc.) and ask them to tell their email admin about your email commitment problem. Their e-mail admin might need to reconfigure the recipient's mailbox and so information technology accepts email from y'all.

  • 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 ship to. Enquire the owner of the restricted grouping to grant yous permission to send messages to the grouping. If you lot don't know the group's owner, you lot tin find information technology in Outlook or Outlook on the web (formerly known as Outlook Web App) past doing the following steps:

    • Outlook: Select the NDR, double-click the group name on the To line, and and so choose Contact.
    • Outlook on the web: Select the NDR, choose the group name on the To line, and and so choose Owner.

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

    • Letters sent to the grouping crave approval by a moderator.
    • Large messages can't be sent to the grouping. Withal, senders of big messages will receive a different NDR. For more information virtually large messages, encounter Distribution group limits.

    To resolve the upshot, bring together the group, or ask the grouping's possessor or moderator to approve your bulletin. Refer them to the I'm the owner of a restricted group. What can I do? section afterwards in this topic.

If none of the previous steps employ or solve your consequence, contact the recipient's email administrator, and refer them to the I'thousand an email admin. How can I fix this event? department later in this topic.

I'chiliad the possessor of a restricted grouping. What can I practice?

If a bulletin sender received this NDR when they attempted to ship a bulletin to your group, and y'all want them to successfully send messages to your group, try 1 of the following steps:

  • Remove the sender restriction: Change your group settings to unblock the sender in 1 of the following ways:

    • Add together the sender to the grouping's allowed senders listing. Annotation that you lot must create a post contact or a mail user to represent the external sender in your organization.
    • 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 menses rule (also known a a transport rule) to restrict certain senders or groups of senders, y'all tin can modify the dominion to accept messages from the sender.

  • Restrictions on big groups: Groups with more than than five,000 members have the post-obit restrictions automatically applied:

    • Letters sent to the grouping crave approval by a moderator.
    • Large messages tin't be sent to the grouping (merely you'll receive a different NDR from this one if that'due south the upshot). Come across Exchange Online Limits.

    To resolve the issue for the sender, corroborate their message, or add them to the grouping.

  • Managing distribution groups

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

I'1000 an email admin. How can I fix this issue?

If the steps in the before sections don't solve the outcome 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 system)

If only this recipient is having difficulty accepting messages from external senders, configure the recipient or your email servers to have messages from external or bearding senders.

The recipient is a public binder in your Commutation Online organization

When the recipient is a mail-enabled public folder in your Exchange Online organization, an external sender volition receive an NDR with the post-obit error code:

Remote Server returned '<xxxxxxxx> #5.vii.1 smtp;550 5.vii.1 RESOLVER.RST.AuthRequired; authentication required [Stage: CreateMessage]'

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

New EAC

  1. Open up the Exchange admin center (EAC). For more information, see Exchange admin center in Exchange Online.

  2. Get to Public folders > Public folders.

  3. Choose a public folder from the list, so click Edit Edit icon..

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

  4. Click Mail period settings.

  5. Nether Message Delivery Restrictions > Accept letters 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 the Exchange admin center (EAC). For more information, see exchange admin center in exchange online.

  2. In the EAC, go to Public folders > Public folders > select the public folder from the list, and then click Edit Edit icon.

    View public folders to help fix DSN 5.7.135.

  3. In the public folder properties dialog box that opens, get to Mail menstruation settings, and configure the following settings in the Accept messages from department:

    • 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 example, 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 [thirty.xxx.thirty.xxx] blocked using Blocklist 1; To request removal from this list please forward this message to delist@messaging.microsoft.com

To remove the brake on the sender'south source email system, forrard the NDR message to delist@messaging.microsoft.com. Likewise run into Use the delist portal to remove yourself from the blocked senders listing.

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 following steps:

  • Verify your domain appears as Good for you in the Microsoft 365 admin eye at Settings > Domains.
  • For data nigh adding your domain to Microsoft 365 or Office 365, see Add a domain to Microsoft 365.
  • To troubleshoot domain verification issues, see Microsoft Knowledge Base article KB2515404.

Your domain's MX record has a problem

If you take an wrong MX record, attempt the following steps:

  1. Check the sender and recipient domains for incorrect or stale MX records by using the Avant-garde diagnostics > Exchange Online test in the Microsoft Support and Recovery Assistant. For more than information most the Support and Recovery Assistant, see About 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'southward enrolled in Exchange Online uses the syntax <domain\ >.post.protection.outlook.com.

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

  4. Verify you accept only i MX record configured for your domain. Microsoft doesn't back up using more than than ane MX record for a domain that's enrolled in Commutation Online.

Your domain'southward SPF record has a problem

The Sender Policy Framework (SPF) record for your domain might exist incomplete, and might not include all email sources for your domain. For more than information, come across Gear up SPF to help preclude spoofing.

Hybrid configuration issues

  • If your domain is function of a hybrid deployment between on-premises Exchange and Exchange Online, the Hybrid Configuration Wizard should automatically configure the required connectors for mail service flow. Notwithstanding, you can use the steps in this section 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 Flow > Connectors. Select the connector that's used for hybrid, and choose Edit. Verify the following information:

      • Delivery: If Road 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 right mail server.

        You lot tin can examination your MX tape and your power to send mail service from your Commutation Online system by using the Outbound SMTP Email test in the Microsoft Remote Connectivity Analyzer.

      • Scope: If y'all demand to route inbound internet mail to your on-bounds Exchange arrangement, Domains need 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 service through the on-bounds organization.

    If the connectors are configured incorrectly, your Commutation administrator needs to rerun the Hybrid Configuration Wizard in the on-premises Commutation system.

  • If you disable an on-premises Active Directory account, you lot'll get the following error message:

    Your message couldn't exist delivered to the recipient because you don't accept permission to transport to information technology. Ask the recipient's e-mail admin to add you to the have list for the recipient. For more than information, see DSN five.7.129 Errors in Exchange Online and Microsoft 365 or Office 365.

    To terminate all advice with the Exchange Online mailbox, yous need to delete the on-premises user account instead of disabling it.

    Another solution would exist to remove the license, but then you would need to create a post flow rule (also known as a send rule) to prevent the user from receiving email messages. Otherwise, the user would continue to receive messages for about xxx days after removal of the license.

    Consider this scenario as part of the workflow for disabling a user on Commutation Online.

Even so need help?

Get help from the community forums.

Admins: Sign in and create a service request.

Admins: Call Support.

See besides

Electronic mail non-commitment reports in Commutation Online