Learn
Gmail bulk sender requirements, plus Yahoo and Outlook rules
What Gmail, Yahoo and Outlook.com require from bulk senders: SPF, DKIM, DMARC at p=none or stricter, From: alignment and unsubscribe rules.
What changed
Gmail bulk sender requirements oblige anyone sending close to 5,000 or more messages a day to personal Gmail accounts to authenticate with SPF and DKIM, publish DMARC, align the From: domain and offer one-click unsubscribe on marketing mail. SPF lists the servers allowed to send for your domain. DKIM signs each message. DMARC tells receivers how to treat mail that fails those checks and where to send reports.
Gmail's rules date from February 1, 2024. Yahoo began enforcing similar rules that month, and Outlook.com followed on May 5, 2025.
Gmail bulk sender requirements: 2026 update
Google's official guidelines date no new requirement to 2026, and Yahoo's requirements page and FAQ date none to 2025 or 2026. Gmail's enforcement did change: since November 2025 it has been ramping up temporary and permanent rejections.
By status class (RFC 3463), 4.7 codes are temporary and 5.7 codes permanent:
| Problem | Temporary | Permanent |
|---|---|---|
| Reverse DNS | 4.7.23 |
5.7.25 |
| SPF | 4.7.27 |
5.7.27 |
| TLS | 4.7.29 |
5.7.29 |
| DKIM | 4.7.30 |
5.7.30 |
| From: alignment | 4.7.32 |
5.7.32 (Google's table shows reply 421) |
| No DMARC record or policy | 4.7.40 (4.7.31 in Google's FAQ) |
5.7.40 |
550 5.7.26 covers unauthenticated mail in three documented wordings. Meanings vary by server: Gmail uses 5.7.27 for SPF, but the IANA registry defines X.7.27 as a sender address with a null MX.
Microsoft's pages disagree on Junk or rejection. Its policy page says Junk first, then possible rejection with:
550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level.
Plan for rejection and check Junk too.
Who is affected
| Gmail | Yahoo | Outlook.com | |
|---|---|---|---|
| Recipients | @gmail.com and @googlemail.com addresses | All domains and consumer brands hosted by Yahoo Mail | Hotmail, Live.com, Outlook.com; the support article adds MSN |
| Bulk means | Close to 5,000 or more in 24 hours (guidelines: more than 5,000 a day) | "A significant volume of mail", with no number | More than 5,000 a day (support article: 5,000 or more, no period given) |
Google counts subdomains together: 2,500 from example.com plus 2,500 from promotions.example.com makes 5,000. Once a From: domain reaches Microsoft's threshold, Microsoft expects all its mail to comply.
Smaller senders still have rules. Gmail and Yahoo require SPF or DKIM, valid forward and reverse DNS, RFC 5322 format and a spam rate below 0.3%. Gmail adds TLS; Yahoo adds RFC 5321. Microsoft strongly recommends SPF, DKIM and DMARC for all senders.
Checklist
| Bulk tier | Gmail | Yahoo | Outlook.com |
|---|---|---|---|
| SPF and DKIM | Both | Both | Both must pass |
| DMARC | At least p=none |
At least p=none, must pass |
At least p=none, must pass |
| From: aligned with SPF or DKIM | One is enough | One is enough | One is enough, both preferred |
| Reverse DNS | Required | Required | Required |
| TLS | Required | Not listed | Not listed |
| One-click unsubscribe | RFC 8058, marketing mail | Marketing mail, mailto: accepted |
One-click not listed; requires a clearly documented, easy-to-find unsubscribe |
| Honor unsubscribes | 48 hours (recommended; missing it loses Google's delivery support) | 2 days | No deadline documented |
| Spam rate | Below 0.3%, ideally below 0.1% | Below 0.3% of inbox mail | No requirement; Microsoft suggests a complaint rate below 0.3% per IP |
-
List every service that sends as your domain: mail host, marketing platform, CRM, website forms.
-
Publish one SPF record naming them all. Caution: a second record returns
permerror, as does passing 10 DNS lookups. A service you omit fails SPF. -
Turn on DKIM in each service, signing with your domain and a key of at least 1024 bits. Google and Yahoo recommend 2048. Caution: add the key to DNS before turning on signing.
-
Align each service with your From: domain through its return path (the bounce address) or DKIM signature. Caution: publish the records the service asks for before you switch it.
-
Publish DMARC if
_dmarc.example.comhas no record:TXTv=DMARC1; p=none; rua=mailto:dmarc@example.com
Yahoo strongly recommends
rua, and aggregate reports show senders you missed. Caution: if a record exists, edit it and keep itspvalue, because receivers discard all records at a name that has more than one. None of these rules requiresquarantineorreject, and both can stop legitimate mail. RFC 9989 says to fix legitimate sources first. -
Ask whoever controls the sending IP to set reverse DNS. Each sending IP needs a PTR record for a hostname that resolves back to that IP. It lives outside your domain's DNS, so your hosting or email provider sets it. Test it with the reverse DNS lookup.
-
Add one-click unsubscribe to marketing mail, plus a visible link in the body:
List-Unsubscribe-Post: List-Unsubscribe=One-ClickList-Unsubscribe: <https://example.com/unsubscribe/opaque-token>RFC 8058 requires an HTTPS URL identifying the recipient and list, no redirect and a DKIM signature covering both headers.
-
Watch complaints in Postmaster Tools (Google's sender dashboard) and Yahoo's Complaint Feedback Loop.
Check your domain
- Run the email security check. It reads SPF, DKIM and DMARC from public DNS and tries common DKIM selectors (key names), so a custom one can show as missing. It cannot see reverse DNS, TLS, spam rate or unsubscribe headers.
- Send a test to a Gmail account you control. Click More next to Reply, then Show original, and paste the headers into the email header analyzer. Repeat with Yahoo and Outlook.com mailboxes.
- Open Compliance status in Postmaster Tools. Google says a fix can take up to 7 days to appear.
- Do not retry a message that bounced with a 5xx code. Microsoft and Yahoo both say not to. Fix the cause, then send a new message.