DMARC p=reject versus p=quarantine for cold email sending domains in 2026 and why the policy you choose affects inbox placement in ways most guides never explain
dmarc_policy_sasha · 2026-09-12 · 0 views
Every DNS guide for cold email says set DMARC to p=none, then p=quarantine, then p=reject. That advice is mostly right. The part nobody explains is what actually happens to your inbox placement at each stage and why moving to p=reject too early can cause problems that look like deliverability failures but are actually policy configuration issues.
Here's what I've learned across 40-plus domain setups over the last two years.
p=none: DMARC is monitoring only. Failed DMARC checks on your domain don't affect delivery. The receiving server logs the failure but takes no action. If your SPF or DKIM is misconfigured, p=none protects you from losing emails while you fix it. Start every new domain here for at least two weeks while you confirm your SPF and DKIM are passing cleanly.
p=quarantine: Failed DMARC checks route to spam. This is where most cold email domains should land permanently if you're running campaigns through a single sending platform like Instantly or Smartlead. It signals to receiving servers that your domain is being monitored and that you care about authentication. GlockApps placement scores improve modestly on some providers when you move from p=none to p=quarantine. I've seen 2 to 4 percentage point improvements on the Microsoft network specifically.
p=reject: Failed DMARC checks are rejected outright. This is appropriate for your main company domain, not your cold email sending domains. Here's the problem: if you run multiple sending platforms or any third-party tool that sends on your domain's behalf, a misconfigured SPF record at p=reject causes legitimate sends to bounce. I've watched agencies burn sending domains because they moved to p=reject before they had SPF and DKIM perfectly aligned across every tool sending from that domain.
My setup: PuzzleInbox handles DNS for my sending domains. They configure SPF and DKIM correctly on delivery. I set DMARC manually to p=quarantine once the domain is live. I stay at p=quarantine for cold email domains. p=reject is only for domains I own that never send cold email.
Check your DMARC reports with a free tool like dmarcian or EasyDMARC before you change your policy level. The reports show you exactly which servers are sending on your behalf and whether they're passing or failing authentication. One misconfigured sending source at p=reject causes bounces you won't immediately trace back to DNS.