A DMARC record tells receiving servers two things: what to do with mail that fails the check, and where to send reports about it. The "what to do" part is the p= tag, and it has three settings.
Where it lives
The standard says a domain owner's DMARC preferences are stored as DNS TXT records in subdomains named "_dmarc".1 So a receiver handling mail "From" example.com looks up _dmarc.example.com.
The standard's own example looks like this:1
v=DMARC1; p=none; rua=mailto:dmarc-feedback@example.com1
That reads as version one of DMARC, a policy of none, and a mailbox for summary reports.1
The three policies
| Setting | What the domain owner is asking for |
|---|---|
| p=none | No specific action about delivery. Reports can still arrive.1 |
| p=quarantine | Treat failing mail as suspicious, which can mean the spam folder, extra scrutiny or a flag.1 |
| p=reject | Reject failing mail, ideally during the SMTP conversation.1 |
These are requests. The standard words them as what the owner "wishes" or "requests", and what a receiver does depends on its own capabilities.1
What alignment means
Passing SPF or DKIM isn't enough by itself. DMARC also asks whether the domain that passed matches the domain in the From address that people see. That match is called alignment.1
Mail passes DMARC when at least one of the two checks passes and is aligned. For DKIM, the standard says a message counts as a pass if any signature is aligned and verifies.1
There are two modes, set with the adkim= and aspf= tags.2 In relaxed mode, the two domains need the same organisational domain, which is the one registered with a registrar. So a signature from example.com lines up with mail from a subdomain of it. In strict mode, only an exact match counts.1
This is why a service that sends "on your behalf" using its own domain can pass SPF yet still fail DMARC. The domain that passed isn't yours. It's also why the first thing to check, when mail fails, is which domain each result names.
Other tags you'll see
- rua is where summary reports go.
- ruf is for reports about individual failures.
- sp sets the policy for subdomains.
- pct is the percentage of mail the policy applies to, for a slower rollout.
The dmarc.org overview lists these with examples, and says its examples are illustrative and shouldn't replace the specification.2 The default for pct is 100, according to the standard.1
Moving between policies
The dmarc.org overview lists an order for deploying DMARC. Get DKIM and SPF working first. Check that your mailers align. Publish a record that asks for reports, then read the data. Tighten the policy as you gain experience.2
Sort out your SPF record and DKIM signing first. Then look up what's published to confirm it.2