DMARC Quarantine vs Reject: Which Policy Should You Use?
The short answer (what's causing it)
p=quarantine asks receivers to treat failing mail as suspicious (usually spam folder); p=reject asks them to refuse it at SMTP. Both only apply to mail that fails aligned SPF and DKIM.
Step-by-step fix
- Check your current policy with the free scan.
- Use quarantine as the staging step while confirming no legitimate source fails.
- Switch to reject once reports are clean.
- Set
sp=if subdomains need a different policy.
Record examples (replace example.co.uk with your domain)
_dmarc.example.co.uk. TXT "v=DMARC1; p=reject; sp=reject; rua=mailto:[email protected]"
Examples are illustrative templates, not values for your domain. Test changes at
p=none/ staging first.
Check yours free in seconds
Run the free 20-check SuperTool on your domain: no signup, no install, public DNS only. Relevant checks: DMARC.
Scan my domain free (20-check SuperTool) → £24 Sovereign DMARC (T0 RUA), SPF, MTA-STS & PHP2Shell Remediation Pack → £5 Website Launch Special Quick-Fix Pack →One-off download via PayPal guest checkout, no subscription. Packs contain DNS/config templates and scripts you run yourself.
Frequently Asked Questions
Is reject riskier?
Only for mis-configured legitimate senders; that's why you stage it.
Does pct work with reject?
Yes, pct applies a partial rollout; failing mail outside pct falls back to the next-weaker policy.
Related FaultyPacket guides & tools
- Free 20-check SuperTool
- Zero-downtime DMARC p=reject, SPF & MTA-STS rollout
- DMARC RUA first-party reporting vs external SaaS
Authorised use: only scan domains you own or are authorised to inspect. Results are point-in-time public DNS observations.