Skip to main content

Guide

DMARC from p=none to p=reject without breaking your email

A step-by-step path from DMARC monitoring to enforcement: find every sender, align SPF and DKIM, read reports, then move to quarantine and reject safely.

Author
Akash Sengar
Published
5 October 2026
Reading time
2 min

By Akash Sengar · · 2 min read

Why it matters

Without enforcement, anyone can send email that claims to come from your domain. That enables phishing and business email compromise against your customers and staff. Gmail and Yahoo (since February 2024) and Microsoft Outlook.com (since May 2025) require DMARC from bulk senders, so it also affects whether your mail is delivered.

SPF, DKIM and alignment

  • SPF lists the servers allowed to send for your domain. Keep exactly one record and no more than 10 DNS lookups.
  • DKIM signs each message; receivers check the signature against a public key in your DNS.
  • DMARC passes when SPF or DKIM passes and the domain it checked matches (aligns with) the domain in the visible From address.

The rollout path

p=noneMonitorp=quarantineFailing mail to spamp=rejectFailing mail refusedReview reportsReview reports
Move one step at a time. Review aggregate reports before each move, and only advance when every legitimate sender passes.
  1. Publish v=DMARC1; p=none; rua=mailto:… to start receiving aggregate reports. Nothing is blocked yet.
  2. Read the reports for a few weeks of normal business, including month-end and any campaigns.
  3. Fix every legitimate sender until it passes with alignment (usually by enabling DKIM in that service).
  4. Move to p=quarantine. The current DMARC standard (RFC 9989, May 2026) dropped the old pct= tag; for a trial run, add t=y, which asks receivers to apply one step below your stated policy.
  5. When reports show only spoofed or unknown mail failing, move to p=reject.

Finding every sender

Aggregate reports show which IP addresses send as your domain and whether they pass. Typical senders beyond your mailbox provider: CRM and marketing tools, helpdesk, billing and invoicing systems, HR and payroll platforms, website contact forms and scanners or printers that email documents. Each needs DKIM signing with your domain, or an SPF include with an aligned return path.

Common pitfalls

  • Two SPF records, or one that goes over 10 lookups: SPF fails for everyone.
  • Staying at p=none for years. It gives reports but no protection.
  • Forgetting subdomains. Use sp= to set their policy.
  • No rua address, so you can't see what would break before you tighten.

After p=reject

Keep reading reports: new tools get added and keys rotate. Consider MTA-STS and TLS reporting for encrypted delivery, and BIMI if you want your logo shown in supporting inboxes.

[01]FAQ

DMARC to p=reject: common questions.

Still have questions?

info@cloudcyber.co.in

p=none only monitors: receivers send you reports but deliver failing mail normally. p=quarantine asks them to treat failing mail as suspicious, usually the spam folder. p=reject asks them to refuse it outright. Start at none, fix every legitimate sender, then step up.

Long enough to see every service that sends as your domain in the aggregate reports, typically a few weeks covering a full billing and payroll cycle. Move on once legitimate mail passes consistently.

Only if a legitimate sender is not aligned with SPF or DKIM. That is why you fix senders first and can use pct or t=y to step up gradually.

Yes. Without an rua address you are enforcing blind; aggregate reports show who sends as your domain and whether it passes.

[03]Contact

Let's build what's next.

Tell us about your infrastructure, security or automation goals. We reply with questions, then a written plan with scope and next steps.

Response
Usually within one business day
Location
Worldwide

What happens next

  1. 01

    Reply

  2. 02

    Discovery call

  3. 03

    Proposal

We use these details to reply to your enquiry and, if you allowed advertising cookies, to measure which ads lead to enquiries. Our Privacy Notice explains retention and your rights.