A practical plan to move DMARC from p=none to p=quarantine and p=reject: collect rua reports, fix unaligned senders, use pct and t=y, set subdomain policy, and go to enforcement without blocking legitimate mail.
Home › Guides › DMARC p=none to p=reject rollout
Last updated 17 November 2026
Roll DMARC out in this order, and do not skip the monitoring step:
p=none with an aggregate report address (rua) after SPF and DKIM are in place for every service that sends as the domain.p=quarantine (optionally with pct or RFC 9989 t=y while you watch). Then publish p=quarantine at 100% without t=y.p=reject. Stay there. Microsoft's stated goal for custom domains is p=reject; Gmail, Yahoo and Outlook.com bulk-sender rules accept p=none as a minimum, but enforcement is what stops spoofed From addresses.Build each record with the DMARC Record Generator and confirm it with the DMARC Record Checker. If a lot of your mail is forwarded or passes through mailing lists, read DMARC fail after forwarding or on mailing lists before you jump to reject.
d= domain aligns with From) on every sending service, including Microsoft 365, Google Workspace and third-party tools. Check keys with the DKIM Checker.rua address. If that address is on a different domain, the destination domain must publish a confirmation record as described in the DMARC RFCs; the DMARC Record Checker flags a missing one.DMARC passes when aligned SPF or aligned DKIM passes. Third-party senders that use their own bounce domain and their own DKIM d= will fail DMARC until they sign with your domain or use a custom return-path. That problem is explained in DMARC fail with SPF pass.
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
Receivers do not quarantine or reject unauthenticated mail because of this policy. They should still send aggregate reports. Keep p=none until the reports, not a single test message, show that every legitimate source passes.
sp out at first so subdomains inherit p=none, or set sp=none explicitly if you already know a subdomain is not ready.adkim=r, aspf=r). Do not switch to strict until monitoring is clean..xml.gz files in the DMARC Report Analyzer. Treat policy_evaluated (aligned) results as the ones that matter; raw SPF or DKIM pass in auth_results can still be unaligned.When the only failing sources are ones you do not recognise, or ones you have decided are spoofed, publish quarantine. Receivers that honour the policy will treat failing mail as suspicious (often Junk Email or quarantine), not as a hard bounce.
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com
Optional controls while you watch:
pct. RFC 7489 applies the stated policy to this percentage of the messages that would be subject to it (default 100). You can start with pct=10 or pct=25 and raise it. BIMI will not work until quarantine or reject is at 100% (or pct is omitted, which defaults to 100).t=y. Test mode tells receivers to apply one policy level below what you published: p=reject is treated as quarantine, p=quarantine as none, and p=none is unchanged. Reports still go out. Use it as a dress rehearsal, then remove t=y. It is not a substitute for reading reports at p=none.After you publish, watch reports and user complaints for one to two weeks. If a forgotten marketing platform or scanner appears as a failing source, fix its DKIM or SPF and only then continue.
v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.com
Receivers that honour reject will refuse unauthenticated mail that claims your From domain. That is the point of DMARC. It also means:
sp= only as a temporary exception, and give those subdomains their own _dmarc records when you can. A lasting sp=none also blocks BIMI on the organizational domain.You can use pct or t=y for a short reject rehearsal, then publish a plain p=reject record. Generate it with the DMARC Record Generator, check it with the DMARC Record Checker, and confirm resolvers see the new TXT with the DNS Propagation Checker or DNS Lookup.
_dmarc record uses sp= from the organizational domain, or p= if sp is absent. Audit www, mail, marketing and unused names before reject.pct=100 (or omitted), and no sp=none. See BIMI setup.p=none meets the minimum. Enforcement is still the right end state. See the bulk sender requirements checklist.dmarc= in the Email Header Analyzer.Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).
Build and check the record with the DMARC Record Generator and DMARC Record Checker, read reports in the DMARC Report Analyzer, and confirm the domain with the Email Deliverability Checker, SPF Record Checker, DKIM Checker, Email Header Analyzer and DNS Propagation Checker. Related guides: DMARC for Microsoft 365, SPF, DKIM and DMARC for Google Workspace, DMARC fail with SPF pass, DMARC fail after forwarding, BIMI setup and bulk sender requirements.
Until aggregate reports over at least two to four weeks, including a month-end cycle, show that every legitimate sending service passes aligned SPF or DKIM. A few test messages are not enough, because some vendors send only on billing day or at the end of the month.
RFC 7489 applies your published policy to that percentage of the messages that would be subject to it. The default is 100. You can raise pct gradually at quarantine or reject. Do not leave pct below 100 if you want BIMI, and do not use pct as a way to avoid fixing a failing sender.
It tells receivers to apply one policy level below the one you published: reject is treated as quarantine, quarantine as none, and none is unchanged. Aggregate reports are still sent. Remove t=y when you are ready for the published policy to be honoured.
It can. Forwarding usually breaks SPF alignment, and mailing lists often break DKIM, so a forwarded copy may fail DMARC and bounce once the policy is reject. Fix forwarding with aligned DKIM, SRS, From rewriting or ARC before or during the move, as described in the forwarding and mailing lists guide.
Yes, those rules ask for a valid DMARC policy of p=none or stronger and a passing aligned SPF or DKIM check. p=none does not stop spoofed mail that claims your domain. Quarantine and then reject are the steps that provide that protection.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.