The bulk sender requirements from Gmail, Yahoo and Microsoft boil down to one list: authenticate with SPF and DKIM, publish DMARC aligned with your From domain, use valid reverse DNS and TLS, offer one-click unsubscribe and honor it within two days, keep the user-reported spam rate below 0.3% (ideally under 0.1%), and send properly formatted messages from a domain you own. Google and Microsoft apply the bulk tier at roughly 5,000 messages a day; Yahoo publishes no number.
This checklist combines all three providers' official rules in one table, shows how to verify each item yourself in a few minutes, and lists the real error codes you will see when something fails.
Key takeaways
- The threshold: Google counts close to 5,000 or more messages to personal Gmail accounts in 24 hours, and once you cross it you are a bulk sender permanently. Microsoft uses 5,000+ messages to its consumer domains.
- Authentication: SPF and DKIM must both pass, and DMARC (at least
p=none) must pass with SPF or DKIM aligned to the From domain. - Unsubscribe: marketing mail needs
List-UnsubscribeplusList-Unsubscribe-Post(RFC 8058) and a visible link in the body. Yahoo requires honoring within 2 days. - Spam rate: Google asks for below 0.10% and never 0.30% or higher; Yahoo asks for below 0.3%.
- Enforcement is real: Gmail ramped up rejections from November 2025, and Outlook.com rejects non-compliant high-volume mail with
550 5.7.515.
Who counts as a bulk sender?
Each provider defines the bulk tier differently, and the details matter because the counting is per domain, not per campaign or per IP.
| Provider | Official definition | Which recipients count | Notes |
|---|---|---|---|
| Google (Gmail) | Sends close to 5,000 messages or more within a 24-hour period | Personal Gmail accounts (@gmail.com, @googlemail.com) | Messages from the same primary domain count together. Status is permanent once reached. |
| Yahoo | No numeric threshold published | Yahoo consumer mailboxes | Separate rule sets for "all senders" and "bulk senders". If you send marketing at any scale, plan to meet the bulk set. |
| Microsoft (Outlook.com) | 5,000 or more messages (the Outlook blog says more than 5,000 a day) | Consumer domains: outlook.com, hotmail.com, live.com | All messages using the same domain in the RFC 5322 From address count together. |
Sources: Google's email sender guidelines FAQ, Yahoo's Sender Hub best practices, and Microsoft's Outlook high-volume sender announcement.
Three counting details people miss
- Subdomains roll up. Google counts by primary domain, so
news.example.comandmail.example.comadd up underexample.com. - It is permanent at Google. One big day (a launch, a Black Friday send) makes you a bulk sender for good. Google's FAQ says changing your sending practices does not remove the status.
- Workspace and Microsoft 365 recipients are different. These rules target consumer mailboxes. Business mailboxes have their own filters, but they also check SPF, DKIM and DMARC, so the checklist helps there too.
If you send fewer than 5,000 a day, you are not off the hook: Google and Yahoo both have "all senders" rules (SPF or DKIM, valid reverse DNS, spam rate below 0.3%, RFC-compliant formatting). Meeting the full bulk list is simply the safer default.
The combined bulk sender requirements checklist
This table merges the three official lists. "Required" means the provider lists it as a requirement; "Recommended" means it appears as guidance; "Not listed" means it does not appear on that provider's requirement page (it may still affect filtering).
| Item | Gmail | Yahoo | Outlook.com |
|---|---|---|---|
| SPF passes | Required (SPF and DKIM) | Required (SPF and DKIM) | Required |
| DKIM passes | Required, key of 1024 bits or more (2048 recommended) | Required | Required |
DMARC record, minimum p=none | Required | Required, DMARC must pass | Required |
| From domain aligned with SPF or DKIM | Required (one is enough, both recommended) | Required (relaxed alignment accepted) | Required (preferably both) |
| Valid forward and reverse DNS (PTR) for sending IPs | Required | Required | Not listed |
| TLS for transmission | Required | Not listed | Not listed |
| One-click unsubscribe (RFC 8058) plus visible link | Required for marketing and subscribed mail | Required (POST method highly recommended, mailto acceptable) | Recommended: functional, clearly visible unsubscribe |
| Honor unsubscribes | Recommended within 48 hours (missing it removes delivery support) | Required within 2 days | Not specified |
| User-reported spam rate | Below 0.10%, never 0.30% or higher | Below 0.3% | No number published |
| RFC 5322 message formatting | Required | Required (RFC 5321 and 5322) | Recommended: no deceptive headers |
| No impersonation of Gmail From headers | Required | Not listed | Recommended: From/Reply-To must reflect the real sending domain and accept replies |
Two practical conclusions: if you meet Gmail's list, you meet nearly everything Yahoo and Microsoft ask; and the only items that cannot be fixed in an afternoon are the spam rate and the list behind it.
How to check each item yourself
You do not need a paid audit. A terminal (or any online DNS lookup tool), one test email to a Gmail address and Google Postmaster Tools cover all of it.
SPF, DKIM and DMARC records
dig +short TXT example.com
# DKIM: replace s1 with the selector your provider gave you
dig +short TXT s1._domainkey.example.com
dig +short CNAME s1._domainkey.example.com
# DMARC: must exist at the _dmarc label
dig +short TXT _dmarc.example.com
"v=DMARC1; p=none; rua=mailto:dmarc@example.com"
Records existing is not the same as passing. Send a test to a Gmail address, open it, choose Show original from the three-dot menu, and confirm SPF, DKIM and DMARC all say PASS. Then check the domains: DKIM's d= domain or the SPF smtp.mailfrom domain must be your From domain or a subdomain of it. If you have not set these up yet, follow our SPF, DKIM and DMARC setup guide; to see who else is sending as your domain, learn how to read DMARC reports.
Reverse DNS (PTR) and TLS
dig +short -x 203.0.113.25
mta25.mail.example.com.
# The hostname must resolve back to the same IP
dig +short A mta25.mail.example.com
203.0.113.25
If you send through Amazon SES, SendGrid, Mailgun or a similar provider on their IPs, PTR and TLS are their responsibility and are normally correct. They become your job when you run your own server or rent a dedicated IP with custom reverse DNS. For TLS, look in the raw message for a Received line containing ESMTPS or a TLS version; Gmail also shows "Standard encryption (TLS)" in the message details.
One-click unsubscribe headers
In the same raw message, look for both headers:
List-Unsubscribe-Post: List-Unsubscribe=One-Click
Three rules from RFC 8058 catch people out: the HTTPS URL must unsubscribe on a POST request without a login, confirmation page or redirect; the URL must identify the recipient and the list (ideally with a hard-to-forge token); and the DKIM signature must cover both headers. Test it by sending the POST yourself with curl -X POST -d "List-Unsubscribe=One-Click" URL and checking that the contact is suppressed. Our guide to one-click unsubscribe covers implementation per provider. The visible footer link is still required in addition to the headers.
Spam rate and compliance status
Verify your domain in Google Postmaster Tools. The Spam rate dashboard shows the daily user-reported rate, and the Compliance status dashboard shows whether Google sees you meeting each sender requirement. Google notes the compliance data is not real-time. Postmaster only shows data once you send enough daily volume to Gmail, so smaller senders should watch complaint counts in their sending provider instead. What to do when the number climbs is covered in how to lower your spam complaint rate.
Message formatting and From address
Check that each message has one From, one Date, a Message-ID, and a correctly encoded subject. Never put an @gmail.com, @yahoo.com or @outlook.com address in the From line when sending through a marketing platform: it fails DMARC and breaks Google's rule against impersonating Gmail From headers. Make the Reply-To an address that receives replies, as Microsoft recommends.
What happens when you fail: real error codes
Enforcement is gradual. Typically you first see temporary deferrals (4xx codes, which your provider retries), then spam-folder placement, then permanent rejections (5xx codes, which bounce). These are taken from the providers' official error pages.
Gmail
| Code | Meaning (Google's wording, shortened) | Fix |
|---|---|---|
421 4.7.27 / 550 5.7.27 | Rate limited / blocked because SPF authentication didn't pass | Correct the SPF record or the Return-Path domain |
421 4.7.30 / 550 5.7.30 | Rate limited / blocked because DKIM authentication didn't pass | Publish the provider's DKIM records for your domain |
421 4.7.32 | The From: header isn't aligned with the authenticated SPF or DKIM domain | Sign DKIM with your From domain or use a custom MAIL FROM subdomain |
550 5.7.26 | Unauthenticated email is not accepted (including due to the domain's DMARC policy) | Make SPF or DKIM pass and align |
451 4.7.23 / 550 5.7.25 | Sending IP has no PTR record, or it doesn't match | Set reverse DNS with a matching forward record |
421 4.7.29 / 550 5.7.29 | Not sent over a TLS connection | Enable STARTTLS on the sending server |
421 4.7.28 | Unusual rate of email from your IP or domain | Slow down and ramp up gradually |
550 5.7.1 | Message is likely unsolicited or the sender has very low reputation | List quality and complaint rate |
Full wording is on Google's Gmail SMTP errors and codes page. Google's FAQ is clear that spam rate, missing DMARC and missing one-click unsubscribe also mean Google will not offer delivery support or mitigation; bulk senders above a 0.3% spam rate become eligible again only after 7 consecutive days below it.
Outlook.com
Microsoft's support article for this error lists the fix: SPF and DKIM must pass, a DMARC record must exist (p=none is enough), and DMARC must pass with at least one of SPF or DKIM aligned to the From domain. Microsoft's FAQ adds that the recipient's Safe Senders list will not override this. For junk-folder problems that are not authentication related, see emails going to junk in Outlook.
Yahoo
Yahoo uses broader codes. A 421 or 451 is a temporary problem (retry later), and codes beginning TS in the text mean temporarily deferred because of complaints, reputation or unusual traffic. A 553 or 554 is permanent, which includes DMARC and DKIM failures. Persistent deferrals can be raised through a Sender Support Request on Yahoo's SMTP error codes page.
Enforcement timeline, 2024 to 2026
Only dates published by the providers themselves are listed here.
- February 2024: Gmail and Yahoo begin enforcing the sender requirements, gradually. Google stops providing mitigation to non-compliant senders.
- June 1, 2024: Google's deadline for senders who already had an unsubscribe link to add one-click unsubscribe to commercial and promotional mail.
- June 2024: Gmail bulk senders with a spam rate above 0.3% become ineligible for mitigation.
- April 2025: Microsoft announces authentication requirements for senders of more than 5,000 messages a day to Outlook.com consumer domains.
- May 5, 2025: Microsoft enforcement starts. The blog post was updated on April 29, 2025 to name
550 5.7.515as the rejection, while noting that non-compliant mail may first go to Junk. - November 2025: Google states that Gmail is "ramping up its enforcement on non-compliant traffic", with temporary and permanent rejections. New domains face an accelerated timetable.
- 2026: As of November 2026, none of the three official pages adds new numeric requirements. Google is moving Postmaster Tools to a new version with a Compliance status dashboard and has said it will retire the old Domain and IP reputation dashboards.
Compliant but still landing in spam?
Meeting the bulk sender requirements gets you through the door; it does not guarantee the inbox. Placement still depends on reputation and engagement. If every item above passes and you are still in spam, work through our pillar guide on why your emails are going to spam, which covers 15 causes in diagnostic order, and our guide to email sender reputation.
The most common gaps we see in real setups:
- DKIM signed by the provider, not you. Everything shows "pass", but DMARC fails because neither SPF nor DKIM uses your domain.
- A forgotten sender. The CRM, the helpdesk or an invoicing tool sends as your domain without DKIM, and DMARC reports reveal it.
- Unsubscribe endpoint that asks for confirmation. The header exists, but the POST lands on a "Are you sure?" page and nothing is suppressed.
- Warming too fast after setup. A new domain jumps straight to full volume and hits
421 4.7.28. Follow an IP and domain warm-up plan.
With a bring-your-own-server setup such as eMailBase, you verify the domain and DKIM at your own provider (for example, verifying a domain in Amazon SES), so the authentication is in your hands. That is more setup than an all-in-one tool, but it means you can see and fix every item on this checklist yourself.
Frequently asked questions
Do the bulk sender requirements apply if I send fewer than 5,000 emails a day?
The bulk tier does not, but Google's and Yahoo's all-sender rules do: SPF or DKIM, valid reverse DNS, a spam rate below 0.3% and RFC-compliant formatting. Because volume can spike unexpectedly and Gmail bulk status is permanent, meeting the full list from day one is the safer choice.
Do transactional emails need one-click unsubscribe?
Google requires one-click unsubscribe for marketing and subscribed messages, not for transactional mail: Google's FAQ names password resets, reservation confirmations and form submission confirmations as examples. Authentication, alignment and spam rate rules still apply to all your mail.
Is DMARC p=none really enough?
For compliance, yes: all three providers accept p=none as the minimum. It does not protect your domain from spoofing, though. Once your reports show every legitimate sender passing, moving to quarantine and then reject is good practice.
Does the 0.3% spam rate apply per campaign?
Google calculates the user-reported spam rate daily across mail to Gmail, not per campaign. A single bad campaign can still push one day over the line, which is why a low baseline near 0.1% gives you room for occasional spikes.
Can I use a shared IP and still meet the requirements?
Yes. The requirements are about your domain's authentication and your recipients' behavior. On a shared IP, your provider handles PTR and TLS, and you handle SPF, DKIM, DMARC alignment, unsubscribe and list quality.
The bulk sender requirements are a short list and almost entirely within your control: authenticate and align your domain, keep reverse DNS and TLS in order, make leaving one click away, and keep complaints far below 0.3%. Check each item with the commands above, watch Postmaster Tools daily, and treat any 4.7.x deferral as an early warning rather than noise.


