A monitoring DMARC policy is the safest way to start with DMARC. You publish a TXT record with p=none, which tells receiving mail servers: don’t block or quarantine anything yet, just send me reports. You see who is sending mail in your name without breaking real traffic.
In one line p=none = visibility, no enforcement. It’s the recommended first step before moving to quarantine or reject.
The three DMARC policy modes
| Policy | What happens to failed mail |
|---|---|
| p=none (monitoring) | Delivered as usual. Aggregate reports are sent to your rua address. |
| p=quarantine | Failed mail is moved to junk/spam. |
| p=reject | Failed mail is bounced and never reaches the inbox. |
Why start with monitoring?
It lets you find every legitimate sender that uses your domain — CRM, billing platform, helpdesk, Mailpro itself — and authenticate them with SPF and DKIM before any enforcement. Skipping this step is the most common reason real emails get blocked when you switch to p=quarantine or p=reject.
Stay in monitoring long enough Plan at least 2–4 weeks of reports before tightening the policy. Stop only once 100% of legitimate sources align on SPF and DKIM.
Set up DMARC monitoring with Mailpro
Generate a record from the DMARC tool, follow configure DMARC with Mailpro, and check DMARC policy not enabled if your record is missing or invalid.