Email deliverability: the complete guide

Quick answer

Email deliverability is whether your messages reach the inbox instead of the spam folder or a block. For cold outbound it is mostly infrastructure and behavior, not wording: authenticate the domain with SPF, DKIM and DMARC, warm the domain up before sending real volume, keep the list clean and verified, respect sensible daily limits, and earn positive engagement. Get those right and good copy gets read. Get them wrong and the best email in the world lands in spam. This guide covers each layer in the order you should build it.

What actually decides deliverability?

It helps to separate deliverability from delivery. Delivery means the receiving server accepted the message. Deliverability means it reached the inbox, not the spam folder. You can have near-perfect delivery and still fail, because the mail all landed in spam.

Mailbox providers like Google and Microsoft make the inbox-or-spam decision using a handful of signals:

• Authentication: can they verify the mail really came from your domain and was not altered? That is SPF, DKIM and DMARC.
• Reputation: does the sending domain and IP have a track record of wanted mail, or of spam and bounces?
• Engagement: do recipients open, reply, and not mark you as spam?
• List quality: are you sending to real, verified addresses, or hitting dead mailboxes and spam traps?
• Content: does the message look like the spammy mail they already filter?

Notice that content is last, not first. Most outbound fails on the layers above it. We will walk them in build order.

How do you authenticate a sending domain?

Authentication is the foundation. Without it, mailbox providers have no way to trust that your mail is really yours, and modern senders without it get filtered or rejected. Three standards work together.

• SPF (Sender Policy Framework) is a DNS TXT record that lists which servers are allowed to send email on behalf of your domain.
• DKIM (DomainKeys Identified Mail) adds a cryptographic signature to the message header, so the receiver can verify the mail was authorized by your domain and was not altered in transit.
• DMARC (Domain-based Message Authentication, Reporting and Conformance) is a DNS policy that tells receivers what to do when SPF or DKIM fail, with options of none, quarantine or reject, and where to send reports about who is sending as your domain. It relies on alignment with SPF and DKIM.

All three should be in place before you send a single cold email. The full walkthrough, including how they reinforce each other, is in SPF, DKIM and DMARC explained.

What is sender reputation, and how do you build it?

Reputation is the running score mailbox providers keep on your sending domain and IP. It is built from behavior over time: consistent volume, low bounces, low spam complaints, and real engagement. A brand-new domain has no reputation at all, which is why it cannot be trusted with volume on day one.

Two habits protect reputation from the start:

• Use a separate sending domain for cold outbound. Many teams send cold outbound from a secondary domain rather than their primary brand domain, so a reputation problem never touches the main domain their customers and investors email. Often this is a lookalike domain, for example a .co or .io variant of the brand.
• Keep sending patterns steady. Sudden spikes in volume, or long gaps followed by a surge, read as suspicious. Steady, predictable sending builds trust faster than bursts.

How do you warm up a new domain?

Warm-up is the process of gradually increasing sending volume from a new or cold domain and mailbox so providers build a positive reputation for it over time. You start with a low number of sends per day and ramp up over weeks, mixing in messages that get opened and replied to, before you point real campaigns at it.

Sending high volume from a cold domain on day one is one of the fastest ways to get filtered, and it can burn the domain before you have sent anything useful. The step-by-step ramp, and how many domains and inboxes to run, is covered in how to warm up a sending domain.

How much can you send per inbox?

Even a warmed domain has a sensible ceiling. Pushing too many emails from one inbox, or scaling faster than your reputation supports, pushes you toward spam. The usual fix is to scale with more inboxes and domains rather than more volume per inbox, so each mailbox stays within a safe daily range. Reasonable limits and how to think about scaling are in how many emails per day.

Does list quality affect deliverability?

A lot. Sending to bad addresses causes bounces, and a high bounce rate is one of the clearest signals to a mailbox provider that you are not a careful sender. Dead mailboxes and recycled spam-trap addresses do direct damage to reputation.

So verify every address before you send, remove role addresses and obvious risks, and keep your bounce rate low. Clean data is a deliverability lever, not just a data-quality nicety. How list building and verification fit the wider engine is in the B2B outbound guide and how to build a prospect list.

Where does content fit in?

Content matters, but it is the last layer, not the first. Once the infrastructure is sound, a few content habits keep you out of trouble: write like a person rather than a marketer, avoid heavy formatting and image-only emails, go easy on links, and skip the spam-trigger phrasing and fake urgency. Plain text that reads like a real one-to-one email tends to perform best.

The practical, run-before-launch version of all of this is in how to avoid the spam folder, and the deeper reasons messages get filtered are in why cold emails go to spam.

Here is how the layers stack up:

Where Enablemnt fits

Deliverability is the layer where most early-stage outbound quietly dies, and it is unglamorous work: DNS records, warm-up schedules, separate domains, inbox limits, and verification. It takes weeks of setup before a single campaign is safe to launch, and a founder-led team rarely has that time.

Enablemnt builds that foundation for you. As your embedded RevOps and outbound team, we set up SPF, DKIM and DMARC, stand up and warm the sending domains, and check inbox placement before launch, all inside a fixed 14-day sprint. You start sending on infrastructure that is already sound, and you own it at the end.

If you would rather have deliverability built right the first time than learn it by burning a domain, tell us about your startup and we will map it out on a short call.

Filed under Outbound & cold email. Written by Enablemnt AI.