What happens to failing mail under each policy
A DMARC policy is a request, so there's no single answer. p=none asks receivers not to change how they handle failing mail. p=quarantine asks them to treat it as suspicious, which in practice can mean a spam or Junk folder, an admin quarantine, or a flagged message. p=reject asks them to refuse it, usually during delivery. Each receiver makes the final call, and it can accept failing mail or filter mail that passes.
How quarantine and reject compare as policy choices is covered in our post on the difference between p=quarantine and p=reject. How DMARC reaches pass or fail in the first place is in What is DMARC and how it works. This article is about what happens next.
What the standard says
The final handling of any message is always a matter of local policy and is left to the discretion of the mail receiver. Within that:
- none: "no expression of preference." A receiver that finds
p=none"MUST NOT modify existing mail handling processes." Its other spam and phishing filters still run. - quarantine: the domain owner considers failing mail "suspicious. It is possible the mail is valid."
- reject: failures are "a clear indication that the use of the domain name is not valid."
Receivers may quarantine or reject mail that passes DMARC, and may accept mail that fails even at reject. They "MUST NOT reject incoming messages solely on the basis of a 'p=reject' policy," and without other knowledge they treat it as quarantine. When they deviate from your policy, they should say why in aggregate reports.
Two other things change the result. If t=y is set, receivers are asked to apply one level lower. Subdomains follow sp or np when those are set (Subdomain policy (sp)).
What does DMARC quarantine do?
It depends on who receives the message.
- Google says it will "mark the messages as spam and send it to the recipient's spam folder".
- Microsoft, describing what destination systems do in general, says a quarantined message "might be quarantined as spam, delivered to the Junk Email folder, or delivered to the Inbox with an identifier added to the Subject or message body".
- Microsoft 365 as a receiver follows each tenant's Honor DMARC record policy setting. When it's on (Microsoft's recommended setting), mail failing at
p=quarantinegoes to the Junk Email folder (configurable to an admin quarantine). The anti-phishing policy lets the tenant choose between those two actions.
An admin quarantine isn't the same as a Junk folder. Depending on the tenant's quarantine policy, the recipient may not see the message unless it's released.
What happens at reject
A receiver that acts on reject typically refuses the message in the SMTP session, so the sending server gets an error such as 550 5.7.1 Email rejected per DMARC policy for example.com and the sender usually gets a bounce. A silent discard is also possible, where the server accepts the message and then drops it, so a bounce isn't guaranteed.
- Google says the receiving server "usually sends a bounce message" in one table and "should send" one in another, on the same page.
- Microsoft says rejected messages "are typically discarded," and that what happens "depends on the destination email system."
- Microsoft 365 as a receiver, with Honor DMARC record policy on, documents a rejection during SMTP (
550 5.7.1, withdmarc=fail action=orejectin the headers) in its Set up DMARC summary. The anti-phishing policy also lets the tenant choose to quarantine that mail instead of rejecting it. More on Microsoft in Microsoft and Outlook authentication rules.
What happens at none
Nothing changes because of DMARC. Microsoft's summary for p=none says "No DMARC-specific action. Other filtering still applies." So spoofed mail can still be caught by other filters, and your legitimate mail can still land in spam for unrelated reasons (Authentication vs inbox placement).
Forwarded and mailing-list mail
Legitimate mail that goes through a forwarder or list can fail DMARC. Receivers sometimes accept it anyway and report a reason such as mailing_list or trusted_forwarder. Lists may also rewrite the From address to avoid the failure. Forwarding problems are in Forwarded mail fails DMARC.
Where to see what happened
Aggregate reports show the disposition each receiver applied (none, quarantine, or reject) and any override reasons (A field-by-field walk-through of a DMARC aggregate report). They don't show inbox or spam placement. The standard report format has no placement data, and extensions that would disclose message placement (inbox or spam) are discouraged. And mail rejected early on SPF -all, before the From header is seen, never shows up.
A failing row with disposition=none at a reject domain isn't a bug. Look at the override reason.
If legitimate mail started failing after you published a policy, see Mail started failing after we published DMARC. Whether you're ready to tighten is in When you are ready for p=quarantine and When you are ready for p=reject.
Free DMARC account
Ready to move from p=none to enforcement?
Check that your legitimate senders are aligned before you tighten your policy, and get help from our team if something blocks the move.
- See which senders aren't aligned yet
- Check results per sender before each policy step
- Talk to our team when a sender won't align
FAQ
If I'm at quarantine, where does failing mail go?
It depends on the receiver: a spam or Junk folder, an admin quarantine, or the inbox with a warning.
Will the sender know if a message is rejected?
Usually, through a bounce from their own server. A receiver can also silently discard it.
Why did a failing message still arrive at reject?
The receiver applied its own policy, for example for a trusted forwarder. Check the override reason in your reports.