Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 550 5.7.1

550 5.7.1 in Exchange: the receive connector refuses to relay your mail

9 min read Updated October 5, 2026 Exchange Server

Fix it now

The device connected, sent its message, and was told it has no permission to relay. Microsoft publishes 5.7.1 Unable to relay for exactly this: a sending system trying to reach a destination the receiving system is not the final stop for. The fix is a permission on a connector scoped to that sender, not a firewall change.

Run these in the Exchange Management Shell, in order, substituting your own device addresses

Get-ReceiveConnector | Format-List Identity,Bindings,RemoteIPRanges,PermissionGroups,AuthMechanism

New-ReceiveConnector -Name "Anonymous Relay" -TransportRole FrontendTransport -Custom -Bindings 0.0.0.0:25 -RemoteIpRanges 10.10.20.15,10.10.20.16

Set-ReceiveConnector "Anonymous Relay" -PermissionGroups AnonymousUsers

Get-ReceiveConnector "Anonymous Relay" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"
  1. Confirm the sender is actually relaying – sending to a domain Exchange is not authoritative for. Mail to your own accepted domains needs no relay right at all.
  2. Work out which connector the session lands on. Exchange picks the connector whose remote IP range most specifically matches the source address, so a single address beats a range and a range beats the whole internet.
  3. Never add the relay right to a default connector. Default Frontend is bound to port 25 for every address on the internet; granting relay there makes the server an open relay.
  4. Test from the sending host, then confirm the message in the message tracking log and read the receive protocol log to check which connector handled the session.

If the application can authenticate, do that instead: point it at the client submission port, 587, where the Client Frontend connector accepts authenticated submission and no anonymous permission is needed.

If the device now relays and nothing else can, that is the job. If you are seeing 530 or 504 rather than 550, the next section separates a relay refusal from an authentication one.

Why it happens

Microsoft publishes three distinct meanings behind the enhanced status code 5.7.1, and the trailing text tells you which one you have. Unable to relay is the sending system trying to send to a system that is not the message’s final destination – the classic relay refusal. Delivery not authorized is the sender not being permitted to send to that recipient, which covers a restricted distribution group and a transport rule rejection. Client was not authenticated is the receiving system requiring authentication before submission and not getting it.

Every inbound SMTP session lands on exactly one receive connector, chosen by matching the client’s address against the remote IP ranges of the connectors bound to that port. Microsoft documents that overlapping ranges are allowed as long as one is fully contained in another, and that the most specific match wins. That is the mechanism that makes a dedicated relay connector safe: only the addresses you list will ever use it, and everything else continues to land on Default Frontend with no relay rights.

Once the connector is chosen, its permissions decide what the session may do. Accepting mail for your own accepted domains is ordinary inbound mail and needs no special right. Accepting mail addressed anywhere else is relaying, and Microsoft names the minimum permission set for it: ms-Exch-Accept-Headers-Routing, ms-Exch-SMTP-Accept-Any-Recipient, ms-Exch-SMTP-Accept-Any-Sender, ms-Exch-SMTP-Accept-Authoritative-Domain-Sender and ms-Exch-SMTP-Submit. The AnonymousUsers permission group supplies most of that; the accept-any-recipient right is the one you have to add, and it is exactly the one an anonymous connector does not get by default.

The session lands on a default connector

You have this one if The sending host’s address is not listed in the remote IP ranges of any dedicated connector.

  1. List the connectors and their ranges, and work out which one most specifically matches the sender.
  2. Create a dedicated connector listing only the addresses that need to relay.
  3. Leave the default connectors alone. Default Frontend exists to accept anonymous mail from the internet for your own domains, and adding relay to it turns the server into an open relay.

The right connector is selected but lacks the relay right

You have this one if Anonymous connections are accepted, mail to internal recipients works, and only external recipients are refused.

  1. Read the current rights: Get-ADPermission "Anonymous Relay" -User "NT AUTHORITY\ANONYMOUS LOGON" | Format-List User,ExtendedRights
  2. Confirm the PermissionGroups value includes AnonymousUsers, then add the accept-any-recipient extended right as shown above.
  3. Retest from the device rather than from the server console, because the connector is chosen by the client’s address.

The application should be authenticating and is not

You have this one if 530 5.7.1 rather than 550, or the application is pointed at port 587 with no credentials.

  1. Give the application a mailbox account and point it at the client submission port, 587, where the Client Frontend connector accepts authenticated submission.
  2. Confirm the connector offers an authentication mechanism the application supports.
  3. Devices that cannot negotiate TLS or authenticate at all need the anonymous route with an IP-scoped connector instead.

It is a policy rejection rather than a relay refusal

You have this one if The trailing text reads Delivery not authorized, or the rejection is on mail to internal recipients only.

  1. Check whether a transport rule is rejecting the message, and read the rule’s action.
  2. For a distribution group, check whether it requires all senders to be authenticated, which blocks anonymous internal submission to that group.
  3. Turn on verbose protocol logging on the connector and read the session in the receive protocol log. It shows the exact command that was refused.

Full reference

Which response you got, and what it says

