From p=none to p=reject without breaking your email

A staged rollout for DMARC enforcement: inventory your senders from the reports, fix alignment, ramp pct, protect subdomains, and keep a rollback plan.

Updated

Want to see where your domain stands before you start? Check your current policy

p=none gives you reports. p=reject gives you protection. The distance between the two is a short project whose only real risk is rejecting your own legitimate mail because a sender you forgot about never got aligned. This plan removes that risk by moving in steps that are each reversible within a DNS TTL.

Why not go straight to reject

Every system that sends mail with your domain in the From header must pass aligned SPF or DKIM: your mail provider, but also the CRM, the helpdesk, the newsletter platform, the invoicing tool, the HR software, the website contact form, the monitoring alerts and the multifunction printer in the corridor. Most organisations discover two or three forgotten senders in their first DMARC reports. At p=reject, each of them would silently stop reaching customers.

Phase 0: monitor (week 1 to 3)

Publish the record with a reporting address and change nothing else:

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com

Let two to three weeks of reports accumulate so that weekly and monthly senders (invoices, statements) show up. How to read a DMARC report explains the format.

Phase 1: inventory and fix (week 2 to 6)

Build one table from the reports and keep it updated:

Source (IP owner) Messages / week SPF aligned DKIM aligned Owner Action
Google Workspace 4,800 pass pass IT none
Marketing platform 1,200 fail fail (signs as vendor) Marketing enable custom DKIM domain, add SPF include
Helpdesk 350 pass fail Support enable DKIM in vendor settings
Unknown, 185.x.x.x 90 fail fail – spoofing, no action

For each legitimate source that fails:

  1. DKIM first. In the vendor’s settings, look for “domain authentication”, “custom DKIM” or “sending domain”. They give you one to three CNAME or TXT records. DKIM alignment survives forwarding, so it is the one to prioritise.
  2. SPF second. Add the vendor’s include only if the vendor uses your domain in the envelope sender (Return-Path). Many vendors use their own bounce domain, in which case SPF cannot align and adding the include is useless. Watch the lookup count with the SPF checker.
  3. Bulk senders on a subdomain. Point newsletters to news.yourdomain.com with its own SPF and DKIM. The main domain’s record stays short, and the subdomain can have its own DMARC policy.
  4. Devices and internal apps. Route printers and scripts through your provider’s authenticated SMTP relay instead of sending directly.

Re-check alignment after each fix with the DMARC checker and, for the real test, with the next day’s reports.

Phase 2: quarantine, gradually (week 4 to 8)

When every legitimate source has passed for two consecutive weeks, tighten the policy while limiting the blast radius with pct:

v=DMARC1; p=quarantine; pct=10; rua=mailto:dmarc-reports@yourdomain.com

pct=10 applies the policy to 10% of failing messages only. Keep each step for about a week and watch the disposition field in the reports: it now shows quarantine for the affected share. Raise it to 25, 50, then 100 (or remove the tag, which means 100). If a legitimate source starts showing quarantine, drop back to the previous value, fix the source, and resume.

Phase 3: reject (week 8 to 10)

Same ramp, final policy:

v=DMARC1; p=reject; pct=25; rua=mailto:dmarc-reports@yourdomain.com

then pct=100. Many teams skip the ramp at this stage because the quarantine phase already proved the inventory; keep it if your volume is high or your senders change often.

Phase 4: subdomains and housekeeping

Rollback plan

Because the policy lives in DNS, rollback is one edit: set p=none (or lower pct) and wait for the TTL to expire. Keep the TTL of the _dmarc record at 1 hour or less during the rollout, and raise it afterwards if you like.

Checklist before p=reject

Google and Yahoo have required DMARC from bulk senders since 2024, and Microsoft since 2025, so this rollout is now part of ordinary email hygiene rather than a security extra.

Check your work. Run the checker on your domain: it reads the live DNS records and tells you what is still missing.