Fix Exchange Online 550 5.7.1: Delivery Not Authorized, Unable to Relay or Client Not Authenticated

What Exchange Online 550 5.7.1 means (delivery not authorized, unable to relay, client was not authenticated), how restricted groups, public folders, blocklists, MX, SPF and hybrid connectors cause it, and the fix for each.

Home › Guides › Exchange Online 550 5.7.1

Last updated 17 November 2026

Quick answer

Microsoft's article on NDR 550 5.7.1 says the error typically means a security setting in your organization or the recipient's organization is preventing your message from reaching the recipient, and that the same information applies to codes 5.7.0 through 5.7.999. Microsoft's examples:

The Exchange Online NDR reference lists three different texts for 5.7.1:

TextWhat Microsoft says it means
Delivery not authorizedThe sender isn't allowed to send messages to the recipient. Often a distribution group that accepts messages only from members or other authorized senders. A mail flow (transport) rule that rejects the message can also cause it.
Unable to relayThe sending system tried to send an anonymous message to a system that doesn't accept mail for the recipient's domain: spam relay attempts, an MX record pointing to a system that doesn't accept the domain, or a client or server without permission to relay.
Client was not authenticatedThe receiving system requires authentication before message submission and the sender didn't authenticate.

Step 1: Find which server rejected the message

Open the NDR and read Diagnostic information for administrators. Microsoft's NDR reference uses this example, where the user section says Your message wasn't delivered due to a permission or security issue. It might have been rejected by a moderator, the address might only accept email from certain senders, or another restriction might be preventing delivery. and the diagnostic line reads:

mail.contoso.com #<exchange.contoso.com #5.7.1 smtp;530 5.7.1 Client was not authenticated> #SMTP#

Here the server that rejected the message, mail.contoso.com, isn't a Microsoft 365 server, so the admins of that domain must fix it. Microsoft says this particular error means that server is configured not to accept anonymous email from the internet. The Received headers in the original message show the path and the last hop if the generating server isn't clear. Paste them into the Email Header Analyzer to read them.

Then match the diagnostic text against the documented variants:

Diagnostic textCause
NDR lists the names of restricted groupsYou don't have permission to send to the group or one of its subgroups.
550 5.7.1 RESOLVER.RST.AuthRequired; authentication required [Stage: CreateMessage]An external sender wrote to a mail-enabled public folder that only accepts authenticated senders.
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 delist@microsoft.comThe sender's source IP address is on Microsoft's blocklist.
Your message couldn't be delivered to the recipient because you don't have permission to send to it.One documented cause is a disabled on-premises Active Directory account in a hybrid setup.

If you sent the message

Microsoft says you typically can't fix this yourself; the recipient or their email admin has to change their configuration. What you can do:

If you own the restricted group

The same settings in Exchange Online PowerShell (parameters from the Set-DistributionGroup reference):

Set-DistributionGroup -Identity "Sales" -RequireSenderAuthenticationEnabled $false
Set-DistributionGroup -Identity "Sales" -AcceptMessagesOnlyFrom @{Add="partner-contact"}

$true for RequireSenderAuthenticationEnabled accepts only authenticated (internal) senders; $false accepts internal and external senders. When AcceptMessagesOnlyFrom (or AcceptMessagesOnlyFromSendersOrMembers) is blank, the group accepts messages from all senders. The 5.7.133 and 5.7.124 guide covers every group, mailbox and public folder restriction code.

If you're the recipient's email admin

One recipient rejects external senders

Configure the recipient to accept messages from external or anonymous senders. For a mailbox: Set-Mailbox -Identity <user> -RequireSenderAuthenticationEnabled $false, or in the EAC under the mailbox's Manage message delivery restriction, clear Require senders to be authenticated.

Mail-enabled public folder (RESOLVER.RST.AuthRequired)

In the EAC go to Public folders > Public folders, select the folder, choose Edit, then Mail flow settings. Under Message Delivery Restrictions > Accept messages from, clear Require that all senders are authenticated, select All senders and Save. The PowerShell equivalent is Set-MailPublicFolder -Identity <folder> -RequireSenderAuthenticationEnabled $false.

Sender IP on Microsoft's blocklist

The sender forwards the NDR to delist@microsoft.com, or uses Microsoft's delist portal to remove themselves from the blocked senders list.

Domain not fully enrolled

Check that the domain shows as Healthy in the Microsoft 365 admin center at Settings > Domains.

MX record problem

Incomplete SPF record

The SPF record might not include all email sources for the domain. Expand it with the SPF Record Checker and fix it with the SPF for Microsoft 365 guide.

Hybrid connectors

The Hybrid Configuration Wizard should create the connectors, but you can check them in the EAC under Mail flow > Connectors: edit the hybrid connector and confirm that Route mail through smart hosts has the right IP address or FQDN (or, with MX record associated with the recipient domain, that the MX points to the right server), and that the scope Domains include every domain used on-premises (* also routes all outbound internet mail on-premises). If the connectors are wrong, rerun the Hybrid Configuration Wizard.

Disabled on-premises account

Disabling an on-premises Active Directory account produces Your message couldn't be delivered to the recipient because you don't have permission to send to it. Microsoft says to delete the on-premises account instead of disabling it if you want to stop all mail to the Exchange Online mailbox. Removing the license also works, but then add a mail flow rule to stop delivery, because the user would otherwise keep receiving messages for about 30 days.

Audit hundreds of domains at once

Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).

Related tools and guides

Read the NDR and Received headers in the Email Header Analyzer, check MX with the MX Record Lookup, SPF with the SPF Record Checker and the whole domain with the Email Deliverability Checker, confirm the tenant with the M365 Tenant Lookup, look up a blocked IP with the ASN IP Lookup and keep cmdlets in the PowerShell Cheat Sheet. Related guides: Exchange Online 5.7.133 and 5.7.124, Exchange Online 5.7.57 (SMTP AUTH), Exchange Online 550 5.4.1, Exchange Online 550 5.1.10 and SPF for Microsoft 365.

FAQ

What does 550 5.7.1 mean in Exchange Online?

Microsoft says it typically means a security setting in your organization or the recipient's organization is preventing the message from reaching the recipient: no permission to send to the recipient or a group, no permission to relay through a server in between, or the message was routed to the wrong server.

Why do I get 5.7.1 Delivery not authorized when emailing a distribution group?

The group probably accepts messages only from members or other authorized senders, or from internal senders only. The NDR names the restricted groups. Ask the group owner to add you to the allowed senders list or to allow external senders.

How do I fix 550 5.7.1 RESOLVER.RST.AuthRequired?

It means an external sender wrote to a mail-enabled public folder that requires authenticated senders. In the EAC open Public folders, edit the folder, and under Mail flow settings, Accept messages from, clear Require that all senders are authenticated and select All senders.

What does 5.7.1 Unable to relay mean?

The sending system sent an anonymous message to a server that doesn't accept mail for the recipient's domain. Common causes are spam relay attempts, an MX record that points to a system where the domain isn't accepted, or a device or server that lacks permission to relay.

Why does a hybrid user bounce with you don't have permission to send to it?

Microsoft documents that disabling the on-premises Active Directory account causes this NDR. Delete the on-premises account instead, or remove the license and add a mail flow rule, because the mailbox can keep receiving mail for about 30 days.

Want the full kit?

Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.