Skip to content

DMARC policy

A DMARC policy describes the requested handling of failed domain checks. It repairs neither sending sources nor their alignment.

Also known asDMARC handling policy
Cloud & Operations

A DMARC policy describes the handling a domain requests for messages that fail DMARC checks. The policy record provides values including p=none, p=quarantine or p=reject. This concerns use of the sender domain, not a person signing in.

Check effects and configuration separately

With none, the domain expresses no special handling preference for such failures. This does not turn off the receiver’s other checks. The other values indicate the stricter handling requested; the receiving system makes the actual decision.

In the fictional design, a portal creates notification P-659. A newly connected service is not yet appropriately authenticated. A stricter policy does not fix that service’s configuration. The team must check the sending source and domain alignment before assessing a change’s effects.

Set up reporting deliberately

Reporting destinations are specified separately; the policy value alone does not organise analysis. For a planned transition, record known sending sources, test cases, responsibility and observation. A successful DMARC result still does not become a guarantee of inbox placement or harmless content.

Sources

Articles on this topic

Cloud & Operations with ASES

Hosting, deployment, maintenance and support