Outbound email deliverability basics
Deliverability is whether your email reaches the inbox rather than spam or rejection. It depends on domain authentication, sending reputation, list quality, and recipient engagement. Buying accurate data helps, but it does not by itself prevent messages being filtered.
Teams frequently blame data quality for outbound that does not land. Sometimes that is right. Often the data was fine and the sending setup was the problem, and the two failure modes look identical from a dashboard.
Authentication, the part that is non negotiable
Three records prove you are entitled to send from your domain. Without them, major providers will filter or reject regardless of content.
- SPF lists the servers permitted to send for your domain.
- DKIM cryptographically signs messages so tampering is detectable.
- DMARC tells receivers what to do when SPF or DKIM fails, and sends you reports.
All three are table stakes now. Major mailbox providers have tightened enforcement for bulk senders, and unauthenticated mail increasingly does not arrive at all.
Reputation, and why new domains fail
Receivers score sending domains and IPs on history. A domain with no history has no reputation, so sending high volume from a fresh domain looks exactly like a spam pattern.
Warming means starting at low daily volume and increasing gradually over weeks, ideally to recipients likely to engage. It is slow and there is no way to buy past it. Teams that skip warming usually burn the domain, and recovering a damaged sending reputation takes longer than warming would have.
Protect the primary domain
Send cold outbound from a separate domain, not the one carrying your business mail. If reputation is damaged, the blast radius is contained. This is standard practice and cheap insurance.
Where list quality actually matters
Bounce rate is the fastest way to damage reputation. Repeatedly hitting invalid addresses signals that you are not maintaining your list, and receivers respond accordingly.
This is where accurate data pays off, but the mechanism is worth being precise about. Verification prevents hard bounces, which protects reputation, which keeps you in the inbox. It does not make a poorly targeted message welcome. Verified data sent to people with no reason to care still produces complaints, and complaints do more damage than bounces.
Engagement is the modern signal
Receivers increasingly weigh whether recipients open, reply, and mark as not spam, against whether they delete unread or complain. This is why volume without targeting backfires: sending more to a weaker list depresses engagement, which depresses placement for everyone you contact.
Practically, that argues for smaller, better targeted sends over large ones. It also argues for genuinely relevant messages, which is a targeting and research problem rather than a technical one.
A working checklist
- SPF, DKIM, and DMARC configured and passing.
- Separate sending domain for cold outbound.
- Warmed gradually before volume sending.
- List verified before send, with hard bounces suppressed permanently.
- Unsubscribe honoured immediately and suppressed across all future sends.
- Volume matched to reply capacity rather than to list size.
Legal requirements sit alongside the technical ones. The FTC's CAN-SPAM guidance covers US sending, and the UK ICO's direct marketing rules cover the UK. They differ, and the rules that apply follow the recipient rather than the sender.
Common questions
Lower is better and the trend matters more than any single figure. A sudden rise means your list has decayed or verification has stopped working, and it should be treated as an incident rather than noise.
No. Verification prevents bounces, which protects reputation. Placement also depends on authentication, warming, engagement, and relevance. Any vendor promising guaranteed inbox placement is overselling.
Weeks rather than days, scaling with your intended volume. There is no way to shortcut it, and attempting to is the most common cause of a burned domain.
Have the sending setup reviewed before you scale
Our consulting team audits authentication, domain strategy, list hygiene, and sending patterns, then fixes what is limiting placement.