Skip to content
  • There are no suggestions because the search field is empty.

When you are ready for p=reject

You're ready for p=reject on a domain when a period at quarantine shows every legitimate source passing with aligned DKIM, you've tested the mailing lists and forwarders you care about, and the domain's owners accept that receivers that honor DMARC may refuse what still fails. Make the call domain by domain. Reject is where we'd like sending domains to end up, but domains used for everyday staff email shouldn't go there, so it isn't the right end state for all of them.

How reject compares with quarantine as a policy is in our post on the difference between p=quarantine and p=reject. This article covers the readiness decision.

What a reject policy asks for

Reject means the domain owner considers all such failures to be a clear indication that the use of the domain name is not valid. Receivers that act on it usually refuse the message during the SMTP session, with a reply such as:

550 5.7.1 Email rejected per DMARC policy for example.com

It's still a request. Receivers must not reject incoming messages solely on the basis of a p=reject policy and, without other knowledge, must treat the failure as quarantine. In practice, though, mailing-list mail is frequently rejected due to a p=reject policy. Don't count on receiver leniency.

First: what kind of domain is it?

Domains where staff send everyday email

Domains used for general-purpose email should not deploy a DMARC policy of p=reject. The reason is mailing lists. A list that changes the subject line or adds a footer breaks DKIM, the forwarding breaks SPF, and the receiver rejects the post. Worse, list software can read those rejections as dead addresses and unsubscribe other members.

If you still want reject on such a domain, publish p=none for at least a month, then quarantine for an equally long period, compare the dispositions, and tell users that mailing-list participation may be hindered.

Dedicated sending subdomains

A subdomain used only by your transactional or marketing platform, say mail.example.com, has a known set of senders and no staff posting to lists. That makes it an easier case for reject. That's our inference, not a hard rule. Rolling out on low-volume subdomains first, and saving the parent domain for last, is a common approach.

Parked domains that never send

Microsoft recommends v=DMARC1; p=reject; for domains that "no one on the internet should expect to receive mail from." Pair it with v=spf1 -all (Common SPF mistakes). Confirm nothing sends first.

Microsoft 365's published goal is to get to a p=reject DMARC policy for all of your custom domains and subdomains. That's Microsoft's position for its platform. Weigh it against the caution for staff domains above.

The non-negotiable: aligned DKIM on every source

Domains at reject must not rely solely on SPF to secure a DMARC pass and must apply valid DKIM signatures. SPF fails as soon as mail is forwarded, because the forwarding server's IP isn't in your record. DKIM signatures will generally remain valid through plain relays.

So check every legitimate source for a DKIM signature aligned with your From domain. A vendor that passes only through SPF today is a vendor whose forwarded mail will be refused tomorrow. What breaks DKIM on lists is in DKIM and mailing lists or forwarders.

Readiness evidence

  1. A quarantine period with stable reports. Compare dispositions with the none period, source by source, not just the headline pass rate.
  2. Aligned DKIM on every legitimate source, checked in policy_evaluated (A field-by-field walk-through of a DMARC aggregate report).
  3. Unexplained failures are only unauthorized use. Every legitimate failing source is fixed or deliberately accepted.
  4. Indirect mail tested. The lists, forwarders, and alumni-style addresses your users and customers rely on (Forwarded mail fails DMARC).
  5. The business has signed off on the remaining risk, in writing if that's how your organization works.
  6. A rollback path. Keep the old record and know who can publish it.

If any of these is missing, stay at quarantine. It's already enforcement. More on the earlier gate in When you are ready for p=quarantine, and the full sequence in A safe rollout: p=none to quarantine to reject.

Pitfalls

  • Publishing reject on the main staff domain without a quarantine period.
  • Vendors that pass only via SPF.
  • Forgetting staff posts to industry mailing lists.
  • Moving many domains to reject at once after a security incident, without the evidence for each.
  • Assuming subdomains are handled. Set sp deliberately (Subdomain policy (sp)).
  • Using SPF -all on sending domains. Mail rejected early on SPF will never appear in aggregate DMARC reports, so you lose sight of it. Our house stance is ~all for sending domains.

After you switch

Keep rua and keep reading. Recipients' own settings shape what happens. In Microsoft 365, when Honor DMARC record policy is on, Microsoft's Set up DMARC summary is a rejection during SMTP, and the anti-phishing policy also lets the tenant quarantine that mail instead (What happens to failing mail under each policy). If legitimate mail starts bouncing, start at Mail started failing after we published DMARC.

Reject doesn't stop lookalike domains, display-name tricks, or compromised accounts, and passing DMARC doesn't mean the inbox.

Free DMARC account

Ready to move from p=none to enforcement?

Check that your legitimate senders are aligned before you tighten your policy, and get help from our team if something blocks the move.

  • See which senders aren't aligned yet
  • Check results per sender before each policy step
  • Talk to our team when a sender won't align

Create a free DMARC accountTalk to an expert

FAQ

Is reject better than quarantine?

It's a stronger request. For domains where staff send everyday mail, reject is usually the wrong end state. For BIMI, either quarantine or reject works.

Will reject break mailing lists?

It can, for your users' posts to lists that modify messages. Test the lists that matter first.

Is p=reject required for BIMI?

No. Quarantine meets the policy requirement, as long as subdomains are at enforcement too (BIMI requirements checklist).