The p tag is the heart of a DMARC record: it tells receivers what you want done with mail that uses your domain in From but fails DMARC. none asks for nothing but reports, quarantine asks for the spam folder, reject asks for it to be refused.
| Syntax | p=none | p=quarantine | p=reject |
| Values | none, quarantine, reject |
| Subdomains | Follow p unless sp= or np= say otherwise |
| Defined in | RFC 9989 |
What it does
none: deliver as usual, but send me reports — the monitoring stage, and enough to meet Gmail’s, Yahoo’s and Microsoft’s requirement to have a DMARC record. quarantine: treat failing mail as suspicious, usually the spam folder. reject: refuse it during delivery, so it never arrives.
A policy is a request. Receivers apply their own judgement on top — they may quarantine when you asked for reject, for example for mailing lists.
Examples
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Monitor: nothing is blocked, reports arrive daily.
v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
Failing mail goes to spam.
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Failing mail is refused — full protection against people sending as you.
See what your own DMARC record says
Every term of your published record, read and explained — including this one.
Common mistakes
- Jumping straight to reject before every service sending as the domain passes.
- Staying at none for years: it protects nothing.
- A policy with no rua=, so you never learn what is failing.
What we recommend
Start at p=none with a report address. When the reports show every legitimate sender passing, move to quarantine — with t=y first if you want a trial — then to reject.
Read your DMARC reports free →
Questions
Is p=none enough for Gmail and Yahoo?
For their bulk-sender requirements, yes: they ask for a DMARC record, and p=none is a valid policy. It does nothing to stop forgery, so treat it as the first step.
Sources
Checked on 25 September 2026 against these official sources: