Configuration9 min read · Updated Jun 2026

From p=none to p=reject: the safe enforcement playbook

Enforcement is where DMARC actually stops spoofing, but rushing it can block real mail. This staged playbook gets you to p=reject with the least risk to your legitimate mail.

Stage 1: Monitoring at p=none

Stay here until the dashboard accounts for 100% of your legitimate volume. You are looking for a stable picture where every real sender passes aligned SPF or DKIM. Most teams spend one to two weeks here.

Stage 2: Quarantine, test mode first

Move to p=quarantine with test mode on (t=y). Receivers apply the next-lower policy, so mail is delivered as it was at p=none, while the reports show what quarantine would catch. Test mode replaces the old pct tag, which DMARCbis retires.

Test mode first, then the real policy
v=DMARC1; p=quarantine; t=y; rua=mailto:<your report address>
v=DMARC1; p=quarantine; rua=mailto:<your report address>

After a week or two with nothing legitimate failing, turn test mode off. Failing mail now lands in spam rather than the inbox. Keep watching the reports. If a legitimate source appears, fix its alignment before going further.

Stage 3: Reject

Once quarantine runs clean, switch to p=reject. Spoofed mail is now refused outright at the receiving server. You own your domain.

ClearDMARC does this for you

The console shows a readiness score and a checklist before each policy change, and updates the managed record when you advance, so you never hand-edit DNS mid-rollout.

Do not forget subdomains

Set sp= to control subdomain policy, and publish records on active subdomains too. Attackers love an unprotected mail.yourdomain.

Was this guide helpful?