Cold email deliverability: what actually matters

Cold email deliverability has an entire industry of “hacks” attached to it. Almost none of them matter. What matters is a short list of boring fundamentals, done in order, and the discipline not to sabotage them with volume.

The fundamentals, in order

1. Authentication, complete

SPF, DKIM, and DMARC ( at least monitoring ) on the sending domain. This is table stakes — without it, everything else is noise. Receivers make a snap trust decision on unauthenticated mail, and cold mail starts with zero trust. Check yours free with the deliverability checker before anything else.

2. A warmed, real domain

Don't cold-send from your company's crown-jewel domain. Use a dedicated domain ( or subdomain ) that has sent normal mail for weeks, built a history of one-to-one conversations that got replies. A brand-new domain sending volume is the classic spam-folder pattern — the warmup is not optional. How to do it safely: email warmup explained.

3. Volume discipline

The single most common killer. A human being does not send hundreds of identical messages a day. Ramp slowly, keep daily sends modest per mailbox, and stop the moment reply rates or spam-placement tells you something's off. Every receiver models this; the “safe number” varies by sender reputation, which is exactly why nobody honest quotes you one.

4. List quality over everything

A bounce-heavy list is a reputation wound. Verify addresses before sending, remove hard bounces immediately, and prune non-responders over time. Fifty well-chosen, relevant recipients will outperform five thousand scraped ones — both for replies and for staying out of spam.

5. Engagement is the real filter

Receivers track opens, replies, moves to inbox, deletes-without- reading. Cold mail that reads like a human wrote it for one person gets replies; replies build the reputation that keeps the next send in the inbox. Template blasts rot the domain.

What mostly doesn't matter

• Spam-word lists. “Free” and “click here” won't sink an otherwise-healthy, relevant email. Filters are far more behavioral than lexical.
• Plain text vs HTML. Simple is fine and loads everywhere, but a clean, light HTML email from an authenticated domain does not land in spam for being HTML.
• One more tracking pixel. Heavy tracking infrastructure can slightly hurt; the marginal pixel is not your problem.
• “DMARC on a different domain than you send from.” Alignment failures are structural — fix the setup, not the symptom.

The honest odds

Even done perfectly, cold email is a numbers game with a real cost per reply. Done sloppily, it damages the domain for the legitimate mail too. If cold outreach is core to your pipeline, treat it as its own sending identity — never mixed with your support@ or billing@ traffic. That separation is more valuable than any “deliverability hack.”

SuperMailOS customers run cold programs on dedicated domains while product and support mail stays on clean ones — every domain gets its own authentication from the mail server's zone, and the deliverability dashboard shows spam placement per domain so you spot a burning domain before it costs you a week. Pricing is per mailbox, so an extra sending identity is a few dollars, not a new contract: see pricing.