Skip to content
DMARC Pulse

Learn

DMARC policy none quarantine reject: what each value does

DMARC policy none, quarantine or reject tells receivers how to treat failing mail. What each value does, quarantine vs reject, and how to raise it safely.

What it is

DMARC policy none, quarantine and reject are the three values of the p tag: none expresses no preference, quarantine calls failing mail suspicious, and reject calls it an invalid use of your domain. DMARC is a DNS record that tells receiving mail servers (receivers) how you want that mail treated. RFC 9989, the current standard, defines no other DMARC policy options for p.

Failing means neither SPF (the list of servers allowed to send for a domain) nor DKIM (a signature on the message) passed for a domain aligned with the From address. Your record states a preference, and RFC 9989 leaves the final handling to each receiver's local policy. Google and Microsoft document these outcomes. The Microsoft 365 column assumes its Honor DMARC record policy setting is on, which is the default.

Value Google's description Microsoft 365
p=none Deliver and log in a daily report No DMARC action; other filters still run
p=quarantine Spam folder Quarantine or Junk Email, as the admin sets it
p=reject Reject, usually with a bounce Reject, or quarantine if the admin picks it

DMARC none (p=none)

RFC 9989 says p=none must not change how receivers handle your mail, so forged mail gets no extra treatment because of your record. The value of this stage is the aggregate reports, XML summaries of who sends as your domain.

DMARC quarantine (p=quarantine)

Quarantine is the first level of enforcement. RFC 9989 says failing mail will not reach the inbox at receivers that honor it. Microsoft notes a receiver might instead deliver it to the inbox with a marker added to the Subject or body.

DMARC reject (p=reject)

A DMARC policy of reject says every failure clearly indicates invalid use of your domain. Receivers that honor it normally refuse the message during the SMTP session, the conversation between the two mail servers. RFC 9989 gives 550 5.7.1 Email rejected per DMARC policy for example.com as a sample reply. The wording varies by receiver, and 550 5.7.1 also covers other refusals, such as relaying denied. A receiver can also discard the message silently, so a missing bounce proves nothing.

Receivers still decide, and RFC 9989 tells them not to reject on that policy alone. It also admits that mail relayed by mailing lists with an unmodified From line is frequently rejected in practice.

DMARC quarantine vs reject

Google says recipients can review quarantined mail in the spam folder, and it warns that rejected mail is never delivered. RFC 9989 says domains whose users might post to mailing lists should not publish p=reject. Those that do should spend at least a month at none and as long at quarantine, then compare the results. Microsoft's rollout guide instead sets p=reject as the goal for all custom domains.

Example

This is the usual path for example.com, in one TXT record at _dmarc.example.com. Edit that record at each step, because RFC 9989 tells receivers to discard all DMARC records when several exist at the same name. For the first record, see how to set up DMARC.

  1. Monitor. Keep p=none until your reports show every service that sends as your domain. Google's rollout starts with one week. RFC 9989 warns it can take many months, depending on how often you send.

    TXT
    v=DMARC1; p=none; rua=mailto:dmarc@example.com
  2. Fix senders, then quarantine. RFC 9989 requires legitimate senders to be fixed first. Caution: any sender you missed, and forwarded mail without aligned DKIM, can now land in spam. Subdomains without their own DMARC record follow p unless you set sp, so check them in your reports too.

    TXT
    v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
  3. Reject once your reports stay clean. Caution: mail from any sender still failing can be refused. Your reports must already show DKIM passing aligned: RFC 9989 says domains at p=reject must not rely on SPF alone, because forwarded mail usually fails SPF.

    TXT
    v=DMARC1; p=reject; rua=mailto:dmarc@example.com

After each change, confirm the value with the DMARC checker. In your reports, disposition shows what the receiver did, and reason explains a difference from your policy.

Common mistakes

  • Publishing p=none without rua. Receivers must not send aggregate reports without that tag, so you get no data for moving up. See how the rua tag works.
  • Using pct to apply your policy gradually. This tag asked receivers to apply the policy to only a percentage of failing mail. RFC 9989 removed pct because values other than 0 and 100 were usually applied inaccurately. Google's and Microsoft's guides still show it.
  • Counting on t=y as a safety net. This test tag asks for one level below your p. Google's and Microsoft's pages do not mention it, and RFC 7489 told receivers to ignore unknown tags. A receiver that has not adopted RFC 9989 would apply your p in full.

Check it now

Look up and validate a DMARC record

Frequently asked questions

Does p=none protect my domain from spoofing?
Not by itself. RFC 9989 says a p=none policy must not change how receivers handle your mail, so a forged message gets no extra treatment because of your record. Other filters keep running. The value of p=none is the aggregate reports, and those arrive only if the record has a rua tag.
Should I use p=quarantine or p=reject?
Go to quarantine first, because that mail can still be reviewed. Move to reject when your reports show that every legitimate sender passes. RFC 9989 says domains whose users might post to mailing lists should not publish p=reject. Microsoft's rollout guide sets p=reject as the goal for all custom domains, so weigh how your domain is used. A domain that never sends mail can publish p=reject directly, as Microsoft advises for parked domains. Check first that nothing sends from it.
How long should I stay at p=none?
Stay until your reports cover all your mail streams and every legitimate sender passes. Google's rollout starts with one week. RFC 9989 says it may take many months, depending on how often you send. For domains whose users might post to mailing lists, it asks for at least a month at none and as long at quarantine before p=reject.
Does p=reject stop every forged email?
No. The receiver makes the final decision, and RFC 9989 lets it accept failing mail even at p=reject. DMARC also checks only the domain in the From address. Microsoft notes that a lookalike domain with its own valid records can pass SPF, DKIM and DMARC.

Sources consulted

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.