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

Why staying at p=none is a problem

p=none is the right place to start DMARC and the wrong place to stay. It asks receivers to change nothing about mail that fails DMARC, so a forgery using your exact domain is left to their other filters. With rua set it gets you reports, which only help if someone uses them to fix your senders and move on. And it rules out BIMI.

The business case for moving on is in our post on the real cost of skipping DMARC enforcement. This article sticks to what p=none does and doesn't do.

What DMARC p=none actually does

With p=none the domain owner offers no expression of preference, and a receiver that finds it must not modify existing mail handling processes.

That doesn't mean all spoofed mail gets through. Receivers' other filters still act. Microsoft's anti-phishing documentation says that at p=none, "other protection features in the filtering stack are still able to act on the message." What p=none means is that you haven't asked for anything.

With a report address, this is monitoring mode:

_dmarc.example.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"

Without rua, you get no aggregate reports, so you aren't even monitoring. Report addresses on another domain need authorization (rua, ruf, and report authorization).

Why staying there is the problem

You never ask for protection. Enforcement means a policy other than none on your organizational domain and all its subdomains. Only then will failing mail not reach the inbox at receivers that participate in DMARC and honor your preference.

Monitoring was meant to lead somewhere. Use the reports to make any needed adjustments, and end with a decision about enforcement. Reports that pile up unread don't fix the vendor that's still unaligned.

BIMI is off the table. BIMI requires p and sp at quarantine or reject. Policies of none are not accepted. A VMC or CMC can't help a domain at none (BIMI requirements checklist).

Security reviews flag it. Security scanners and audits can report a missing quarantine or reject policy as a finding. Fixing the finding by jumping straight to reject causes more trouble than it solves.

What p=none does satisfy

It's why many domains stop here. The DMARC part of the big providers' sender rules accepts none:

  • Gmail bulk senders: "Your DMARC enforcement policy can be set to none".
  • Yahoo: "Publish a valid DMARC policy with at least p=none," and DMARC must pass.
  • Outlook.com requires high-volume senders to pass SPF and DKIM and to pass DMARC, with a policy of "at least p=none". Microsoft 365 business mailboxes apply their own anti-spoofing checks and settings.

Meeting those rules is about getting your mail delivered to those providers, with aligned passing mail. It isn't spoofing protection. The full requirements are in Google, Yahoo, and Microsoft sender requirements.

Why domains stall, and how to move

The usual reason is fear of blocking your own mail, which is reasonable. The answer is evidence, not a leap:

  1. Make sure rua is set and reports arrive.
  2. List every legitimate sender with an owner (How to inventory sending sources), and sort failures into spoofing and setup gaps (Legitimate mail vs spoofing in reports).
  3. Fix alignment for every legitimate source.
  4. When reports covering a full sending cycle look clean, move to p=quarantine (When you are ready for p=quarantine). Quarantine already counts as enforcement.
  5. Then decide, domain by domain, whether reject fits (When you are ready for p=reject). That's where we'd like most sending domains to end up, but reject is usually the wrong end state for domains where staff send everyday mail.

The full sequence is in A safe rollout: p=none to quarantine to reject. What receivers do at each policy is in What happens to failing mail under each policy.

Mistakes worth avoiding

  • Treating DMARC as done once p=none is published.
  • Publishing p=none without rua.
  • Jumping from none to reject to clear a scanner finding.
  • Moving p to quarantine but leaving sp=none. Subdomains stay unprotected, and BIMI won't accept it (Subdomain policy (sp)).
  • Blaming p=none for spam-folder placement. It doesn't change handling, so the cause is elsewhere (why legitimate email goes to spam).

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

What does DMARC p=none mean?

You publish DMARC and ask for reports, but you express no preference for how receivers handle failing mail.

Is p=none bad?

No. It's the right first step. Staying there indefinitely is the problem.

Does p=none meet Gmail, Yahoo, and Outlook.com rules?

Yes, for the DMARC policy part, provided your mail passes DMARC with alignment.

Can I get BIMI at p=none?

No. You need quarantine or reject on the domain and its subdomains. The path from enforcement to BIMI is in How to move from DMARC enforcement to BIMI.