Topic · Authentication
DMARC p=quarantine policy
The DMARC p=quarantine policy requests suspicious treatment of messages that fail DMARC authentication.
How it works
Compliant receivers may direct failed mail to spam, junk or similar review handling; final disposition varies by provider.
What can go wrong
An overlooked legitimate mail stream may be diverted to spam, harming critical business communications.
What to check or do
Complete sender inventory and sample real mail flows before enforcement; review aggregate reports and inbox placement.
How to investigate DMARC p=quarantine policy
- Signal to investigate
- Legitimate customer mail begins landing in spam after quarantine is enabled.
- Evidence to collect
- Compare DMARC disposition and Authentication-Results for impacted streams with aggregate-report source breakdowns.
- Common wrong conclusion
- Quarantine is a receiver-requested disposition; it is not a guarantee of a particular spam-folder outcome.
How to interpret the evidence
Some receiving systems may apply local policy overrides. Identify whether a service lacks aligned DKIM, uses an unaligned bounce domain, or modifies signed content in transit.
What to change and how to verify it
Correct the sender configuration and test across representative receivers; consider temporary policy adjustments only with a documented risk decision.
Put this into practice
Run a focused check, then explore protection if your domain needs it.