Valeriia Horbenko
Home / Blog / DMARC

How to move DMARC from p=none to quarantine safely

Short answer

Turn on DMARC reports, collect two to four weeks of data, make every legitimate sender pass with aligned SPF or DKIM, wait for clean reports, then switch to p=quarantine. Skip pct: it was removed from the DMARC spec in May 2026.

Why p=none isn't the finish line

A DMARC record with p=none ticks the box for Gmail and Yahoo's bulk sender rules. It also tells every inbox provider to do nothing with email that fails authentication. Anyone can still send email that looks like it comes from your domain, and your policy won't stop it.

p=none is meant to be a starting point: you watch first, then you enforce. A lot of domains set it once and never come back.

Step 1: Turn on reports

Without reports you're moving to enforcement blind. Add a rua address to your record:

v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Inbox providers will start sending daily XML reports listing every server that sent email as your domain and whether it passed. They aren't meant to be read raw, so use a report parser. There are free tiers that are fine for a single domain.

Step 2: List every sender

Give it two to four weeks so you catch monthly sends like invoices and newsletters. Then go through the sources in the reports and sort them into three groups:

  • Yours and passing. Leave them alone.
  • Yours and failing. The support desk, the billing system, the tool someone in sales connected. These are your to-do list.
  • Not yours. Spoofing attempts, plus forwarding services that resend your mail. These are what enforcement is for.

Step 3: Make every real sender pass with alignment

DMARC passes when SPF or DKIM passes and the domain it passed for lines up with the domain in the From address. By default the match is relaxed, so mail.yourdomain.com lines up with yourdomain.com.

In practice, DKIM is the more reliable route. Most platforms let you set up DKIM on your own domain with a couple of DNS records. SPF often can't align, because many tools use their own bounce domain. If a sender passes neither, it will fail as soon as you enforce.

Step 4: Wait for clean data

Don't switch the day you fix the last sender. Watch the reports for another week or two and check that every source you recognise is now passing. Look at volume too: a tool that sends once a month might not have shown up yet.

Step 5: Switch to quarantine

v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com

With p=quarantine, email that fails DMARC goes to spam instead of the inbox. That's a much softer landing than reject if you've missed something.

What about pct and the new t tag?

Older guides tell you to ramp up with pct=10, then 25, then 50. In May 2026 the DMARC specification was republished as RFC 9989, and pct was removed. Receivers applied it inconsistently anyway. Its replacement is a simple testing flag: t=y asks receivers to apply one level less than your policy while you test.

Receivers are still catching up with the new tags, so I treat t=y as a nice extra, not the safety net. The real safety net is clean reports before you switch.

Step 6: Don't forget subdomains

Your policy covers subdomains unless you say otherwise with sp=. Check that you haven't left sp=none in place. The new spec also adds np=, a policy for subdomains that don't exist at all. Attackers like those, because nobody watches them.

Step 7: Decide on reject, or don't

p=reject tells receivers to refuse failing email outright. It's the strongest protection, but email that gets forwarded through mailing lists can fail DMARC through no fault of yours, and with reject it simply disappears. The updated spec no longer presents reject as the goal for everyone.

For most SaaS teams, a well-monitored quarantine is a solid place to stay. Move to reject if your domain is being actively spoofed and you're confident no legitimate flow depends on forwarding.

Quick questions

How long should I stay on p=none?

Long enough to see every regular sender in your reports, usually two to four weeks, plus however long it takes to fix the ones that fail.

Will quarantine block my own emails?

Only the ones that fail DMARC, which is why you fix every legitimate sender first. With quarantine they go to spam rather than disappearing, so mistakes are easier to spot.

Do I still need pct=?

No. RFC 9989 removed pct. If you want a testing phase, the new flag is t=y, though receiver support is still growing.

V
Valeriia Horbenko

Email retention marketer working with B2B SaaS. I fix email authentication and build lifecycle sequences, everything over email.

Want me to check your domain?

Run the live check on my homepage, or send me your domain and get a one-page report within one business day. Free.

Run the live check →
© 2026 Valeriia Horbenko. All rights reserved.Privacy policyTerms of serviceBusiness detailsLinkedInTelegram