Since February 2024, Gmail and Yahoo treat email from a poorly configured domain differently. Every sender must at least authenticate its messages with SPF or DKIM; bulk senders must also publish a DMARC policy. Outlook.com added similar rules in May 2025.
These rules are not a law: they are the mailbox providers' own conditions. But their inboxes hold a large share of your customers and prospects. A non-compliant domain sees its email filtered as spam, or even rejected.
What Gmail requires
Google sets two levels, in force since February 1, 2024.
Every sender to a Gmail account must, among other things:
- authenticate messages with SPF or DKIM;
- have valid forward and reverse DNS records for its sending servers;
- use a TLS connection;
- keep the reported spam rate, as measured in Postmaster Tools, below 0.3%.
Above 5,000 messages a day to Gmail accounts, senders also need:
- SPF and DKIM;
- a published DMARC policy;
- a sending domain (the From header) aligned with the SPF or DKIM domain;
- for marketing and subscribed messages, one-click unsubscribe (
List-UnsubscribeandList-Unsubscribe-Postheaders).
Google recommends keeping the spam rate below 0.1% and never reaching 0.3%.
What Yahoo requires
Yahoo says its rules apply "beginning in February 2024", rolled out gradually over the first half of 2024.
Every sender must, among other things, implement SPF or DKIM at a minimum, keep the spam rate below 0.3% and have valid forward and reverse DNS records.
Bulk senders must also have SPF and DKIM, a valid DMARC policy (at least p=none) that passes, and one-click unsubscribe, honored within two days. Yahoo does not set a numeric threshold for "bulk".
What about Outlook.com?
Since May 5, 2025, Microsoft applies similar rules to domains sending more than 5,000 messages a day to Outlook.com, Hotmail and Live: SPF and DKIM must pass, and DMARC must be published at least at p=none, aligned with SPF or DKIM. Non-compliant messages go to the Junk folder; Microsoft says they will be rejected later.
Is my domain affected?
Yes, as soon as it sends email to Gmail or Yahoo addresses, even a little: the "every sender" requirements have no threshold. The 5,000-a-day threshold only applies to the additional rules.
One point is often missed: a sending tool (newsletter, CRM, invoicing) that sends on behalf of your domain must also be authorized in your SPF record or sign with DKIM using your domain.
Check your domain for free. The AttackScout audit reads your domain's public SPF and DMARC records and tells you what is missing. Run the audit
How to comply
- SPF: a single TXT record that lists every service sending for you. Test it with our SPF tool.
- DKIM: turn on signing in your mailbox service and in each sending tool, then publish the key in your DNS. Our DKIM tool checks that it is online.
- DMARC: start with
p=noneand a report address (rua), then tighten the policy once the reports are clean. Check it with our DMARC tool.
Our step-by-step guides cover the main providers, for example DMARC at GoDaddy or at Cloudflare. If your email already lands in spam, read why emails go to spam.
Frequently asked questions
I send fewer than 5,000 emails a day: am I fine?
No. At both Gmail and Yahoo, every sender needs at least SPF or DKIM. Publishing DMARC as well costs nothing and protects your domain against spoofing.
Is DMARC at p=none enough?
For the bulk-sender rules of Gmail, Yahoo and Outlook.com, a p=none policy is accepted. It does not block any spoofing, though: it is a starting point, not protection.
Are these rules a legal obligation?
No. They are the mailbox providers' conditions. They decide what reaches the inbox, which is enough to make them unavoidable.
All the dates are in our deadline calendar.
Sources
Checked on November 16, 2026.
- Google, Email sender guidelines: https://support.google.com/a/answer/81126
- Yahoo, Sender Best Practices: https://senders.yahooinc.com/best-practices/
- Microsoft, Strengthening Email Ecosystem: Outlook's New Requirements for High-Volume Senders: https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730