Skip to content
Email Deliverability in 2026
KlaviyoAug 20, 20269 min

Email Deliverability in 2026: The Gmail and Yahoo Rules That Decide the Inbox

Email deliverability in 2026 runs on four rulebooks, not one. Google, Yahoo, Microsoft and Apple each publish their own email deliverability requirements, thresholds and tooling for checking them. The four overlap enough that Google’s list gets treated as all four, and it isn’t.

We build and run Klaviyo programs for ecommerce brands, so what follows is the email deliverability analysis we’d give a client before a heavy sending season.

What Email Deliverability Is, and What a Good Rate Looks Like

Email deliverability is whether your message reaches the inbox, not whether a receiving server accepted it. Validity, a vendor selling inbox-placement monitoring, names the trap in its 2025 benchmarks: bounce rates near 1.5% produce a delivery figure around 98.5% (opens in new tab) that says nothing about inbox versus spam.

Validity puts 2024 global inbox placement at 83.5%, with 6.7% in spam and 9.8% missing entirely. In Q4 2024 it dipped to 82.3%, the lowest point Validity reports for the year, while retail sat higher at 87.7%. That’s seed-list panel data from Validity’s own Everest customers with no published sample size, and Validity sells email deliverability monitoring, so use the direction, not the decimals.

No mailbox provider publishes a good email deliverability rate, so there isn’t one. Klaviyo, a platform we partner with, publishes account-health bars (opens in new tab) instead: bounce under 1%, unsubscribes under 0.3%, spam complaints under 0.01%. That’s an ESP’s internal bar, not a provider’s enforcement line, and merging them is how merchants manage the wrong email deliverability number.

The Email Deliverability Rules Are Four Different Rulebooks

Yahoo won’t tell you whether you’re a bulk sender. It defines one as a sender of “a significant volume of mail” (opens in new tab) and won’t specify a volume threshold. Yahoo evaluates at the authenticated or From-header domain level, and says spoofed mail counts toward the volume it reviews. You can’t total your own sends and rule yourself out, so meeting Yahoo’s bulk email deliverability requirements is the only safe posture.

Microsoft’s high-volume email deliverability requirements are authentication only. Its Outlook.com postmaster policies require SPF, DKIM and DMARC above 5,000 emails a day (opens in new tab), effective May 5, 2025, and Microsoft publishes no complaint-rate threshold for Outlook.com. Non-compliant high-volume mail goes to junk first and may be rejected if issues stay unresolved, and Microsoft describes that mail as rejected with 550 5.7.515 (opens in new tab). This is consumer Outlook.com, Hotmail and Live mail, not Microsoft 365 tenants.

Apple sets email deliverability requirements and gives you nothing to measure them against. For iCloud Mail, all bulk requirements must be met or the mail gets rejected (opens in new tab), and Apple requires ARC headers on forwarded messages and asks only for an unsubscribe link, with no List-Unsubscribe requirement. Apple offers no allowlist and no feedback loop, so the escalation path is an email address.

Email deliverability requirements each mailbox provider publishes.

Requirement Gmail Yahoo + AOL Outlook.com iCloud Mail
Bulk threshold Close to 5,000 or more per day to personal Gmail None published More than 5,000 per day from one domain None published
Rules for all senders Yes Yes Yes Bulk only
Spam complaint line Below 0.10%, never 0.30% Below 0.3%, every tier None published None published
TLS required Yes Not listed Not listed Not listed
One-click unsubscribe Bulk only: required, RFC 8058 Bulk only: required, mailto accepted Not listed; unsubscribe must be easy to find and use Not listed; unsubscribe link required
Unsubscribes honored in 48 hours (bulk) 2 days (bulk) No window stated “As soon as possible,” no window stated
Failure action Failure codes or spam foldering Spam folder or rejection Junk folder first, then 550 5.7.515 rejection Rejection
Sender dashboard Postmaster Tools Sender Hub Insights SNDS, IP-based None

