Move DMARC from p=none to p=reject safely
Quick summary: Publish a DMARC record at p=none with reporting turned on. Use the reports to list every system that sends as your domain, fix each legitimate sender so SPF or DKIM aligns with your From domain, then raise the policy to quarantine in steps and finally to reject. Most rollouts take 4 to 12 weeks depending on how many senders you have.
What DMARC actually checks
DMARC passes when a message passes SPF or DKIM and the domain that passed matches the domain in the visible From address. That match is called alignment. A message can pass SPF and DKIM for your email provider’s domain and still fail DMARC, because neither domain is yours.
Step 1: publish p=none with reporting
Add a TXT record at _dmarc.yourdomain.com:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
p=none asks receivers to take no action on failures, so nothing is blocked. The rua address receives daily aggregate reports as XML files. If the address is on a different domain, that domain must publish a TXT record at yourdomain.com._report._dmarc.reportdomain.com containing v=DMARC1, or most receivers will not send reports. A report-processing service or tool makes the XML readable.
Step 2: find every sender
Collect reports for at least two to four weeks, long enough to catch monthly and quarterly sends. For each source IP, identify the system: your email platform, a CRM, a helpdesk, a billing tool, a website form, a forgotten server. Sort them into legitimate senders and unknown ones. Unknown sources that fail authentication are the traffic DMARC enforcement will block.
Step 3: fix each legitimate sender
- Sign with your own domain (DKIM). Most platforms let you publish a DKIM key so the signature uses
d=yourdomain.com. This is the most reliable route to alignment. - Use a custom return-path (SPF). Many platforms let you point a subdomain at them so the envelope sender is on your domain, which allows SPF to align.
- Keep SPF within 10 DNS lookups. Every
includecounts. Remove senders you no longer use.
Check results with the SPF, DKIM and DMARC lookup, and confirm on real messages with the email header parser.
Step 4: move to quarantine gradually
When reports show legitimate mail passing, change the policy to p=quarantine with a percentage so only part of failing mail is affected:
v=DMARC1; p=quarantine; pct=10; rua=mailto:dmarc-reports@yourdomain.com
Watch reports and complaints for a week or two, then raise pct to 25, 50 and 100. If a legitimate sender starts failing, lower the percentage while you fix it. Support for pct varies between receivers, so treat it as a ramp, not a guarantee.
Step 5: move to reject
v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com
Failing messages are now refused. Keep reporting on and review it regularly, because new tools and new teams add senders over time. Use sp= if subdomains need a different policy from the main domain.
Cases that cause trouble
- Forwarding and mailing lists. Forwarding usually breaks SPF, and lists that change the subject or body can break DKIM. DKIM-signed mail survives plain forwarding, which is another reason to align DKIM for every sender.
- Domains that never send. Publish
v=spf1 -allandp=rejecton parked and unused domains to stop spoofing. - Third parties you forgot. Invoicing, surveys and support tools often send as your domain. Reports reveal them.
Why it matters beyond spoofing
Since February 2024, Gmail and Yahoo have required bulk senders to authenticate mail and publish at least a DMARC record. Check their current sender guidelines for exact thresholds, since the rules are updated.
Need hands-on help with this? I freelance on email platforms, automation logic and migrations.
Start a project