DMARC p=none to p=reject Rollout Plan

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

Quick answer

Roll DMARC out in this order, and do not skip the monitoring step:

  1. Publish p=none with an aggregate report address (rua) after SPF and DKIM are in place for every service that sends as the domain.
  2. Read several weeks of reports, including a month-end cycle, in the DMARC Report Analyzer. Fix every legitimate source that fails aligned SPF and DKIM.
  3. Move to p=quarantine (optionally with pct or RFC 9989 t=y while you watch). Then publish p=quarantine at 100% without t=y.
  4. Repeat the report check, then publish 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.

Prerequisites

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.

Stage 1: p=none (monitor only)

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.

Stage 2: p=quarantine

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:

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.

Stage 3: p=reject

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:

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.

Subdomains, BIMI and bulk-sender rules

Verify each stage

  1. Check the live record with the DMARC Record Checker and the Email Deliverability Checker.
  2. Send a test message and read dmarc= in the Email Header Analyzer.
  3. After each policy change, wait for the next rua cycle and open the reports in the DMARC Report Analyzer. The policy in the report should match what you published, and legitimate sources should still pass.

Audit hundreds of domains at once

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).

Related tools and guides

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.

FAQ

How long should I stay at p=none?

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.

What does the DMARC pct tag do?

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.

What does RFC 9989 t=y test mode do?

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.

Will p=reject break forwarded mail?

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.

Is p=none enough for Gmail, Yahoo and Outlook.com bulk sender rules?

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.

Want the full kit?

Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.