Gmail's Two Tiers of Consequence

Google sorts its email deliverability rules into two very different penalties (opens in new tab). Misaligned From headers, missing SPF or DKIM, bad forward and reverse DNS, no TLS and RFC 5322 errors draw temporary or permanent failure codes, or spam foldering. A spam rate above 0.3%, a missing DMARC record, missing one-click unsubscribe and unsubscribes not honored within 48 hours draw something quieter: delivery support or mitigations unavailable. Google calls that 48-hour window a recommendation and grades you against it all the same.

Your email keeps going out. You’ve lost the right to ask Google for help when email deliverability breaks, and bulk senders stay ineligible for mitigation while their spam rate is above 0.3%. Google puts recovery at seven consecutive days below 0.3% (opens in new tab). Google doesn’t accept allowlist requests from email providers, so mitigation is the only lever you have.

The 0.3% figure isn’t the email deliverability number to manage to. Google tells senders to keep spam rates below 0.10% and never reach 0.30% (opens in new tab), and says rates above 0.1% already hurt inbox delivery for bulk senders. Google also said it would ramp up enforcement on non-compliant traffic starting November 2025, including temporary and permanent rejections.

The way Google computes that rate changes what it can tell you about email deliverability. Postmaster Tools (opens in new tab) measures it against messages that actually reached an engaged recipient’s inbox, and counts only DKIM-signed mail. Google notes that heavy auto-filtering to spam can make the rate look low, because fewer messages reached an inbox. A domain in real email deliverability trouble watches its spam rate improve.

Bulk Sender Status Triggers Once and Never Expires

Google defines a bulk sender as one sending close to 5,000 messages or more to personal Gmail accounts in 24 hours. Google permanently classifies senders who meet the criteria at least once as bulk senders, and later changes in sending practice won’t reverse it. Subdomains don’t help, since Google counts every message from the same primary domain.

One Black Friday campaign over 5,000 sends to Gmail addresses is a one-way door, in the quarter Validity measured as its low point. Meet the bulk email deliverability requirements now, at ordinary volume, instead of discovering them on the day your list is largest.

Authentication Is the Floor of Email Deliverability, Not a Boost

RFC 7208 (opens in new tab) defines SPF against the MAIL FROM and HELO identities, not the From address your customer reads, and advises against checking others with it. DKIM, defined in RFC 6376 (opens in new tab), lets a domain claim responsibility for a message, and a valid signature asserts nothing beyond the signed content being unchanged. A spammer can sign their own mail perfectly, so neither record buys you email deliverability on its own.

DMARC ties both to the visible From address, and RFC 9989 (opens in new tab) obsoleted RFC 7489 in May 2026, putting DMARC on the IETF Standards Track for the first time. The pct sampling tag is gone, replaced by a t test-mode tag, and np and psd are new. A record still parked at p=reject with pct=10 is carrying a tag the current spec doesn’t define.

Under RFC 9989, a DMARC pass indicates only that use of the author domain was validated, carrying no value assertion about the message. Google’s bulk requirement is satisfied at p=none. Klaviyo says DMARC can help improve email deliverability (opens in new tab), a fair report of what an ESP observes, but the standard describes a spoofing control, not a reputation booster.

SPF caps DNS-querying terms at 10 per evaluation and returns permerror past that, which RFC 7208 (opens in new tab) defines not as a fail but as a record that couldn’t be interpreted, an error the spec says requires DNS operator intervention. A Shopify Plus domain with includes for the ESP, helpdesk, reviews app, ERP and Google Workspace burns that budget fast.

Shopify rewrites an unauthenticated store’s sender address (opens in new tab) to store+123@shopifyemail.com so mail keeps flowing, which puts order confirmations and password resets under a generic Shopify address. That’s a brand problem before it’s an email deliverability problem.

What Affects Email Deliverability Most Is Sender Reputation

Sender reputation decides email deliverability after that, built from what recipients do with your mail. The email deliverability best practices that move the number are list practices, not record edits.

