Email deliverability for cold outbound: the whole picture

Email deliverability is the difference between "we sent 1,000 emails" and "1,000 people had a chance to read them." Most cold senders only see the first number. Their tool says delivered, the replies don't come, and nobody can say whether the offer is weak or the mail never arrived. This post is the whole picture of email deliverability for cold outbound, with a short section per lever and links to the deeper guides.

Delivered is not inboxed

A message is delivered when the receiving server accepts it. It is inboxed when it lands in the inbox the person actually reads. Between the two sit spam folders, Promotions tabs, quarantines and silent filtering. A server can accept your message and still file it where nobody looks.

That is why a clean bounce report doesn't prove anything about placement. Bounces tell you which addresses refused you. They say nothing about the ones that accepted you and then hid the message.

The four levers of email deliverability

Placement comes down to four things. When it drops, one of them changed.

1. Authentication: can the receiver verify the mail really came from your domain.

2. Reputation: what mailbox providers have learned about your domain and inboxes from past sending.

3. List quality: whether the addresses exist and want, or at least tolerate, your email.

4. Content and volume: what you say, how many links you use, and how fast you send.

You don't tune all four at once. You check them in that order, because the early ones are binary: either authentication passes or it doesn't.

Lever 1: authentication

SPF says which servers may send for your domain. DKIM signs each message so it can't be altered unnoticed. DMARC tells receivers what to do when the other two fail. Google's sender guidelines and Yahoo's sender hub require this setup from bulk senders, and for cold email you should treat it as mandatory anyway.

Start here, because a failing record can sink a whole domain on its own. SPF, DKIM and DMARC for cold email walks through each record and how to check it.

Lever 2: reputation

Providers keep a running opinion of your domain and of each inbox. A new domain has none, and a domain that jumps from zero to full volume looks like a spammer whatever the copy says. Reputation is built by sending steadily to people who don't complain, and lost by the opposite.

Two guides cover it: email warmup for building a history on a new domain, and domain reputation for how it is scored, checked and repaired. In SendingOS, warmup runs on a pool of real Google and Microsoft inboxes only, with no SMTP accounts in it.

Lever 3: list quality

Sending to addresses that don't exist tells providers you don't know who you're emailing. That shows up as bounces first, and as spam placement soon after. Hard bounces mean the address is gone; soft bounces are temporary and need different handling. Hard bounce vs soft bounce explains the split, and high email bounce rate helps you work out whether the problem is the list or the domain.

Verify before you send. In SendingOS, email verification is free, so there's no cost reason to skip it. Every bounce is also read and sorted into hard, soft or block with its reason and SMTP code, so you can see which problems come from the list.

Lever 4: content and volume

Content problems are usually stacking problems. One link is fine. Link shorteners, several links, image-only emails, attachments in a first touch and a shared tracking domain together are a different story. Volume works the same way: the speed of change matters more than the absolute number. How to stop emails going to spam covers the content checks, and how many cold emails per day shows how to plan volume instead of guessing it.

How to measure it

No single number tells you your deliverability. You triangulate from several signals.

Google's sender guidelines say to keep the spam rate shown in Postmaster Tools below 0.1% and never let it reach 0.3%. That is the number to remember.

For hands-on checks, email spam test shows how to test placement and where those tests mislead you. If you want tooling to automate the checks, email deliverability tools covers what each category does. In SendingOS, every inbox's connection is checked every few minutes, and domain health rules can pause a drifting domain's inboxes before the whole campaign suffers.

Where to start

If you're setting up from scratch, go in lever order: authentication, then a warmup period, then a verified list, then a small first send. If something is already wrong, check what changed in the days before the drop. A new list, a volume jump and a DNS edit explain most sudden problems.