DMARC Policy: None vs Quarantine vs Reject Explained
A DMARC policy tells receiving servers what to do with mail that fails authentication. Here is how none, quarantine and reject differ, and a safe order to roll them out.

TL;DR
- A DMARC policy is the
p=tag in your DMARC record. It tells receivers what to do with mail that fails SPF and DKIM alignment. p=noneonly monitors.p=quarantineasks receivers to treat failing mail as suspicious.p=rejectasks them to refuse it.- Start at
none, read the reports, fix your senders, then tighten step by step. - Use
pctto apply a stricter policy to a share of mail while you gain confidence.
What is a DMARC policy?#
A DMARC policy is the instruction you publish for receiving mail servers. It sits in a DNS TXT record at _dmarc.yourdomain.com. According to dmarc.org, DMARC builds on SPF and DKIM. It checks whether the domain in the visible From address lines up with the domains that passed those checks. Your policy says what should happen when it does not.
Here is a minimal record:
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
The p= tag is the policy. The rua= tag is where aggregate reports go. If you have not set up authentication yet, start with our guide on how to set up SPF, DKIM and DMARC. To confirm a record is live, see how to check DMARC records.
The three DMARC policy values#
There are exactly three values. Each one asks for a different level of enforcement.
| Policy | What you ask receivers to do | Risk to real mail | Best used for |
|---|---|---|---|
p=none |
Take no action, just send reports | None | Discovery and testing |
p=quarantine |
Treat failing mail as suspicious, often the spam folder | Low to medium | Gradual enforcement |
p=reject |
Refuse failing mail at the SMTP stage | Higher if misconfigured | Full protection |
Receivers treat these as requests. The specification in RFC 7489 lets a receiver apply local judgment. In practice most large mailbox providers follow your policy.
p=none: monitor only#
p=none is the safe starting point. Nothing changes for your mail. You simply start receiving aggregate reports that show who sends as your domain and whether they pass.
Do not stay here forever. A none policy does not stop anyone from spoofing your domain. It only gives you data.
p=quarantine: treat failures as suspicious#
With p=quarantine, you ask receivers to place failing messages in spam or hold them for review. Real mail from a forgotten sender may land in spam, so move here only after the reports look clean.
p=reject: block failures#
p=reject is the strongest setting. Failing mail is refused and never reaches the inbox. It gives the best protection against spoofing and phishing in your name. It also punishes mistakes, so only use it once every legitimate sender is authenticated and aligned.
How to choose the right DMARC policy#
Pick based on how well you know your mail streams.
- You do not know all your senders yet. Use
p=none. - Reports show your main senders passing. Move to
p=quarantine. - Every legitimate source passes for several weeks. Move to
p=reject.
Most teams do not need to rush. A slow rollout costs you nothing, while a blocked invoice email costs a lot.
How to move from none to reject safely#
Follow this order.
- Publish SPF and DKIM first. DMARC needs at least one of them to pass and align.
- Add a
p=nonerecord withrua. Collect reports for a few weeks. - List every sender. Your CRM, billing tool, support desk, marketing platform and cold email tool all send as your domain. Fix each one so it signs with DKIM for your domain.
- Move to
p=quarantinewith a lowpct. Thepcttag applies the policy to a share of failing mail, for examplepct=10. Raise it as reports stay clean. - Go to
p=quarantine; pct=100, thenp=reject. Watch reports after each change.
If you run cold outreach, keep it on a separate sending domain so a mistake there cannot affect your main domain. Our guide to cold email infrastructure covers the setup.
Other DMARC tags worth knowing#
sp=sets a different policy for subdomains.adkim=andaspf=set alignment to relaxed (r) or strict (s).ruf=requests failure reports. Many receivers do not send them.rua=requests daily aggregate reports. Always set it.
Do Google and Yahoo require a DMARC policy?#
Yes, for bulk senders. Google's email sender guidelines say senders of large volumes must publish a DMARC record. A p=none policy meets the minimum. It does not give you protection, so plan to tighten it.
DMARC is one part of email deliverability. Authentication gets you through the door, but list quality decides whether your messages are welcome. Run your list through an email verifier before every campaign so bounces do not hurt your sender reputation.
Common DMARC policy mistakes#
- Jumping straight to
p=rejectwithout reading reports. - Forgetting a third-party sender such as a billing platform.
- Never moving past
p=none. - Publishing two DMARC records. Only one is allowed per domain.
- Leaving
ruaempty, so you never see what is failing.
FAQ#
What is the default DMARC policy?#
There is no default. The p= tag is required. If a receiver cannot read your record, it behaves as if you had no DMARC at all.
Is p=none enough?#
It satisfies basic bulk sender rules, but it does not stop spoofing. Treat it as a first step toward quarantine and reject.
Will p=reject break my email?#
Only if a legitimate sender fails authentication. Reading aggregate reports before you tighten the policy prevents that.
What does pct do in DMARC?#
It sets the percentage of failing mail the policy applies to. It lets you roll out quarantine or reject gradually.
How long should I stay on p=none?#
Long enough to see every sender in your reports. Many teams take a few weeks, but there is no fixed number.
Check your list before you send#
Authentication protects your domain. Clean data protects your reputation. Tomba's email verifier checks addresses before you send, so your DMARC-protected domain keeps a low bounce rate.
// start free
See who Tomba finds at any company
Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.
Free plan · No credit card required · GDPR & CCPA
// about the author