Google states that it doesn’t track open rates and that low open rates aren’t necessarily an accurate indicator of email deliverability problems. Apple’s Mail Privacy Protection (opens in new tab) downloads remote content in the background regardless of whether the recipient engages, which removes the open rate as an email deliverability signal.

Spam traps damage email deliverability, and ordinary ecommerce practice manufactures them. Spamhaus (opens in new tab) describes dead traps, once-valid addresses providers silently turn back on, and typo-domain traps at addresses like homail.com. A five-year-old customer record you’ve never mailed becomes the first, and an unvalidated pop-up field manufactures the second.

When to Suppress Inactive Subscribers

Klaviyo publishes a workable definition of an unengaged profile: at least five emails received, zero opens and zero clicks in 90 days (opens in new tab), or 30 days for frequent senders. Its sunset guidance (opens in new tab) goes further for never-engaged profiles and ends in suppression, not deletion. Because Apple inflates opens, we build these segments on clicks and site activity and treat opens as a tiebreaker.

Suppress before the quarter you plan to send hardest, not during it, and keep excluding those segments afterward. A properly built Klaviyo setup does it on a schedule, and a lifecycle program that pays rent protects email deliverability by earning more from fewer, better-targeted sends than a dormant-list blast ever has.

How to Test and Check Email Deliverability

A seed test or free spam-checker sends to test mailboxes and scores what arrives, catching a broken DKIM signature, a missing List-Unsubscribe header or a content flag before a campaign ships. It can’t tell you where mail landed for real subscribers, so treat it as a configuration pre-flight, not email deliverability measurement.

The real measurement lives in the providers’ own tools, and Google Postmaster Tools (opens in new tab) is the deepest: spam rate, reputation, authentication, encryption, delivery errors and a compliance dashboard open to all senders. Its data is a rolling multi-day average in UTC, covers primary domains only, and can go blank on low-volume days, so give email deliverability changes about seven days.

Google has postponed retirement of the legacy Postmaster Tools interface (opens in new tab) with no new date, and Yahoo’s Insights (opens in new tab) dashboard, launched October 27, 2025, reports spam complaint rate against inbox-delivered mail only.

Microsoft’s tooling is IP-based, so it does least for a brand on shared ESP infrastructure. Trap hit counts left Microsoft’s SNDS Data Report on July 22, 2026 (opens in new tab), removing an email deliverability signal neither Google nor Yahoo offers. Yahoo’s Complaint Feedback Loop (opens in new tab) is DKIM-domain based, and Yahoo no longer offers it for IP or CIDR ranges.

How to Improve Email Deliverability Before Your Heaviest Season

Authenticate first, because that’s the tier that bounces mail, then fix the behavioral tier, because that’s the one that decides whether anyone helps you when email deliverability breaks.

  • Publish SPF and DKIM, align your From domain with at least one, and publish DMARC even at p=none.
  • Verify forward and reverse DNS, TLS and DKIM key length with your ESP instead of assuming they're handled.
  • Ship List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send, keep a visible unsubscribe link in the body, and confirm your firewall isn't blocking the POST.
  • Separate marketing from transactional streams so a bad campaign can't take order confirmations down with it.
  • Suppress unengaged profiles before your heaviest sending quarter, then keep excluding them.

An email deliverability problem is rarely one a DNS record fixes. It’s a list you keep mailing as if it were the 2021 list, graded by four providers on four scales. If you’d rather know where you stand before your heaviest sending season than after it, our Klaviyo email marketing team will look at your sending, or start with the free growth audit on our email and SMS services page.

E.J. Ulery

About the author

EJ Ulery

Co-Founder & CTO

EJ Ulery on LinkedIn (opens in new tab)

Not sure where the gap is? That's exactly what the Digital Marketing Growth Audit is for.

A free, no-obligation look at where your site can win more traffic and conversions, with a clear digital marketing roadmap to get there. Just a straight read on where your digital presence stands and where it's headed.