Email deliverability is whether a message that a mailbox provider accepts lands in the recipient’s inbox or in spam. Delivery only means the receiving server said yes. Deliverability depends on three things you control: authentication (SPF, DKIM and DMARC), sender reputation, driven mostly by spam complaints, and a clean list.
We’re EmailAnalytics, and we don’t sell a deliverability tool, an email service provider or a warmup network. We measure how fast teams reply to email. That means nothing in this guide is steering you toward a product, and every requirement below is quoted from the mailbox provider that publishes it.
Ready for the part that trips people up? Most of the numbers you’ll read about deliverability were never published by Gmail, Yahoo, Outlook or Apple. I’ll show you which ones were, and which ones the email gods never said.
What Is the Difference Between Email Delivery and Email Deliverability?
Delivery is a server event, and deliverability is a placement outcome. A message is delivered when the receiving server accepts it during the SMTP conversation. It can still be filtered to spam a second later.
The SMTP reply codes tell you which stage you’re at. RFC 5321, the standard that defines SMTP, groups them by first digit:
| What happened | SMTP code family | What it means for you |
|---|---|---|
| Accepted (delivered) | RFC 5321 treats a 2xx reply as success | The server took the message; inbox or spam is decided afterwards |
| Deferred | RFC 5321 treats a 4xx reply as a temporary failure | Your server should retry later; repeated deferrals signal a reputation or rate problem |
| Bounced | RFC 5321 treats a 5xx reply as a permanent failure | Don’t resend to that address without fixing the cause |
| Inbox or spam | No SMTP code at all | The provider decides placement privately, which is why deliverability is hard to measure |
That last row matters most. No mailbox provider tells you where an accepted message landed, so every “inbox placement rate” you see is an estimate built from test accounts.
What Gmail, Yahoo, Outlook and Apple Require From Senders
Four mailbox providers publish sender requirements, and they overlap less than most guides suggest. I read each page on September 30, 2026. Here’s what each one says in its own words, and where each one is silent:
| Requirement | Google (Gmail) | Yahoo | Microsoft (Outlook.com) | Apple (iCloud Mail) |
|---|---|---|---|---|
| Who counts as a bulk sender | Google says more than 5,000 messages a day to personal Gmail accounts | Yahoo publishes no volume threshold | Microsoft says 5,000 or more messages to its consumer email services | Apple publishes no volume threshold |
| Authentication | Google requires SPF or DKIM for everyone, and SPF, DKIM and DMARC for bulk senders | Yahoo requires SPF or DKIM, and both plus DMARC for bulk senders | Microsoft requires both SPF and DKIM to pass, plus a DMARC record, for high-volume senders | Apple says to use SPF and DKIM and that the sending domain must publish DMARC |
| Spam complaint rate | Google says stay below 0.3% and aim for below 0.10% | Yahoo says keep your spam rate below 0.3% | Microsoft publishes no complaint-rate number | Apple publishes no complaint-rate number |
| One-click unsubscribe | Google requires RFC 8058 one-click unsubscribe for bulk marketing mail | Yahoo requires a working list-unsubscribe header with one-click support | Microsoft publishes no one-click requirement | Apple says to offer an unsubscribe link and honor requests quickly |
| Bounce-rate threshold | Google publishes none | Yahoo publishes none | Microsoft publishes none | Apple publishes none |
Sources: Google’s email sender guidelines, Yahoo’s sender best practices, Microsoft’s 550 5.7.515 help page and Apple’s postmaster information for iCloud Mail.
Notice the bottom row. Every provider publishes rules about authentication and complaints, and not one publishes a bounce-rate limit.
The Deliverability Numbers Google’s AI Overview Gets Wrong
Search “email deliverability” and Google’s AI Overview tells you to aim for 95% inbox placement, a hard bounce rate below 2% and complaints under 0.1%. Only one of those three numbers comes from a mailbox provider.
The short version: Google publishes a spam complaint ceiling of 0.3% with a target below 0.10%. No mailbox provider publishes a bounce-rate threshold. No mailbox provider publishes an inbox placement benchmark, because none of them report placement to senders at all.
| Number people repeat | Where it comes from | What the primary source says |
|---|---|---|
| The AI Overview says keep complaints under 0.1% | Google’s own sender guidelines | Google says keep spam rates below 0.3% and aim for below 0.10%, so 0.1% is Google’s target and 0.3% is its hard line |
| The AI Overview says keep hard bounces below 2% | A vendor rule of thumb, cited in the AI Overview to an email platform’s blog | Google, Yahoo, Microsoft, Apple and M3AAWG publish no bounce-rate threshold at all |
| The AI Overview says aim for 95% inbox placement | Vendor targets with no stated method | Validity measured an 83.5% global inbox placement rate from seed-account tests in 2024 |
| Vendor guides say one in six emails miss the inbox | Validity’s 2025 benchmark report | Validity’s figure is real, and it comes from its customers’ test addresses, which makes it a sample of senders who test |
Bounces still matter, and Google tells you what to do about them in behavioral terms. Its guidelines say that if messages start bouncing or being deferred, you should reduce your sending volume until the error rate comes down.
The M3AAWG Senders Best Common Practices take the same approach. They tell you to remove an address that bounces consecutively at least two times over two weeks or more, and they give no percentage.
Gmail’s Sender Rules Don’t Cover Google Workspace Recipients
Google’s bulk sender rules apply to mail sent to personal Gmail accounts, which matters a lot for B2B senders. Google’s sender guidelines FAQ says it directly:
“The Email sender guidelines don’t apply to messages sent to Google Workspace accounts. Sender requirements and Google enforcement apply only when sending email to personal Gmail accounts.”
Two things follow from that. Mail to a company on Google Workspace doesn’t count toward Google’s 5,000-a-day bulk threshold. And Google says bulk sender status never expires once you cross it.
None of the five vendor guides ranking at the top for “email deliverability” mention this exclusion. The receiving company’s own admin settings and filters still apply, so authenticate everything anyway.
How to Set Up SPF, DKIM and DMARC
Authentication proves that a message claiming to come from your domain did come from you. Every provider in the table above requires some combination of these three records:
- SPF is a DNS TXT record listing the servers allowed to send for your domain. RFC 7208 caps SPF evaluation at 10 DNS lookups, and exceeding it makes SPF fail.
- DKIM adds a cryptographic signature to each message, verified against a public key in your DNS. Google requires keys of at least 1,024 bits and recommends 2,048.
- DMARC tells receivers what to do when SPF and DKIM fail, and requires one of them to align with your From domain. Google, Yahoo and Microsoft all accept a starting policy of p=none.
A DMARC record at p=none looks like this, published at the _dmarc subdomain of your domain:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
Start at p=none and read the aggregate reports for a few weeks. Once every legitimate sender passes, move to p=quarantine and then p=reject.
The most common failure I see is a forgotten third-party sender. Your CRM, help desk and billing tool all send as your domain, and each one needs to be in SPF or signing with DKIM.
What One-Click Unsubscribe Requires
One-click unsubscribe is two email headers, and an unsubscribe link in the footer doesn’t satisfy it. RFC 8058 says the List-Unsubscribe-Post header must contain the single value List-Unsubscribe=One-Click.
The same standard says the List-Unsubscribe header must contain one HTTPS address, and a valid DKIM signature must cover both headers. Most email service providers add these for you, so check the raw headers of a test message to confirm.
How to Measure Email Deliverability
You can’t see inbox placement directly. You measure it from what providers report, what your sending logs show and what test accounts see, and each has a blind spot.
| Source | What it tells you | Its blind spot |
|---|---|---|
| Google Postmaster Tools | Google’s v2 interface, launched in 2024, adds a Compliance dashboard showing whether you meet its sender guidelines, plus your spam rate | Google says its spam rate covers DKIM-authenticated mail to engaged recipients’ inboxes, so mail already filtered to spam can make it look low |
| Microsoft SNDS | Microsoft’s Smart Network Data Services reports data on your sending IPs at Outlook.com | It now lives at substrate.office.com, requires a Microsoft account sign-in, and covers IPs you register |
| Your SMTP logs | Your server logs record every 2xx, 4xx and 5xx reply per RFC 5321, so deferrals and bounces are visible by provider | An accepted message can still land in spam |
| Seed tests | Vendors like Validity send to test accounts and report where each copy landed | Seed accounts don’t behave like real readers, so they miss the engagement signals real recipients send |
| Open rates | Pixel opens in your email platform are an estimate of engagement at best | Google says it doesn’t track open rates and can’t verify third-party ones, and Apple Mail Privacy Protection preloads images |
Google is blunt about that last row. Its sender guidelines say:
“Google doesn’t track open rates. Google can’t verify the accuracy of open rates reported by third parties. Low open rates aren’t necessarily an accurate indicator of deliverability or spam classification issues.”
Google has also announced that the Domain and IP Reputation dashboards won’t move to Postmaster Tools v2. Its deprecation notice says those two dashboards will be retired, and that it has postponed switching off the legacy interface.
How to Fix Email Deliverability Problems
Fix deliverability by matching the symptom to its cause, rather than changing everything at once. Here’s the triage order I use:
| Symptom | Likely cause | First fix |
|---|---|---|
| Outlook.com bounces with 550 5.7.515 | Microsoft says this means a high-volume sender failed its SPF, DKIM or DMARC requirements | Publish SPF, DKIM and a DMARC record, then confirm both SPF and DKIM pass |
| Gmail rejects or defers bulk mail | Google says that from November 2025 non-compliant mail faces temporary and permanent rejections | Open the Compliance dashboard in Postmaster Tools and fix whatever it flags |
| Repeated 4xx deferrals at one provider | Google treats this as a rate or reputation signal and says to reduce sending volume | Slow down, then ramp back up gradually |
| Hard bounces on a list segment | Invalid or abandoned addresses, which M3AAWG says to remove after repeated bounces | Suppress the addresses and stop importing unverified lists |
| Accepted, then filtered to spam | Complaints, missing one-click unsubscribe or weak engagement, per Google’s and Yahoo’s guidelines | Check your Postmaster spam rate and unsubscribe headers first |
| Rejections citing a blocklist | Your IP or domain is listed by a blocklist operator | Look it up and follow that operator’s own delisting process |
For the blocklist row, our guide to checking whether you’re on an email blacklist and getting delisted walks through each major operator’s process. For mail landing in spam, why emails go to spam, according to Gmail, Yahoo and Outlook covers each provider’s filters.
New domain with no history? Read how email warmup works and what Google says about it before you buy a warmup service.
What Is a Good Email Deliverability Rate?
No mailbox provider defines a good deliverability rate, so treat any single number as a vendor opinion. Validity reported an 83.5% global inbox placement rate for 2024 in its 2025 benchmark report, measured with seed accounts across hundreds of mailbox providers.
A better target is compliance you can check. Keep your Google spam rate below 0.10%, pass SPF, DKIM and DMARC, and watch your bounces and deferrals by provider week over week.
What the Law Requires for Commercial Email in the US
Deliverability rules come from mailbox providers, and legal rules come from governments. In the US, the FTC’s CAN-SPAM compliance guide says your message must include your valid physical postal address and a clear way to opt out.
The FTC’s penalty is up to $53,088 per violating email. Other countries set their own rules, so check the law where your recipients live.
Where Email Analytics Fits Into Deliverability
Deliverability tools tell you whether your mail arrived, and we measure what happens after it does. EmailAnalytics connects to Gmail and Outlook and reports how fast your team replies, which is the part of the conversation you fully control.
If your outbound mail is landing fine and replies still lag, the bottleneck is inside your team. That’s the problem we built our product to show you.
Start Here: Five Steps to Better Email Deliverability
- List every service that sends as your domain. Include your CRM, help desk, billing and marketing tools, then confirm each one passes SPF or DKIM.
- Publish DMARC at p=none. Read the aggregate reports for a few weeks before tightening the policy.
- Set up Google Postmaster Tools and Microsoft SNDS. Check the Compliance dashboard and your spam rate weekly.
- Confirm one-click unsubscribe in the raw headers. Look for List-Unsubscribe-Post alongside a List-Unsubscribe HTTPS address.
- Suppress repeat bounces. Remove addresses that bounce repeatedly, and slow down whenever a provider starts deferring.
Frequently Asked Questions About Email Deliverability
What is email deliverability?
Email deliverability is whether an accepted email reaches the recipient’s inbox rather than the spam folder. It depends on authentication, sender reputation and list quality.
What is the difference between email delivery and deliverability?
Delivery means the receiving server accepted your message with a 2xx SMTP reply. Deliverability means the accepted message landed in the inbox. A delivered email can still go to spam.
What is a good email deliverability rate?
No mailbox provider publishes one. Validity measured 83.5% global inbox placement in 2024 using seed accounts, and vendor targets of 95% or more have no stated method.
Is a 2% bounce rate a Gmail rule?
No, Google publishes no bounce-rate threshold, and neither do Yahoo, Microsoft or Apple. Google’s guidance is to reduce sending volume when bounces or deferrals start rising.
Do Gmail’s bulk sender rules apply to Google Workspace addresses?
No. Google’s FAQ says its sender guidelines apply only to mail sent to personal Gmail accounts, and don’t apply to messages sent to Google Workspace accounts.
How do you fix email deliverability?
Match the symptom to the cause. Authentication failures need SPF, DKIM and DMARC fixes, deferrals need lower volume, and spam placement needs lower complaints and working one-click unsubscribe.
What is the 3 email rule?
It isn’t a deliverability rule, and no mailbox provider or standards body defines it. The phrase usually refers to sending no more than three follow-up emails before moving on.
Jayson is a long-time columnist for Forbes, Entrepreneur, BusinessInsider, Inc.com, and various other major media publications, where he has authored over 1,000 articles since 2012, covering technology, marketing, and entrepreneurship. He keynoted the 2013 MarketingProfs University, and won the “Entrepreneur Blogger of the Year” award in 2015 from the Oxford Center for Entrepreneurs. In 2010, he founded a marketing agency that appeared on the Inc. 5000 before selling it in January of 2019, and he is now the CEO of EmailAnalytics and OutreachBloom.
