Topic · Investigation
DMARC policy override
A DMARC policy override is a receiver decision to handle a message differently from the domain's requested disposition.
How it works
Aggregate reports can include explanations such as forwarding or local policy for the deviation.
What can go wrong
Assuming every p=reject failure was rejected will exaggerate protection and confuse metrics.
What to check or do
Review override-reason fields and compare reported policy with actual recipient outcomes where observable.
Practical scenario
An aggregate report lists failures against a domain publishing p=reject, yet some receivers show disposition none because local policy or trusted-forwarder handling overrode the requested assessment. The reported rejected count is therefore lower than the raw failure count.
Verification checklist
- Group records by policy domain and reporting organization.
- Compare authentication results, disposition and override reason values.
- Identify trusted forwarding paths before treating them as abusive.
- Avoid claiming that every DMARC failure was blocked or that pass guarantees inbox placement.
Put this into practice
Run a focused check, then explore protection if your domain needs it.