Gmail, Yahoo and Outlook.com bulk sender requirements are the minimum rules these mailbox providers apply to anyone who sends email in volume. They ask for three things: authenticate your mail with SPF, DKIM and DMARC, make unsubscribing easy with a one-click header, and keep spam complaints low. This guide puts the three sets of rules side by side and gives you a checklist you can work through in about a month.
Rules change. Mailbox providers update these requirements and how strictly they enforce them. Use this guide as a working checklist and confirm the details in the official documents linked at the end before you rely on a specific number.
The short version
- Authenticate everything. SPF and DKIM on your sending domain, plus a DMARC record. At least one of SPF or DKIM must align with the visible From domain.
- Make unsubscribing one click. Add List-Unsubscribe and List-Unsubscribe-Post headers to marketing mail and process requests within two days.
- Keep complaints under 0.10%. Send only to people who asked for your mail and remove anyone who stops engaging.
- Get the basics right. Matching forward and reverse DNS, TLS in transit and a correctly formatted message.
- Monitor. Use Google Postmaster Tools and check bounce and complaint rates every week.
Who counts as a bulk sender?
Google treats a sender as a bulk sender when it sends close to 5,000 or more messages in a day to personal Gmail addresses. The count covers every message from your primary domain, including all subdomains and all sending systems, and the classification does not expire once you have crossed the line. Yahoo and Microsoft use similar volume thresholds for their consumer mail services.
Two things are easy to miss. First, the count is per provider, so a large list with a strong Gmail share can cross the threshold sooner than you expect. Second, the basic authentication and spam-rate expectations apply to all senders, not only to bulk senders. If you are growing, build to the bulk standard now.
Requirements side by side
| Requirement | Gmail | Yahoo | Outlook.com |
|---|---|---|---|
| SPF or DKIM | Required for all senders | Required | SPF and DKIM required for high-volume senders |
| SPF and DKIM both | Required for bulk senders | Required for bulk senders | Required for high-volume senders |
| DMARC record | Required for bulk senders, p=none is enough | Required for bulk senders, p=none is enough | Required for high-volume senders, p=none is enough |
| Alignment with From domain | SPF or DKIM must align | SPF or DKIM must align | SPF or DKIM must align |
| One-click unsubscribe | Required for marketing mail from bulk senders | Required for marketing mail from bulk senders | Expected as good practice |
| Spam rate | Below 0.10%, never 0.30% or more | Below 0.30% | Monitored through the sender programmes |
| Forward and reverse DNS | Valid PTR record for sending IPs | Valid PTR record for sending IPs | Valid PTR record for sending IPs |
| TLS | Required for transmission | Expected | Expected |
Read the table as a floor. Meeting these rules does not guarantee the inbox. They are the entry ticket. Placement still depends on engagement, content and reputation.
1. Authenticate: SPF, DKIM and DMARC
Authentication proves that a message really comes from your domain. For bulk senders all three layers are expected, and the From domain must align with the domain that passed SPF or DKIM. If you have not set these up yet, follow the step-by-step guide to authenticate a sending domain, then come back to this checklist.
| Check | What a pass looks like | Common failure |
|---|---|---|
| SPF | One record at the domain root ending in ~all or -all, under 10 DNS lookups | Two SPF records, or a sending service missing from the record |
| DKIM | A selector record that validates, signing with a key of 2048 bits where possible | Signing with the provider domain instead of your own |
| DMARC | A record at _dmarc with a policy and a reporting address | No record at all, or a typo in the tag names |
| Alignment | The DKIM d= domain or the Return-Path domain matches the From domain | SPF passes for the provider domain, not yours |
How to verify in one minute
Send a test message to a Gmail address, open the message, choose Show original and look at the summary at the top. You want to see PASS next to SPF, DKIM and DMARC. Repeat the test for an Outlook.com and a Yahoo address, because each provider evaluates alignment on its own.
Authentication-Results: mx.google.com;
dkim=pass header.i=@mail.example.com;
spf=pass smtp.mailfrom=bounce.example.com;
dmarc=pass (p=NONE) header.from=example.com
2. Make unsubscribing easy
For marketing and other subscribed mail, bulk senders must support one-click unsubscribe. That means two message headers, List-Unsubscribe and List-Unsubscribe-Post, plus a visible unsubscribe link in the body. Requests must be honoured within two days, and the safest policy is to apply them immediately. The full header format, an endpoint example and the common mistakes are in the guide to one-click unsubscribe and the List-Unsubscribe header.
- Marketing and subscribed mail: one-click header required.
- Transactional mail: password resets, receipts and security alerts are not required to carry it.
- Mixed messages: if a message is mostly promotional, treat it as marketing.
3. Keep spam complaints low
The spam rate is the share of messages that recipients mark as spam, as reported by the mailbox provider. Google measures it in Postmaster Tools for messages delivered to the inbox. The numbers are small, so a few complaints matter:
| Messages delivered to the inbox | Complaints at 0.10% | Complaints at 0.30% |
|---|---|---|
| 10,000 | 10 | 30 |
| 100,000 | 100 | 300 |
| 1,000,000 | 1,000 | 3,000 |
A spam rate that reaches 0.30 percent is the point at which Google says it can no longer qualify a sender for mitigation, so treat 0.10 percent as the line to defend.
What lowers complaints
- Consent: send only to people who signed up, preferably with double opt-in.
- Expectation: say at sign-up what you will send and how often, then do exactly that.
- A visible, working unsubscribe: people mark mail as spam when they cannot find the unsubscribe link.
- Sunset policy: stop mailing contacts who have not opened or clicked for several months.
- Segmentation: send relevant mail to the segment that wants it, not to the whole list.
- Warm-up: raise volume gradually with a warm-up plan.
4. The technical basics
| Item | What to check | How |
|---|---|---|
| Forward and reverse DNS | The sending IP has a PTR record, and the host name it returns resolves back to the same IP | dig -x 203.0.113.10 +short, then dig host.example.com +short |
| TLS | Messages are sent over an encrypted connection where the receiver offers it | Check the delivery log for the TLS version |
| Message format | Valid headers, a Message-ID, a real From address, no duplicate From or Subject headers | View the raw source of a test message |
| From address | Never use a gmail.com or yahoo.com address as the From of mail you send yourself | Use an address at a domain you own |
| Forwarding and lists | Forwarders and mailing lists should add ARC headers so authentication survives | Only applies if you run forwarding or list software |
5. Monitor and respond
- Add Google Postmaster Tools. Verify your sending domain, then review the spam rate, authentication and compliance dashboards every week.
- Watch the numbers inside MigoSMTP. Track hard bounce rate, complaint rate and deferrals by recipient domain in your delivery reports.
- Join the provider programmes. Register for Microsoft sender support and Yahoo sender tools so you receive complaint data and can ask for help.
- Set alerts. Alert when complaints pass 0.05 percent or when hard bounces pass 2 percent, so you can react before a provider does.
- Act on the first sign. Pause the affected stream, find the cause and resume gradually. The bounce code guide explains what the error text means.
Error messages you may see
| Message | Provider | Meaning and fix |
|---|---|---|
550 5.7.26 unauthenticated | Gmail | SPF or DKIM is missing or not aligned. Fix authentication and resend. |
550 5.7.515 does not meet the required authentication level | Outlook.com | The domain needs passing, aligned SPF, DKIM and DMARC. |
421 4.7.0 temporarily deferred | Yahoo | Volume or complaints are high. Slow down and clean the list. |
421 4.7.28 rate limited | Gmail | Unusual traffic. Slow down, check authentication and the spam rate. |
550 5.7.1 policy rejection | All | A rule blocked the message. Read the text for SPF, DMARC or blocklist hints. |
A 30-day plan to comply
| Week | Focus | Done when |
|---|---|---|
| 1 | Inventory every system that sends as your domain, then publish SPF, DKIM and DMARC p=none | Test messages show PASS for all three at Gmail, Yahoo and Outlook.com |
| 2 | Fix alignment: custom Return-Path and DKIM domain on your own domain | DMARC shows PASS because of alignment, not by accident |
| 3 | Add one-click unsubscribe and test it | The unsubscribe control shows in Gmail and a test request removes the address |
| 4 | Add Postmaster Tools, set alerts, review complaint sources and tidy the list | Spam rate under 0.10% and hard bounces under 2% |
| After | Read DMARC reports for two to four weeks, then move to p=quarantine and p=reject | Policy enforced with no legitimate mail failing |
Not sure whether you comply? Send us a test message header and we will tell you what passes and what to fix.
Further reading and sources
- Google: Email sender guidelines
- Google: Email sender guidelines FAQ
- Yahoo: Sender best practices
- Microsoft: Outlook.com postmaster and sender support
- RFC 8058: Signaling One-Click Functionality for List Email Headers
- RFC 7489: DMARC
- Related guides: Authenticate a sending domain, One-click unsubscribe and Email warm-up guide.
Frequently asked questions
Who counts as a bulk sender for Gmail and Yahoo?
Google defines a bulk sender as a sender that sends close to 5,000 or more messages in one day to personal Gmail accounts, counted across your whole primary domain. Once a domain has been classified as a bulk sender it stays classified. Yahoo applies similar rules to anyone sending in volume to its users. Every sender, large or small, still has to meet the basic authentication rules.
Do these rules apply if I send fewer than 5,000 emails a day?
The strictest rules, such as DMARC and one-click unsubscribe, are written for bulk senders. The basics still apply to everyone: authenticate with SPF or DKIM, have valid DNS records, use TLS and keep complaints low. In practice it is easier to meet the full list from the start than to notice it when you grow.
What spam rate do Gmail and Yahoo allow?
Google asks senders to keep the user-reported spam rate below 0.10 percent and to never reach 0.30 percent, measured in Google Postmaster Tools. Yahoo asks senders to stay below 0.30 percent. Treat 0.10 percent as the working target for all providers: one complaint in every 1,000 messages is already a warning.
Is DMARC p=none enough to comply?
Yes for the current minimum. Gmail, Yahoo and Outlook.com accept a valid DMARC record with p=none for bulk senders as long as SPF or DKIM aligns with your From domain. p=none only monitors, though. Move to quarantine and then reject after reviewing your reports so that the policy actually protects your domain.
What does error 550 5.7.515 from Outlook.com mean?
It means the sending domain does not meet the authentication level Microsoft now requires for high-volume senders: SPF, DKIM and DMARC that pass and align. Check that all three are published and passing for the domain in the From header, then resend.
What does error 550 5.7.26 from Gmail mean?
Gmail returns 5.7.26 when a message is unauthenticated or fails the sender authentication requirements. Check that SPF and DKIM pass and align with your From domain and that a DMARC record exists.
Do transactional emails need an unsubscribe link?
Google requires one-click unsubscribe for marketing and subscribed messages, not for purely transactional mail such as password resets and receipts. If a message is mostly promotional it counts as marketing even when it is triggered by an action, so do not hide promotions inside transactional templates.
How do I check whether my domain complies?
Open Google Postmaster Tools for your sending domain and review the compliance status and the spam rate. Send a test message to a Gmail address, open Show original and confirm SPF, DKIM and DMARC all say PASS. Check the same for an Outlook.com and a Yahoo address.
Can I send from a free address such as gmail.com through my own server?
No. Messages that claim a gmail.com From address but are not sent by Google fail the domain policy and are rejected or sent to spam. Always send from a domain you own and have authenticated.
What happens if I do not comply?
The result ranges from temporary deferrals and spam-folder placement to permanent rejections, and mailbox providers have said they are moving toward stricter enforcement over time. Failing messages can also hurt your reputation, which makes later sends harder to deliver.