Gmail And Yahoo Sender Requirements: What Changed In 2024
Both mailbox providers rolled out enforceable sender rules in February 2024. In November 2025 Gmail ramped up enforcement on non-compliant traffic. Here is the working summary.
In October 2023 Google and Yahoo jointly announced new sender requirements that began taking effect in February 2024. In November 2025 Google confirmed it was ramping up enforcement on non-compliant traffic to Gmail personal accounts. The rules are documented in Google's Email sender guidelines and Yahoo's Sender Hub 2024 requirements.
Who The Rules Apply To
Both providers define a bulk sender as an authenticated domain or From-header domain sending 5,000 or more messages a day to their consumer inboxes. That threshold is a soft line. Google is explicit that senders below it should still follow the guidelines, and that non-compliant behavior can affect delivery at any volume.
What They Require
- Authenticate outgoing mail. SPF and DKIM on every message, plus a DMARC record on the sending domain with at least
p=none. Alignment must be to the visible From domain. - Send from a domain you own. Do not spoof gmail.com or yahoo.com in your From address. Use a sending subdomain of your product's domain instead.
- Keep spam complaints below 0.3 percent as reported in Google Postmaster Tools. Google's guidance is to stay under 0.1 percent as a healthy target.
- Support one-click unsubscribe (RFC 8058) on subscribed mail. This is a marketing requirement and does not apply to true transactional messages (a receipt is not “subscribed”), but any mixed streams need it.
- Include a visible unsubscribe link in the body of commercial mail.
- Format messages per RFC 5322. Well-formed headers, valid MIME, no forged Message-Id, no missing Date.
What This Means For Transactional Senders
The one-click unsubscribe rule does not apply to genuinely transactional mail like receipts, verification codes, and password resets, because the user did not subscribe to them. What still very much applies to transactional senders:
- Full SPF, DKIM, and DMARC alignment.
- Sending from a subdomain you own, not a free mail domain.
- Not letting your transactional stream share reputation with a noisy marketing stream that will drag your complaint rate up.
- Clean, RFC 5322 compliant headers on every message.
The single most common cause of transactional mail suddenly landing in spam at Gmail after 2024 is a domain whose other mail stream (usually a marketing tool or a support helpdesk) started failing DMARC or generating complaints. Keep transactional on its own subdomain.
References
- Google — Email sender guidelines (support.google.com/mail/answer/81126)
- Google — Sender guidelines FAQ (support.google.com/mail/answer/14229414)
- Yahoo Sender Hub — senders.yahooinc.com
- RFC 8058 — One-Click List Unsubscribe
Send transactional email that lands.
MailRoundup is a transactional-only pipe for receipts, confirmations, password resets, and alerts. One endpoint, honest logs, no marketing traffic in the way.