A safe rollout: p=none to quarantine to reject
Start at p=none with aggregate reports, find and fix every legitimate sending source, then move to p=quarantine and compare what the reports show. Only after that, decide domain by domain whether p=reject fits. Reject is where we'd like most sending domains to end up, but the current DMARC standard advises against it for domains used for everyday staff email, so it's a decision, not an automatic last step.
The rollout steps themselves are in our guide to moving from DMARC monitoring to enforcement. This article covers the evidence you want at each gate before you change anything.
Gate 1: Are reports actually arriving?
Monitoring only works if you've asked for reports. A typical starting record:
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"
Without rua, receivers don't send aggregate reports, and p=none gives you nothing to work from. p=none with reports is monitoring mode: use the reports to make any needed adjustments to how your mail is authenticated.
Set up SPF and DKIM at least 48 hours before you publish DMARC. Each message needs at least one aligned identifier, and preferably two.
Gate 2: Do you know every legitimate sender?
The reason to start at none is that a domain owner can overlook a server here or be unaware of a third-party sending agreement there. Build a list of every system that sends as your domain, with an owner for each: staff mail, billing, support desk, marketing platform, HR system. How to do that from reports is in How to inventory sending sources.
Then sort the failures. Some are spoofing. Some are your own vendors without alignment. Some are forwarders and mailing lists, which fail for reasons that have nothing to do with forgery. Telling them apart is in Legitimate mail vs spoofing in reports.
Gate 3: Does each legitimate source pass with alignment?
Check the aligned result, not the raw one. A vendor can pass DKIM for its own domain and still fail DMARC for yours. In an aggregate report that's the difference between auth_results and policy_evaluated (A field-by-field walk-through of a DMARC aggregate report).
For legitimate streams that fail, those shortcomings must be addressed before any attempt to publish an enforcement policy. A small failing stream still counts. It might be the invoice run.
Gate 4: Have reports covered a full sending cycle?
There's no single right number, and the sources disagree:
- One week at none is usually enough time for reports to show all your mail streams, though not always.
- Depending on how often you send, it may take many months before you're sure.
- For domains whose users post to mailing lists and still want reject, spend at least a month at none, then an equally long period at quarantine, comparing dispositions.
- Microsoft 365's guidance is to move on after enough time monitoring, without a fixed number of days.
Our view: wait until reports have covered every mail stream you know about, including the monthly and quarterly ones. A week that misses your quarterly statement run isn't enough.
Gate 5: Move to quarantine, one domain at a time
Microsoft suggests starting with a low-volume domain or subdomain with few senders and "saving the parent domain for last." That's sensible ordering. Subdomains inherit p unless sp, np, or their own record says otherwise, so changing the parent can change them too (Subdomain policy (sp)).
The readiness checklist is in When you are ready for p=quarantine. Change p=none to p=quarantine, keep rua, and watch the next reports. Don't use pct to stage the change. It's historic; what to use instead is in pct is historic: how to phase in DMARC enforcement now.
Quarantine is already enforcement. Enforcement means any policy other than none on the organizational domain and all its subdomains.
Gate 6: Decide on reject, per domain
Before reject, two things in particular:
- Every legitimate source needs aligned DKIM. At reject, you must not rely solely on SPF for a DMARC pass.
- For domains where staff send everyday email, they should not deploy a DMARC policy of
p=reject, mainly because of mailing lists.
Dedicated sending subdomains and parked domains are often easier cases. The full decision is in When you are ready for p=reject.
After each step
Keep reading reports. New senders turn up, and receivers report when they override your policy. If legitimate mail starts failing after a change, go to Mail started failing after we published DMARC before tightening anything else.
Two cautions that catch people out:
sp=nonewithp=quarantineleaves subdomains outside enforcement. That also rules out BIMI.- SPF
-allcan get mail rejected before DMARC runs, and those messages will never appear in aggregate DMARC reports. Our house stance is~allon sending domains.
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
Do we have to end at p=reject?
No. Quarantine counts as enforcement, and it meets the DMARC policy requirement for BIMI. Reject has extra cautions, especially for staff mail domains.
Should we pause campaigns while we change the policy?
Not if the platform already passes with alignment in recent reports. If it doesn't, fix it before you change the policy.
When can we start on BIMI?
Once the organizational domain and its subdomains are at quarantine or reject. Next steps are in How to move from DMARC enforcement to BIMI.