What Is Email Deliverability (and Why Do Your Emails Land in Spam?)

Last updated 2026-09-28

Stack of stamped envelopes on a wooden desk with a blurred laptop inbox behind.

The short answer: email deliverability is the share of your sent emails that actually reach a recipient’s inbox rather than bouncing or being filtered into spam. If your emails are landing in spam, it’s not random and it’s not personal — Gmail, Yahoo, Outlook, and every other provider run the same kind of multi-layer filtering system, and your mail is failing one or more of its gates. The fix is structural: authenticate your domain, keep your list clean, and send mail people actually want.

This matters more than most small businesses realize. Email marketing software can cost under $20 a month — but a 20% spam-placement rate is the equivalent of throwing a fifth of that investment away before anyone even sees your subject line.

The mechanism: how an email actually gets delivered

To understand deliverability, you need the mental model of what happens between “send” and “inbox.” It runs in four stages:

  1. Acceptance. Your email arrives at the receiving mail server (say, Gmail). Before anything else, the server runs cheap, automatic checks: does the sending IP have valid reverse DNS? Is the connection encrypted? Is the sender on a blocklist? Fail these and the mail is rejected outright — it bounces, the recipient never sees it.

  2. Authentication. The receiver checks your SPF, DKIM, and DMARC records. These are DNS entries that prove (a) the server is authorized to send for your domain, (b) the message wasn’t tampered with, and (c) the visible “From” domain matches the authenticated domain. Fail authentication and modern Gmail/Yahoo/Outlook will route the mail to spam or reject it — this is the one layer that is now a hard rule, not a judgment call.

  3. Reputation scoring. Now comes the judgment call. The provider maintains a sender reputation for your domain (and, separately, for the IP address you send from). That reputation is built from observable behavior: what share of your mail gets marked as spam, how many recipients open and engage, how many addresses hard-bounce, and how often you mail strangers. Good reputation → inbox. Bad reputation → spam.

  4. Content and individual filtering. Last, the message itself is scanned — for phishing links, deceptive formatting, and known spam patterns — and adjusted for the individual recipient (has this person opened your mail before? did they search for you recently?). This is where “spammy” subject lines and link-heavy layouts do real damage, but they’re the last layer, not the first.

The key insight: these layers are sequential, and most deliverability failures happen in the first three — the ones almost nobody tweaks copy to fix. A missing DMARC record or a list full of dead addresses will bury you regardless of how tasteful your subject line is. That’s why deliverability advice that starts with “avoid ALL CAPS” is treating the symptom while the disease sits untouched.

Why spam placement is a system, not a verdict on your content

The reputation layer deserves a closer look, because it’s where most small-business deliverability problems actually live. Think of it as a credit score for your domain:

  • Complaints are the heaviest negative signal. When a recipient clicks “Report spam,” that counts far more than an ignored email. Google’s published line: keep your spam-complaint rate under 0.3%, and treat 0.1% as the real target (researched September 28, 2026). Three complaints per thousand delivered emails is the danger zone.
  • Engagement is the heaviest positive signal. Opens, replies, and clicks tell the provider “this mail was wanted.” A list of 500 people who open is worth more, reputation-wise, than a list of 5,000 who ignore you.
  • Bounces poison everything. A hard bounce (address doesn’t exist) signals you don’t know your own list. Providers watch bounce rates closely; consistently mailing dead addresses looks exactly like what spammers do, because it is what spammers do.
  • Reputation is sticky and shared. Reputation builds over months of consistent sending from the same domain and decays fast when you do something abrupt — like blasting 10,000 cold emails after months of silence. If you use a shared sending IP (the default on most email marketing platforms), your mail inherits some of your IP-neighbors’ behavior too.

This is why “my emails used to land fine, then suddenly started going to spam” has a nearly universal cause: something changed in one of the reputation inputs — a bought or scraped list, a burst of volume, a spike in complaints — and the score caught up with it.

The authentication layer: the part that’s now non-negotiable

Since February 2024, Google and Yahoo have enforced hard sender requirements for bulk senders — domains sending roughly 5,000+ messages per day to their users. Microsoft applied the same bar to Outlook.com/Hotmail/Live addresses from May 2025. The requirements (researched September 28, 2026):

Requirement What it means
SPF, DKIM, and DMARC all pass Domain authenticated in DNS; DMARC p=none policy is the minimum
Domain alignment The visible From domain must match the SPF or DKIM domain
One-click unsubscribe RFC 8058 List-Unsubscribe header, honored within 2 days
Complaint rate under 0.3% Hard requirement; 0.1% is the stated target
Valid forward/reverse DNS, TLS Basic server plumbing

