February 2024: authentication stops being best practice and becomes the gate
Since February 2024 Gmail and Yahoo require bulk senders to use SPF, DKIM, DMARC and one-click unsubscribe, with spam under 0.3%. Outlook.com followed in 2025.
Key takeaways
- Since February 1, 2024, Gmail and Yahoo require every sender to authenticate with SPF or DKIM and to keep reported spam below 0.3%.
- Senders of about 5,000 or more messages a day to Gmail must publish SPF, DKIM and DMARC with an aligned From: domain and support one-click unsubscribe. The count covers the whole primary domain, and bulk status is permanent.
- Microsoft applied matching authentication rules to Outlook.com from May 5, 2025, rejecting non-compliant mail from domains sending over 5,000 messages a day.
- Provider rules are now stricter than the law: CAN-SPAM allows ten business days to honor an opt-out, and Yahoo requires two.
Since February 1, 2024, Gmail and Yahoo require every sender to authenticate its mail and keep reported spam below 0.3%, and bulk senders (at Gmail, around 5,000 messages a day) must also publish SPF, DKIM and DMARC and support one-click unsubscribe. Microsoft applied matching authentication rules to Outlook.com from May 5, 2025. Authentication stopped being best practice and became the gate: if your sending domain fails it, nothing else you do in outbound matters.
What changed in February 2024?
Google announced the rules on October 3, 2023. At the time, it said Gmail's defenses were blocking nearly 15 billion unwanted emails every day, and that its 2022 requirement for some form of authentication had already cut the unauthenticated messages Gmail users received by 75%. Yahoo backed the change in the same announcement, and its Sender Hub published matching requirements, with enforcement rolled out gradually from February 2024. Microsoft announced its own on April 2, 2025 for Outlook.com, Hotmail and Live addresses.
| Requirement | Gmail (Feb 2024) | Yahoo (Feb 2024) | Outlook.com (May 2025) |
|---|---|---|---|
| Every sender | SPF or DKIM; valid forward and reverse DNS; TLS; reported spam below 0.3% | SPF or DKIM; valid forward and reverse DNS; spam rate below 0.3% | Rules aimed at domains over 5,000 a day |
| Volume line | About 5,000 a day to Gmail accounts, counted across the primary domain | No number: "a significant volume of mail" | Over 5,000 a day |
| Authentication at volume | SPF and DKIM; DMARC at least p=none; From: aligned with SPF or DKIM | SPF and DKIM; DMARC at least p=none, and DMARC must pass | SPF and DKIM must pass; DMARC at least p=none, aligned with SPF or DKIM |
| Unsubscribe | One-click for marketing and subscribed mail, plus a visible link | One-click header, a visible link, honored within 2 days | A functional unsubscribe link, as a recommendation |
| If you fail | Delivery problems; since November 2025, temporary and permanent rejections | Negative impact on delivery at Yahoo domains | Rejected with error 550 5.7.515 |
- SPF and DKIM pass for the sending domain
- DMARC published, at least p=none
- From: domain aligned with SPF or DKIM
- List-Unsubscribe and List-Unsubscribe-Post headers (RFC 8058)
- A visible unsubscribe link in the body
- Honored within two days
- Reported spam below 0.1% as the working target
- Never at or above 0.3%
- Watched in Postmaster Tools, not guessed
What does DMARC at p=none actually require?
Less than it sounds, with one detail worth checking. A DMARC policy of none means, in the words of the current standard, that the domain owner "offers no expression of preference": it asks receivers to block nothing. What the rules do require is that the record exists and that the From: domain your prospects see lines up with a domain that passes SPF or DKIM. Alignment is the part to check, because every tool that sends as your domain, from the sequencer to the CRM to the marketing platform, needs its own SPF or DKIM setup to pass it. DMARC itself moved from an informational document (RFC 7489, 2015) to a Proposed Standard, RFC 9989, in May 2026.
Do the rules apply to a small B2B sales team?
Read the fine print, because it cuts both ways. Google's FAQ says its sender requirements and enforcement apply only to mail sent to personal Gmail accounts, not to Google Workspace accounts. Microsoft's rules cover its consumer addresses. Dana Reyes reads her mail at northwind.com, not at gmail.com. And a team of four reps sending fifty emails a day each is nowhere near 5,000.
Meet the volume rules anyway, for three reasons.
- The count is your whole domain, not your sales team. Google counts every message sent from the same primary domain to personal Gmail accounts, subdomains included, toward the 5,000. Product notifications and the marketing newsletter count too, and may already have put your company over the line.
- The status does not expire. Google's FAQ is explicit.
Senders who meet the above criteria at least once are permanently considered bulk senders.
- The rules describe a trusted sender, whoever enforces them. SPF, DKIM, DMARC and one-click unsubscribe are open standards, and every receiving filter can read them. Our read: a sender that passes all of them is easier to trust at Workspace and Microsoft 365 companies too, even where no published rule requires it.
Why did more domains make outbound harder to run?
The sender side of this era is more throughput across more domains and mailboxes. Spreading volume over separate domains keeps each one under the line, and multiplies the work: every domain needs its own SPF, DKIM and DMARC records, its own monitoring and its own history. Ten lookalike domains are ten pieces of production infrastructure, and in a company with a first head of sales and no sales operations hire, one person owns all of them.
The stricter view is worth knowing too. M3AAWG's sender best practices define cold email as unsolicited email that tries to start a business relationship with someone who has no prior relationship with the sender, and say the group views such email as abusive. Microsoft's hygiene recommendations for large senders ask them to make sure recipients have consented. The law is looser: CAN-SPAM, as the FTC's guide describes it, makes no exception for business-to-business email, asks for an opt-out rather than prior consent, and allows ten business days to honor it. Yahoo allows two. The provider rules are now stricter than the law, and the providers decide placement.
- Part 12001 to 2010Sending technologyCommercial email infrastructureSelf-serviceSend APIsBulk listsMailbox defenseRule-based spam filteringRulesBlocklistsContent scoring
- Part 22011 to 2017Sending technologySequencing turns follow-up into a systemSequencesSales engagementFollow-upMailbox defenseAdaptive filtering and sender reputationReputationEngagementAdaptive filters
- Part 32018 to 2021Sending technologyData connects to executionEnrichmentCRM syncSignalsMailbox defenseIdentity becomes a stronger signalDomain identityAlignmentFeedback
- Part 42021 to 2023Sending technologyMulti-mailbox scale meets generative draftingMailbox rotationWarmupAI draftingMailbox defensePattern recognition learns fasterBehaviorInfrastructureFeedback loops
- Part 5Feb 2024 to 2025Sending technologyMore throughput, more identity fragmentationOrchestrationAI researchMore capacityMailbox defense · formal enforcementAuthentication becomes a hard gateSPF · DKIM · DMARCOne-click opt-outSpam < 0.3%
- Part 62026 to 2027Sender capabilityResearch and drafting become nearly freeAgent researchDynamic variantsReply routingInbox prioritizationVisibility becomes the next gateRelationship contextMessage contextPriority visibility
What era five means for a head of sales in 2026
- Audit every sending domain before the next campaign. SPF and DKIM passing, DMARC published and aligned. Postmaster Tools now has a compliance status dashboard that shows this for Gmail.
- Put a one-click opt-out in cold email too, with a visible link, and honor it within two days. Google ties fast unsubscribes to fewer spam reports.
- Watch the spam rate against 0.1%, not 0.3%. In a small campaign the arithmetic is unforgiving: one report among 300 emails delivered to Gmail users is 0.33%.
- Check authentication automatically. Records drift when someone changes DNS or adds a tool. Part 13 treats that drift as a known event that should be caught and fixed without waiting for a person, and part 12 makes sender health the first layer of any reply-rate diagnosis.
Next in the series
Part 6 looks at 2026 and 2027, when research and drafting became nearly free and Gmail's AI Inbox started deciding what a reader sees first, so delivery stopped meaning attention. For the shortcuts these rules answered, see part 4. The series page lists every part in order.
Common questions
- Do Gmail's bulk sender rules apply to cold email sent to company addresses?
- Google's FAQ says its requirements and enforcement apply only to mail sent to personal Gmail accounts, not to Google Workspace accounts, and Microsoft's 2025 rules cover Outlook.com consumer addresses. But the 5,000-a-day count includes every message sent from your primary domain, subdomains included, and bulk status is permanent once reached. Meet the rules regardless: they are open standards every filter can read.
- What spam complaint rate is too high?
- Gmail and Yahoo both publish 0.3% as the limit. Google's guidelines ask senders to keep the rate reported in Postmaster Tools below 0.1% and never reach 0.3%. In a small cold campaign a single report moves the number fast: one report among 300 emails delivered to Gmail users is 0.33%.
- How fast must an unsubscribe be honored?
- The FTC's CAN-SPAM guide allows ten business days. Yahoo requires bulk senders to honor unsubscribes within two days, and Google said in 2023 that bulk senders must process them within two days and recommends 48 hours in its FAQ. The provider rule is the stricter one, and it is the one that decides placement.
Sources
- Google, Email sender guidelines (requirements from February 1, 2024)
- Google, Email sender guidelines FAQ (bulk status, Workspace scope, November 2025 enforcement)
- Google, New Gmail protections for a safer, less spammy inbox, October 3, 2023
- Yahoo Sender Hub, Sender best practices and requirements
- Yahoo Sender Hub, FAQs (no volume threshold specified for bulk senders)
- Microsoft, Strengthening Email Ecosystem: Outlook's New Requirements for High-Volume Senders, April 2, 2025 (updated April 29)
- Google, Postmaster Tools dashboards (compliance status, spam rate)
- IETF, RFC 8058: Signaling One-Click Functionality for List Email Headers, January 2017
- IETF, RFC 9989: DMARC, May 2026
- FTC, CAN-SPAM Act: a compliance guide for business
- M3AAWG, Sender Best Common Practices, version 4.0, August 2026 (section 4.5, cold email)
Written by Jared Hawkins-Young from the system he builds and runs. Diagrams are drawn from the same specs as the software. Published October 8, 2026. Illustrative numbers are labelled as such; every other figure carries its source.