Response Published meaning
550 5.7.1 Unable to relay The sending system is not allowed to send to a system that is not the final destination
5.7.1 Delivery not authorized The sender is not allowed to send to that recipient – a restricted group or a transport rule
5.7.1 Client was not authenticated The receiving system requires authentication before submission
504 5.7.4 Not published by Microsoft. RFC 3463 defines the class as security features, such as secure authentication, that the delivery protocol cannot support

The default connectors, and why they matter here

Connector Port What it is for
Default Frontend 25 Anonymous connections from external SMTP servers
Client Frontend 587 Authenticated SMTP client submission
Outbound Proxy Frontend 717 Authenticated connections from the Transport service
Client Proxy 465 Authenticated client connections proxied from the Front End service
Default 2525 Authenticated connections between internal servers

A device pointed at port 25 with no credentials lands on Default Frontend unless a more specific connector exists for its address. Default Frontend accepts anonymous connections from the whole internet, which is exactly why it must never carry the accept-any-recipient right, and exactly why the fix is a new connector rather than an edit to that one.

The five rights Microsoft names for anonymous relay

  • ms-Exch-Accept-Headers-Routing
  • ms-Exch-SMTP-Accept-Any-Recipient
  • ms-Exch-SMTP-Accept-Any-Sender
  • ms-Exch-SMTP-Accept-Authoritative-Domain-Sender
  • ms-Exch-SMTP-Submit

Setting PermissionGroups to AnonymousUsers grants the surrounding set; the accept-any-recipient right is added separately with Add-ADPermission. If you are auditing a connector somebody else built, compare its Get-ADPermission output against that list rather than against a memory of what should be there.

Two supported routes, and when to use each

Anonymous, IP-scoped connector Authenticated submission
Port 25 on a dedicated connector 587, Client Frontend
Identity None; the source address is the control A mailbox account
Survives an address change No – the connector lists addresses Yes
Suits Printers, scanners, appliances that cannot authenticate Applications that can
Audit trail Connector and protocol logs The submitting account, in message tracking

Never grant the accept-any-recipient right on a connector whose remote IP range covers everything. That is the definition of an open relay. Microsoft’s own wording is that open relay servers are eagerly sought out and used by spammers, and the reputation damage outlasts the mistake by months. Scope every relay connector to named addresses.

Proving the scope as well as the fix

  1. Send a test message from the device’s own host to an external address and confirm it is accepted.
  2. Find it in the message tracking log and confirm it was received and queued.
  3. Read the receive protocol log for that session and confirm the connector used was the dedicated one, not a default.
  4. From a host outside the connector’s remote IP ranges, attempt the same relay and confirm it is still refused. This is the step people skip, and it is the one that proves you have not opened a relay.

Every code this article covers

Code What it points at Source
550 5.7.1 Unable to relay: the sending system is not allowed to send to a system that is not the message’s final destination Microsoft Learn
554 5.7.1 Microsoft publishes the enhanced code 5.7.1 Delivery not authorized – a restricted recipient or a transport rule – but not the 554 prefix separately Microsoft Learn
530 5.7.1 Client was not authenticated: the receiving system requires authentication before message submission Microsoft Learn
504 5.7.4 Not published by Microsoft. RFC 3463 defines the X.7.4 class as a message containing security features, such as secure authentication, that the delivery protocol cannot support RFC 3463

Confirm the fix worked

  1. A test message from the device’s own host reaches an external address.
  2. The message tracking log shows it received and queued.
  3. The receive protocol log for that session names the dedicated connector.
  4. A host outside the connector’s remote IP ranges is still refused when it attempts to relay.
  5. Get-ADPermission on the dedicated connector shows the accept-any-recipient right on the anonymous account, and no default connector has it.

Questions people ask about this

Why not just allow anonymous relay on the default connector?

Because Default Frontend accepts connections from any address on the internet. Adding relay rights to it makes the server an open relay, which will be found and abused quickly.

Should the application authenticate instead?

Where it can, yes. Authenticated submission on port 587 is easier to audit, does not depend on IP addresses staying the same, and survives a network change. Reserve the anonymous IP-scoped connector for devices that genuinely cannot authenticate.

Does this need a licence or a CAL?

No. Receive connectors and their permissions are part of Exchange Server. This is configuration and nothing about it is gated behind a purchase.

How does Exchange decide which connector handles a session?

By the remote IP ranges of the connectors bound to that port. Overlapping ranges are allowed as long as one is fully contained in another, and the most specific match to the connecting address wins.

The same application gets a similar refusal from Microsoft 365. Same fix?

No. On-premises this is a connector permission. In the hosted service the equivalent is one of three documented options – authenticated client submission, direct send, or an SMTP relay connector – and the refusals carry different codes.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error 452 4.3.1 insufficient system resources: Exchange back pressure explained Free Fix Event ID 7024 and Event ID 4999: Exchange services crash or refuse to start License Error Event ID 9646: a client blew past the Exchange session or object limit License Error Event ID 1069 and Event ID 1146: cluster faults that take a whole DAG offline
โ† Back to Knowledge Base