DMARC Explained: Why Gmail and Yahoo Now Require It
Home ยป DMARC Explained: Why Gmail and Yahoo Now Require It
See How My Agency DIGIBROOD Can Drive Real Growth for Your Business
Digital Marketing โ performance-driven strategies to generate high-quality leads and consistent sales.
Website Development โ fast, conversion-focused websites built to scale your business online.
WhatsApp & Bulk Marketing โ powerful automation tools to reach thousands of customers instantly.
Data & Lead Solutions โ verified, targeted databases to boost your outreach and ROI.
We donโt just offer servicesโwe build systems that grow your business.
DMARC is a DNS record that tells mailbox providers what to do with email that fails SPF and DKIM checks for your domain, and where to send you reports. Since 2024, Google and Yahoo expect bulk senders to have SPF, DKIM and a DMARC policy. Start with p=none, read the reports, then move to quarantine and reject when all your real senders pass.
What changed for senders
For years, DMARC was optional. In 2024, Google and Yahoo began asking senders of large volumes of email to authenticate it properly. Google talks about senders of about 5,000 or more messages a day to Gmail addresses, and Microsoft has brought in similar requirements for Outlook.com. You can read each providerโs own wording in Googleโs sender guidelines and Yahooโs best practices.
Each provider has its own idea of โbulkโ, and mail from domains without authentication is judged more harshly even below those volumes. So the practical advice is simple: if you send business email, set up DMARC.
What DMARC does
Two things. First, it connects SPF and DKIM to the address people see in the From line. Second, it lets you choose what receivers do when a message fails. It also gives you reports, so you can see who sends mail using your domain.
A starter DMARC record, published as a TXT record at _dmarc.yourdomain.com
v=DMARC1; p=none; rua=mailto:[email protected]
| Tag | Meaning |
|---|---|
v=DMARC1 |
Version. Always first. |
p= |
The policy for your domain: none, quarantine or reject. |
rua= |
Where aggregate reports are sent. |
sp= |
Optional policy for subdomains, if you want it to differ. |
Alignment: the part that trips people up
DMARC passes only when SPF or DKIM passes and the domain that passed matches the From domain. This is called alignment. It is why a message can pass SPF and still fail DMARC: the server that sent it is allowed, but it is using a different domain in its technical headers.
This is common with third-party tools such as email service providers, CRMs and help desks. They often need a custom return-path or their own DKIM domain set up, so that the signature aligns with your domain.
In a Gmail message, open Show original. You will see SPF, DKIM and DMARC, each with PASS or FAIL. If SPF or DKIM says PASS but DMARC says FAIL, look at alignment.
Want us to set this up for you?
We find every system that sends email for your domain, fix SPF, turn on DKIM, and roll out DMARC in stages, so nothing real gets blocked. Then we test it and show you the results.
The three policies
| Policy | What receivers do | When to use it |
|---|---|---|
p=none |
Nothing changes. You only get reports. | Start here, for a few weeks. |
p=quarantine |
Failing mail goes to spam. | When reports show your real senders pass. |
p=reject |
Failing mail is refused. | The strongest protection against spoofing. |
A safe rollout in six steps
- List every senderOffice mail, your website, CRM, billing, newsletter and support tools, and any agency sending for you.
- Fix SPF and DKIMOne valid SPF record, and DKIM enabled and verified for each platform.
- Publish
p=noneWith a mailbox, or a reporting service, to receive the reports. - Read the reportsLook for legitimate sources that fail, and for sources you do not recognise.
- Fix what failsSet up alignment for each real sender, using their custom domain options.
- Tighten the policyMove to quarantine, watch for problems, then move to reject.
The standard is defined in RFC 7489, and dmarc.org has a good overview. If you would rather have it done and tested for you, see our DMARC, SPF and DKIM setup service.
Frequently asked questions
Is DMARC mandatory?
For bulk senders to Gmail and Yahoo, a DMARC policy is now expected. For everyone else, it is strongly recommended, because it protects your domain from spoofing and helps deliverability.
Will DMARC make all my emails reach the inbox?
No. It is required for the inbox, but it is not a guarantee of the inbox. Reputation, content and list quality still matter.
What is the safest first policy?
p=none with reporting. It blocks nothing, and it shows you what is happening before you enforce anything.
Do I need DMARC for subdomains?
A subdomain inherits the domain policy unless you set sp= or publish a separate record. If you send from a subdomain, make sure it is authenticated too.
How long should I stay on p=none?
Long enough to see all your real senders in the reports and fix them. For many domains that is a few weeks. There is no fixed number.
Want us to set this up for you?
We find every system that sends email for your domain, fix SPF, turn on DKIM, and roll out DMARC in stages, so nothing real gets blocked. Then we test it and show you the results.