The receiving system checks SPF and rejects mail that fails it, and the server that sent this message is not authorised by the sender domain’s SPF record.
550 5.7.23 The message was rejected because of Sender Policy Framework violation
1 other wording of the same rejection
Outlook.com, older wording (the domain publishes v=spf1 -all):
550 command rejected due to Sender ID validation failure.
Check your domain’s SPF, DKIM and DMARC
Enter the domain in your From address. We read its records the way Microsoft 365 and Outlook.com does.
What it means
This appears both when mail to a Microsoft 365 recipient fails SPF and when a Microsoft 365 tenant’s own outbound mail fails SPF at another receiver.
Microsoft adds one cause people rarely think of: outbound mail classed as spam is sent through its High Risk Delivery Pool, whose servers will never pass your SPF record.
Why it happens
- The sending server or service is not in the SPF record.
- On-premises servers sending through Microsoft 365 whose addresses are not in SPF.
- A domain sent from that was never added and verified in the tenant.
- Outbound mail flagged as spam and sent through the High Risk Delivery Pool.
How to fix it
- Check your SPF record below and add the missing sender (include:spf.protection.outlook.com for Microsoft 365).
- Add on-premises sending addresses to SPF, and add every domain you send from to the tenant.
- If outbound mail is being classed as spam, fix that first — SPF cannot pass from the High Risk Delivery Pool.
Microsoft 365 SPF and DKIM setup →
Sources
Message text and meaning checked on 25 September 2026 against these official sources:
- Fix NDR error 5.7.23 in Exchange Online — learn.microsoft.com
- Troubleshooting — substrate.office.com