Home · Troubleshoot · p=none

DMARC · p=none

DMARC Policy is set to p=none

22 October 2026

p=none tells receivers to monitor and report, not to quarantine or reject unauthenticated mail. Spoofed messages that fail SPF and DKIM alignment can still reach the inbox. The free audit flags this as DMARC_POLICY_NONE (medium)—informative, not a DNS error.

Why teams stay on none

• Unknown third-party senders still pass or fail in reports.
• SPF is over budget or DKIM selectors are missing.
• Subdomain policy (sp) is weaker than expected.

Smooth path to enforcement

Use the full playbook: From p=none to p=reject without dropping legitimate mail.

1. Publish rua (your mailbox or Hosted DMARC) and collect aggregate reports.
2. Name every passing source: SPF ip4/ip6 or a published DKIM selector.
3. Clear static blockers with the free audit (no +all, no lookup PermError, valid DMARC syntax).
4. Hosted DMARC stages (each requires a person to approve): monitor → quarantine 25% → quarantine 50% → p=reject.

BIMI note

BIMI needs organizational DMARC at quarantine or reject with pct=100. Staying on p=none means logos will not qualify.