The recipient is on Microsoft 365. Your domain’s DMARC policy is p=reject, and this message failed DMARC — neither SPF nor DKIM passed for your domain — so Exchange Online did what your policy asked and refused it.
550 5.7.509 Access denied, sending domain [example.com] does not pass DMARC verification and has a DMARC policy of reject.
Your bounce names your own domain and sending address where this one says example.com and 203.0.113.5.
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
Microsoft names three reasons: DMARC or SPF records that are missing, wrong or not aligned; DKIM missing (no public key, or the message is not signed); and forwarding that broke SPF or DKIM on the way.
The bounce usually returns the message’s Authentication-Results header, which says which of SPF, DKIM and DMARC failed.
Why it happens
- A sending service not authenticated for your domain.
- Mail forwarded or relayed through a gateway that broke the DKIM signature, with SPF failing at the next hop.
- A DKIM key missing from DNS after a change of provider.
How to fix it
- Read the Authentication-Results in the bounce to see which check failed.
- Check your domain below, then set up DKIM for your domain in the service that sent the message.
- Until every legitimate sender passes, consider p=quarantine rather than reject — and read DMARC reports to find them.
Email setup guides for each sending service →
Sources
Message text and meaning checked on 25 September 2026 against these official sources:
- Email nondelivery reports (NDRs) and SMTP errors in Exchange Online — learn.microsoft.com