Two details most guides miss: the 5,000/day threshold is sticky — once your domain has crossed it, the rules apply permanently even if your volume drops. And non-compliant mail now gets rejected outright (SMTP 5xx errors), not just sent to spam.

If you’re a small business sending a few hundred emails a week, you may never trigger the formal “bulk sender” definition — but set these up anyway. Most email marketing platforms (MailerLite, Brevo, Kit, and the rest) walk you through adding the three DNS records during onboarding; it’s a one-time, 20-minute setup, and it’s the single highest-leverage deliverability task that exists.

The diagnostic: finding out which layer is broken

Deliverability problems are diagnosable, not mysterious. Work through this in order:

  1. Check authentication first. Send yourself a test email to a Gmail address and view the original headers (“Show original” in Gmail). Look for SPF, DKIM, and DMARC lines — all should say PASS. If any fail, fix your DNS records before doing anything else.
  2. Check your complaint rate. Gmail’s Postmaster Tools (free) shows your domain’s spam-complaint rate, IP and domain reputation, and authentication pass rates. If you don’t have it set up, that’s step one — you’re flying blind without it.
  3. Check list hygiene. When did you last remove addresses that haven’t opened anything in 6–12 months? Are you still mailing people who haven’t engaged since signup? Chronic non-openers drag your engagement ratios down and cost you on platforms that charge by contact count (see our cost guide for why pruning dead contacts saves money twice over).
  4. Check for abrupt changes. Did spam placement start after a volume spike, a new list import, a domain change, or a switch of sending platform? The trigger is usually in the week the problem started.

The bottom line

Emails land in spam because a filtering system with four layers — acceptance, authentication, reputation scoring, and content filtering — scored your mail poorly. For small businesses, the fix is almost always the same sequence: authenticate your domain properly (SPF/DKIM/DMARC), email only people who opted in, prune chronic non-openers, and send consistently instead of in bursts. Content and subject-line tweaks are the finishing touches, not the foundation. Deliverability is infrastructure — build it once, monitor it in Postmaster Tools, and your email marketing keeps the reach you paid for.

Technical requirements referenced above were researched on September 28, 2026 and reflect Google’s, Yahoo’s, and Microsoft’s published bulk-sender rules at that date. Providers tighten enforcement periodically, so re-verify the current rules if you’re reading this much later.

Frequently asked questions

What is a good email deliverability rate?

For a small business with a permission-based list, aim for 98–99% of emails accepted by receiving servers, with 90%+ landing in the primary inbox rather than spam. If more than ≈5% of your mail is going to spam, something structural is wrong — usually missing authentication, a stale list, or a damaged sender reputation.

Why are my emails going to spam if nobody reported me?

Spam placement is rarely about a single complaint. Gmail and other providers score every sender on a basket of signals — authentication setup, engagement history, complaint rate, list hygiene, and sending patterns. Fail authentication and you get filtered regardless of content; neglect any of the others and you slide toward spam gradually, without a single triggering event.

What do SPF, DKIM, and DMARC actually do?

SPF is a DNS record listing which servers may send mail from your domain — it answers 'is this server authorized?' DKIM cryptographically signs each message so the receiver can verify it wasn't altered in transit — it answers 'is this message genuine?' DMARC ties them together: it requires the From domain to align with SPF or DKIM and tells receivers what to do when authentication fails. Gmail, Yahoo, and Outlook require all three for bulk senders (roughly 5,000+ messages/day to their users, enforced since Feb 2024, with Microsoft joining in May 2025).

Can I fix deliverability by changing my email's subject line or content?

Rarely. Content filters are only one layer of a multi-layer decision, and they're a minor one for legitimate senders. If your mail is landing in spam, fix the layers in order: (1) authentication — SPF, DKIM, DMARC records; (2) list quality — only email people who asked; (3) engagement and complaints — remove chronic non-openers; (4) sending pattern — consistent volume from a consistent domain. Content tweaks only matter after the first three are clean.

Does switching email marketing platforms improve deliverability?

Only if the real problem is the platform's sending infrastructure, which is uncommon for established providers — most give you their shared pool's average reputation and handle authentication setup for you. The dominant variables are your own: whether your domain is authenticated properly, how clean your list is, and how subscribers react to your mail. Switching platforms without fixing those carries your problem to a new provider.