Email Security21 April 2026· 8 min read· Enet Engineering8 views0 found this helpful

DMARC Rollout Guide: Moving Safely from p=none to p=reject

A step-by-step plan to reach full DMARC enforcement without blocking your own invoices, newsletters or CRM emails — including how to read aggregate reports.

Three shields growing stronger on rising steps beside a report chart

Publishing a DMARC record with p=none is a good start, but it protects nobody: receivers still deliver spoofed mail. Real protection only comes at p=quarantine or p=reject. The challenge is getting there without accidentally blocking your own legitimate email. Here is the process we follow for customers.

Step 1: Monitor (p=none) — 2 to 4 weeks

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

Collect aggregate (RUA) reports from Google, Microsoft, Yahoo and others. They are XML files listing every IP that sent mail as your domain and whether SPF and DKIM passed and aligned. Use a DMARC report viewer rather than reading raw XML.

Step 2: Inventory every legitimate sender

Reports almost always reveal surprises. Typical senders for a Kenyan SME include:

  • Your mailbox provider (Enet Business Email, Microsoft 365, Google Workspace or Zoho).
  • Your website contact forms and WooCommerce order emails.
  • Accounting and ERP systems sending invoices and statements.
  • WHMCS or billing platforms, CRM and helpdesk tools.
  • Newsletter and bulk SMS/email platforms.

For each, set up DKIM signing with your domain and add it to SPF where needed — remembering SPF's 10-lookup limit. A single authenticated SMTP relay for applications simplifies this a lot.

Step 3: Quarantine gradually

v=DMARC1; p=quarantine; pct=25; rua=mailto:[email protected]

The pct tag applies the policy to a percentage of failing mail. Go 25% → 50% → 100% over a few weeks, watching reports and asking finance and sales whether anything went missing.

Step 4: Reject

v=DMARC1; p=reject; rua=mailto:[email protected]; adkim=s; aspf=s

At p=reject, spoofed messages are refused outright. You are now eligible for BIMI logo display and have closed the door on exact-domain impersonation.

Don't forget subdomains and parked domains

Use the sp= tag to set a subdomain policy. For domains that never send email — brand-protection registrations, for example — publish v=spf1 -all and v=DMARC1; p=reject so criminals cannot use them either.

Common rollout problems

  • Forwarding: mailing lists and forwarders can break SPF. DKIM usually survives, which is why DKIM on every sender matters.
  • Third-party senders using their own domain in the envelope — fix with custom DKIM.
  • Reports going to an unread mailbox. Assign someone to review them monthly.

Tools to help

Build your record with our DMARC generator, then verify with the DMARC checker, SPF checker and DKIM checker. DMARC protects your domain outbound; spam filtering protects your inbox from everyone else's spoofed mail. Background reading: DMARC.org overview.

Share this article

Was this article helpful?

Your vote helps us write better guides.

Need a hand implementing this?

Enet engineers in Nairobi handle migrations, SSL installs, M-Pesa and eTIMS integrations for you.

Launch today

Powering Your Online Success!

Domain, hosting, email and SSL from one local team — set up in minutes and backed by people you can call.

  • Free SSL
  • Free migration
  • 99.9% uptime
  • 24/7 expert support

Start with your domain

Check availability, then add hosting in the same order.

Prefer to talk? Call +254 726 872 512