Why Microsoft 365 and Outlook.com reject mail with 550 5.7.509 when your domain fails DMARC with p=reject, how to read dmarc=fail action=oreject, and how to fix alignment or safely accept forwarded mail.
Home › Guides › 550 5.7.509 DMARC reject
Last updated 18 November 2026
The bounce reads, in Microsoft's NDR reference:
5.7.509 Access denied, sending domain [$SenderDomain] does not pass DMARC verification and has a DMARC policy of reject.
The domain in the visible From address (the 5322.From) publishes p=reject, the message failed DMARC, and the receiving Microsoft 365 organization honors the sender's policy, which Microsoft made the default in a change announced on 19 July 2023. The fix is almost always on the sending side: make SPF or DKIM pass and align with the From domain for that sender. If the failing mail was forwarded to you, the receiving admin can trust the forwarder instead.
p=reject) or quarantines (p=quarantine) as instructed. Admins can choose other actions in anti-phishing policies.p=reject or p=quarantine, "we will reject the email." So lowering your policy to quarantine does not stop the rejection there.550 5.7.509: Access denied, sending domain contoso.com does not pass DMARC verification and has a DMARC policy of reject. Microsoft's DMARC setup article summarises the same case as "Rejected during SMTP (550 5.7.1)", so check the text, not only the number.Microsoft includes the original headers in the NDR returned to the sender. Paste them into the Email Header Analyzer and find Authentication-Results. Microsoft's example of a message where SPF and DKIM pass but neither aligns:
Authentication-Results: spf=pass (sender IP is 198.51.100.10) smtp.mailfrom=bounces.adatum.com; dkim=pass (signature was verified) header.d=adatum.com; dmarc=fail action=oreject header.from=contoso.com;compauth=fail reason=000
| Action value | Meaning (Microsoft Learn) |
|---|---|
action=none | Sender published p=none; no action taken |
action=quarantine | Sender published p=quarantine; message quarantined or junked |
action=oreject | Sender published p=reject; message rejected ("o" = origin) |
action=pct.quarantine / action=pct.reject | Policy with pct= below 100; this message was in the sampled percentage |
Compare smtp.mailfrom= and header.d= with header.from=. DMARC passes when at least one of SPF or DKIM passes and its domain aligns with the From domain. RFC 7489 makes relaxed alignment the default (adkim and aspf default to r), so bounces.contoso.com aligns with contoso.com but adatum.com does not.
Microsoft lists three reasons DMARC fails: missing or incorrect DMARC/DNS records (alignment issues, missing SPF, policy issues), missing DKIM (no public key in DNS, or the message isn't signed), and forwarding that breaks SPF or DKIM. Its diagnostic steps:
bounces.contoso.com instead of bounces.adatum.com. Add the service to that domain's SPF with the SPF Record Builder and confirm it with the SPF Record Checker.d=contoso.com: publish the keys it gives you and turn on custom DKIM signing. Check the selector with the DKIM Checker. Microsoft notes that forwarding breaks SPF alignment, while DKIM breaks only when the body is changed.sub.contoso.com, publish a separate DMARC record for it, and have the service sign with d=sub.contoso.com.p=reject before every sender was aligned, follow the p=none to p=reject rollout to find the rest.If your users need mail that legitimately fails DMARC, usually because it passes through a forwarder or mailing list, Microsoft lists these options (the first is preferred):
Check what your tenant does in Exchange Online PowerShell:
Get-AntiPhishPolicy | Format-List Name, HonorDmarcPolicy, DmarcQuarantineAction, DmarcRejectAction Get-ArcConfig | Format-List ArcTrustedSealers
In the anti-phishing policy, Honor DMARC record policy when the message is detected as spoof offers Quarantine the message or Reject the message for p=reject. If your MX points to a non-Microsoft service in front of Microsoft 365, the Honor DMARC policy setting is applied only when Enhanced Filtering for Connectors is enabled on the inbound connector. Check where your MX points with the MX Record Lookup.
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).
Decode the NDR headers with the Email Header Analyzer, check the record with the DMARC Record Checker, read rua reports in the DMARC Report Analyzer, check SPF with the SPF Record Checker and DKIM with the DKIM Checker, and check everything at once with the Email Deliverability Checker. Related guides: DMARC fail with SPF pass, DMARC fail after forwarding, Microsoft 365 compauth=fail, DMARC for Microsoft 365 and Outlook.com 550 5.7.515.
The sending domain in the From address failed DMARC and publishes p=reject, so the Microsoft 365 or Outlook.com recipient rejected the message as the sender asked. The sender has to make SPF or DKIM pass and align with the From domain.
DMARC also needs alignment. If smtp.mailfrom or the DKIM d= domain is the sending service's domain rather than yours, SPF or DKIM can pass while DMARC fails. Change the MAIL FROM domain at the service, or have it sign DKIM with your domain.
Not at Outlook.com consumer mailboxes: Microsoft says it rejects mail that fails DMARC when the policy is p=reject or p=quarantine. At Microsoft 365 organizations quarantine sends mail to junk or quarantine instead. Fix alignment rather than weakening the policy.
It is how Microsoft 365 records that the message failed DMARC and the sender published p=reject, so the message was rejected. Microsoft documents the o as meaning origin.
Microsoft prefers adding the forwarding service as a trusted ARC sealer. Other options are a mail flow rule matching both sender IP and domain to skip spam filtering, or a temporary Tenant Allow/Block List entry that expires after 30 days.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.