DMARC is a DNS record that tells receiving mail servers what to do with email that fails authentication for your domain. It builds on SPF and DKIM. The policy you choose, set with the p tag, decides how strict that handling is.
How it works
p=none
No action is taken on email that fails DMARC. Use it to monitor and collect reports without affecting delivery.
p=quarantine
Email that fails DMARC is treated as suspicious and may go to the spam folder.
p=reject
Email that fails DMARC is rejected and doesn't reach the recipient. Check your setup carefully first, so you don't block legitimate email.
Applying a policy to part of your mail
The pct tag applies quarantine or reject to a percentage of failing email. For example:
v=DMARC1; p=quarantine; pct=50A lower percentage has a smaller effect. A higher percentage makes it more likely that failing email goes to spam or is rejected.
When to use it
Start with
p=noneto see authentication problems without affecting delivery.Move to
p=quarantine, thenp=reject, once your authentication is set up correctly.
Good to know
DMARC is one factor in deliverability. Sender reputation, content and recipient engagement also matter.
DMARC uses the results of SPF and DKIM. DKIM signs your email so receivers can check it wasn't changed in transit.
FAQ
Which DMARC policy should I start with?
Start with p=none. It lets you monitor authentication issues without affecting delivery. Then move to stricter policies step by step.
Should I set p=reject straight away?
No. Make sure your email authentication is set up correctly first. Starting with p=none or p=quarantine helps you avoid blocking legitimate email.
What's the difference between a DMARC record and a DKIM record?
A DKIM record lets receivers check your email's signature. A DMARC record tells receivers what to do when an email fails authentication.
Still stuck? Contact support from the chat in your Smartlead dashboard.
