When you are ready for p=quarantine
You're ready for p=quarantine when reports covering your whole sending cycle show every legitimate source passing DMARC with an aligned identifier, the remaining failures are explained, and you know which subdomains will inherit the change. There's no standard pass-rate number that settles it. The evidence is source by source.
What quarantine and reject mean as policies is covered in our post on the difference between p=quarantine and p=reject. This article is about the first gate: leaving p=none.
DMARC none vs quarantine: what changes
At p=none you ask receivers for no change in handling. At p=quarantine, you consider failing mail to be suspicious: it is possible the mail is valid, although the failure creates a significant concern.
That's the first point where a receiver that honors your policy may treat your own unaligned mail differently. What that looks like varies. Google describes the spam folder. When Honor DMARC record policy is on (Microsoft's recommended setting), Microsoft documents the Junk Email folder, configurable to an admin quarantine. Details are in What happens to failing mail under each policy. For readiness, assume a failing message may not be seen normally.
The readiness checklist
1. Reports cover your full sending cycle
Monthly invoices, a quarterly newsletter, an annual renewal notice. If a sender hasn't sent yet, your reports can't show it. One week is usually enough for high-volume streams; depending on how often you send, it may take many months. Go by your own calendar, not either number.
2. Every legitimate source is identified and owned
Each system that sends as your domain should be on a list with someone responsible for it (How to inventory sending sources). The reason for starting at none is exactly this: it's easy to overlook a server here or be unaware of a third-party sending agreement there.
3. Each source passes with an aligned identifier
Look at policy_evaluated, not just auth_results. A raw DKIM pass can belong to the vendor's domain (A field-by-field walk-through of a DMARC aggregate report).
For example, a platform sending From: billing@example.com with a DKIM signature d=mailvendor.example.net passes DKIM but doesn't align with example.com. Unless SPF aligns, that mail fails DMARC.
Aligned DKIM is the one to aim for on every source. It usually survives plain forwarding, and SPF doesn't. You'll need it anyway if you later consider reject.
4. Remaining failures are explained
Sort them into spoofing and legitimate mail that isn't set up yet (Legitimate mail vs spoofing in reports). For the legitimate ones, the shortcomings must be addressed before enforcement.
Forwarded and mailing-list mail is its own category. It can fail even when it's genuine, and you can't always fix it at the source. Decide how much of it you care about (Forwarded mail fails DMARC).
5. Subdomains are accounted for
Without sp, subdomains inherit p=quarantine. A subdomain with its own DMARC record follows that record instead. List which subdomains send mail and confirm each is ready, or give it its own record for now (Subdomain policy (sp)).
Note the other direction too: p=quarantine; sp=none leaves subdomains outside enforcement, and BIMI won't accept it (BIMI requirements checklist).
6. People know, and you can roll back
Tell the owners of marketing, billing, and support tools when the change goes in. Keep the old record. If something legitimate breaks, republishing p=none is the rollback. Allow for the record's DNS TTL before the change, or the rollback, is seen everywhere.
Publishing the change
Change only p, and keep rua:
_dmarc.example.com. TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com"
Don't add pct to soften it. The tag is historic (pct is historic: how to phase in DMARC enforcement now). The new test flag t=y asks receivers to apply none instead of quarantine, but how widely receivers support it isn't documented.
What to watch afterwards
- Your known sources should keep showing aligned passes.
- Watch quarantine dispositions, and the override reasons receivers report, such as
mailing_listortrusted_forwarder. - Compare the quarantine period with the none period. Do the same comparison before reject.
- Reports show what receivers did under DMARC, not inbox placement. Take user complaints seriously too.
If legitimate mail starts failing, see Mail started failing after we published DMARC. The overall sequence is in A safe rollout: p=none to quarantine to reject, and the next gate is 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
Can I go straight from none to reject?
You can, but a quarantine period first is recommended for domains whose users post to mailing lists, and both Gmail and Microsoft 365 stage through quarantine.
What if something breaks?
Republish p=none, find the source in your reports, fix its alignment, and try again.
Does quarantine count for BIMI?
Yes, as long as subdomains are also at quarantine or reject and the record has no pct below 100.