Blog / Deliverability

Cold Email Deliverability: The Complete Guide

27 April 2026

Cold email deliverability is the ability of your outbound mail to reach the recipient’s inbox rather than the spam folder or a hard bounce. It depends on a stack of factors working together. Each one is covered below: authenticated DNS records, isolated sending infrastructure, a proper warmup ramp, controlled volume, a low complaint rate, and genuine recipient engagement. No single setting fixes it, and no provider can guarantee a placement percentage.

Deliverability vs delivery: a critical distinction

These two terms get used interchangeably, and the confusion costs senders real money.

Delivery means the receiving mail server accepted your message instead of rejecting it. A “delivered” status means the message did not bounce. That is all it means.

Deliverability means where the accepted message actually landed — the inbox, the promotions tab, or the spam folder. This is what determines whether anyone reads your mail.

The gap matters because most sending tools report delivery, not deliverability. A campaign can show 99% delivery while most of those messages sit unseen in spam. You cannot infer inbox placement from a delivery rate; the only way to know where mail lands is to test it — see how to test cold email deliverability for the seed-list and placement-test methods.

The deliverability stack

Inbox placement is the sum of several independent layers. A weakness in any one of them drags the others down.

Layer	What it controls	Common failure
Authentication	Whether receivers can verify the sender	Missing or broken SPF/DKIM/DMARC
Infrastructure isolation	Whether one bad domain harms others	Shared tenants and shared reputation
Warmup	Whether a new domain looks trustworthy	Sending full volume on day one
Volume control	Whether sending looks human	Sudden spikes, too much per mailbox
Complaints	The heaviest negative signal	Poor targeting, unwanted mail
Engagement	Whether recipients react positively	Irrelevant mail, no replies

The rest of this guide works through each layer.

Authentication: SPF, DKIM, DMARC

Authentication is how a receiving server confirms your mail is genuinely from your domain and was not forged. Without it, modern providers treat your mail with suspicion by default. Three DNS records carry the load:

• SPF (Sender Policy Framework) lists which servers are allowed to send for your domain. See SPF records for cold email.
• DKIM (DomainKeys Identified Mail) adds a cryptographic signature so receivers can detect tampering or forgery.
• DMARC (Domain-based Message Authentication, Reporting and Conformance) tells receivers what to do when SPF or DKIM fail.

Since February 2024, Google and Yahoo require bulk senders to authenticate with SPF, DKIM, and DMARC, support one-click unsubscribe, and keep their spam complaint rate low — commonly cited as under roughly 0.3%. Authentication is the entry ticket, not an optimisation. A full walkthrough lives in the SPF, DKIM, DMARC setup checklist.

Infrastructure isolation

Reputation attaches to a domain and the tenant it sends from. If many unrelated senders share the same infrastructure, one careless neighbour can pull down everyone’s placement. This is the case against cheap shared setups for cold email.

Isolation means each sending domain runs on its own dedicated Microsoft 365 tenant, so its reputation rises or falls on its own behaviour alone. It also keeps cold campaigns off your primary brand domain, so a burned sending domain never threatens your core identity — which is why most experienced senders never run cold outbound from their main company domain. They also plan for the fact that domains burn out under sustained volume, often within a few months.

Warmup: building trust before volume

A brand-new domain has no reputation. If it suddenly sends hundreds of cold messages, receivers read that pattern as spam and filter it. Warmup is the gradual ramp that builds a positive sending history first: low volume, increasing slowly, with simulated engagement, before real campaign traffic flows.

Warmup takes weeks, not days, and continues at a lower level after campaigns start. There is no instant or pre-warmed shortcut — trust is earned through time and behaviour. The email warmup explainer covers the mechanics.

Volume control

Even a warmed domain can be burned by volume. Keep per-mailbox daily volume modest and spread the total across several domains and mailboxes rather than forcing it through a few; sudden spikes look automated and trigger filtering.

There are hard ceilings too. Exchange Online enforces approximate limits of 10,000 recipients per 24 hours per mailbox, 30 messages per minute, and a maximum of 1,000 recipients per message. Cold-email volume should sit far below these technical caps — the deliverability-safe number is much lower than the ceiling. For how to choose the right daily figure, see how many cold emails per day.

Complaints and engagement

These two signals decide deliverability over the long run, and both trace back to targeting rather than configuration.

A spam complaint is the heaviest negative signal in the system. It happens when a recipient marks your mail as junk, or when their provider infers the same. Even a complaint rate well under 1% can drag a domain down, and complaints almost always come from mailing people who never wanted to hear from you.

Engagement is the positive counterweight — opens, replies, and the absence of instant deletes. Providers increasingly treat low engagement as a filtering signal in its own right: a domain that sends thousands of messages and earns almost no replies looks, statistically, like one worth filtering. Tighter targeting and relevant copy do more for deliverability than any DNS tweak. More in why cold emails go to spam.

What deliverability is not

Strong deliverability gets wanted mail to the inbox. It does not make unwanted mail acceptable, and it does not grant legal permission to send. Consent and local law sit with you as the sender. Germany’s UWG §7(2) generally requires prior opt-in for advertising email even between businesses, and several EU markets take a similar line. Healthy infrastructure is necessary, not sufficient — and none of this is legal advice.

How Mailionaire approaches this

Mailionaire provisions each sending domain on its own isolated Microsoft 365 tenant, sets SPF, DKIM, and DMARC automatically, and runs warmup from the start, so the full stack is in place before you send. Monitoring watches the wear signals and the self-healing model replaces mailboxes and domains as they degrade. Pricing is a flat $50 per active domain per month, with EU/Swiss data residency available as an optional add-on rather than the default. See how it works for the full picture.

FAQ

What is the difference between email delivery and deliverability?

Delivery means the receiving server accepted your message instead of bouncing it. Deliverability means where the accepted message landed — inbox or spam. A campaign can show near-perfect delivery while most mail sits in spam, so delivery rate alone tells you almost nothing about results.

What hurts cold email deliverability the most?

Spam complaints carry the heaviest weight, followed by low engagement and sending to spam traps on scraped or stale lists. Broken SPF, DKIM, or DMARC compounds the damage. Most deliverability problems trace back to poor targeting and volume the recipient never wanted.

How long until cold email deliverability is reliable?

Plan for several weeks. New domains and mailboxes need a warmup ramp before they carry campaign volume, and reputation builds gradually from real recipient engagement. There is no instant path — pushing full volume on day one is the fastest way to land in spam.

Does good deliverability make cold email legal?

No. Deliverability is purely technical — it governs whether mail reaches the inbox, not whether you are allowed to send it. Consent and local law sit with you as the sender. Germany's UWG §7(2) requires prior opt-in even for B2B advertising email. This is not legal advice.

---