DMARC quarantine vs reject

Quick fix

Publish p=none with a rua address and read the aggregate reports for a few weeks. Change to p=quarantine, then to p=reject when the reports show only forged mail failing.

v=DMARC1; p=none; rua=mailto:[email protected]

How to fix it

  1. Publish p=none with a rua address, for example v=DMARC1; p=none; rua=mailto:[email protected], and read the aggregate reports for a few weeks.
  2. Make every legitimate sender pass SPF or DKIM aligned with the From domain: your mailbox provider, newsletter tool, CRM, billing and support systems.
  3. Change to p=quarantine and keep reading the reports. A sender that still fails now lands in spam instead of the inbox.
  4. Change to p=reject when the reports show only forged mail failing. Add sp=reject if your subdomains do not send mail of their own.

Learn more: DMARC explained: policy, alignment and reports

How to check

The DMARC check shows the policy receivers apply to your domain: p, sp and np, the report addresses, and whether the record is inherited from a parent domain.

The DMARC check opens with your domain filled in; it runs when you press Check.

Tools to check it

What the error means

p=quarantine asks receivers to treat mail that fails DMARC as suspicious, which in practice means the spam or junk folder. p=reject asks them to refuse it during the SMTP transaction, so it is never delivered and the sending server gets a bounce. Both are enforcement policies. Reject is the stronger one and the goal for most domains, once every legitimate sender passes DMARC.

The p tag of the DMARC record at _dmarc.example.com has three values (RFC 9989, section 4.7): none (monitoring only), quarantine (the domain owner considers failing mail suspicious) and reject (failing mail is a clear sign that the use of the domain is not valid). The policy is a request: each receiver decides how to apply it.

p=quarantinep=reject
Forged mailUsually delivered to spamRefused, never delivered
Legitimate mail that failsLands in spam, the recipient can still find itBounces back to the sender

Gmail, for example, bounces mail it refuses under a DMARC policy with 550 5.7.26 "Unauthenticated email from domain-name is not accepted due to domain's DMARC policy". Microsoft 365 bounces it with 550 5.7.509. Quarantine is the safer step while you still find senders you did not know about: a mistake costs a spam folder, not a lost message. The policy for subdomains is sp, and for subdomains that do not exist np. A record with p=reject and sp=none still leaves every subdomain open to spoofing. The pct tag that let you apply a policy to part of the mail was removed in RFC 9989; see DMARC_PARTIAL_PCT.

Sources

All findings