Fix Exchange Online Connector Validation Success but Email Failure
Question details
Determine why Exchange Online connector validation succeeds while normal messages to an on-premises mail server fail.

- Product
- Exchange Online and an on-premises non-Exchange mail server
- Device & OS
- not provided
- Scenario
- Microsoft 365 sends messages through an outbound connector to an on-premises mail server.
- Observed behavior
- The validation message is delivered, but normal messages fail with SMTP error 553 5.7.1 stating that the sender is not logged in.
Have a failed message's non-delivery report, recipient address, and approximate send time available. Confirm that you have access to the Exchange admin center and the destination mail server's SMTP logs and configuration.
Compare connector scope and message routing
Use this approach to check whether validation and normal messages follow different connector routes.
In the Exchange admin center, go to Mail flow > Message trace and search for the failed message by sender, recipient, and time. Review the delivery details and the non-delivery report to identify where the rejection occurred.
Go to Mail flow > Connectors and inspect the enabled outbound connectors. Compare their recipient-domain scope, routing settings, and any mail flow rules that select a connector with the failed recipient's domain.
Connect to Exchange Online PowerShell with Connect-ExchangeOnline, then run Get-AcceptedDomain | Format-List and Get-OutboundConnector | Format-List. Compare accepted domains and connector settings with the intended mail route.
Correct any unintended connector scope or routing configuration, then send a normal test message to the affected recipient. Disable an unused connector only after confirming that no required mail flow depends on it.

Check SMTP acceptance on the destination mail server
Use this approach when the non-delivery report or server logs show that the on-premises server rejected the message.
Document Exchange Mail Flow Troubleshooting in WPS Office
WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format compatibility, making it easy to move existing troubleshooting documents and checklists. It does not change Exchange Online connectors or fix SMTP delivery.

Frequently Asked Questions
Why can connector validation succeed when a normal message fails?
The validation message and normal message may use different connector routes or be treated differently by the destination server. Compare connector scope under Exchange admin center > Mail flow > Connectors and inspect the failed message and SMTP logs.
What does SMTP error 553 5.7.1 mean in this case?
The destination server is rejecting the message under its SMTP policy, such as an authentication or relay restriction. Check the non-delivery report and destination SMTP logs for the exact command and reason.
How can I inspect Exchange Online connector settings in PowerShell?
Connect with Connect-ExchangeOnline, then run Get-OutboundConnector | Format-List to review outbound connectors and Get-AcceptedDomain | Format-List to inspect accepted domains.
Will adding an SPF record fix the 553 rejection?
Not necessarily. SPF helps receivers evaluate authorized sending sources, but a relay or authentication rejection may require changes to the destination server's inbound SMTP policy. Review its logs before changing DNS.




