Topic · Authentication

DMARC p=reject policy

A DMARC p=reject policy requests receivers to reject mail that fails aligned SPF or DKIM checks for the protected From domain.

Email Security Glossary·Practical guidance
Share this definition LinkedIn X WhatsApp Email
01 / How it works

How it works

Receivers apply their own policy and trust evaluations, but reject is the strongest published DMARC disposition request.

02 / What can go wrong

What can go wrong

Misaligned production senders may experience hard delivery failures when the receiving system enforces the policy.

03 / What to check or do

What to check or do

Verify known senders, preserve report monitoring and test vendors and forwarders before moving to reject.

Practical diagnosis

How to investigate DMARC p=reject policy

Signal to investigate
SMTP rejects affect a legitimate application after p=reject deployment.
Evidence to collect
Capture the SMTP rejection, aligned identifiers on rejected messages if available, and aggregate reporting for the affected source.
Common wrong conclusion
A syntactically valid reject policy does not establish that every legitimate mail flow is correctly authenticated.

How to interpret the evidence

Receivers make local handling decisions, and messages from forwarding systems may fail SPF while preserving DKIM. Treat enforcement failures as an inventory or alignment investigation, not a reason to disable all authentication.

What to change and how to verify it

Fix aligned DKIM or branded return-path for the affected stream; retest actual messages before re-enabling or escalating enforcement.

NEXT STEP

Put this into practice

Run a focused check, then explore protection if your domain needs it.

Authoritative reference ↗