Email Deliverability
Email deliverability is engineering, not marketing. It's the science of making sure the emails you SEND actually arrive in the INBOX (not spam, not blocked, not silently dropped). The KnowMBA POV: deliverability is owned by infrastructure, not by content writers. The pillars: (1) authentication — SPF, DKIM, DMARC must be configured correctly. (2) sender reputation — IP and domain warmth. (3) list hygiene — bouncing, unengaged, and complaint-prone addresses removed. (4) engagement signals — opens, clicks, replies, marks-as-important. The inbox-placement rate (% of sent emails that reach the inbox vs. spam folder) is the only deliverability KPI that matters; open rate is downstream and useless without it.
The Trap
The trap is treating deliverability as a marketing problem solved with 'better subject lines.' It isn't. If your DMARC alignment is broken, no subject line saves you — Google sends you to spam regardless. The other trap: assuming Mailgun, SendGrid, Postmark, or your ESP 'handles it.' They handle the infrastructure, but your domain reputation, list quality, and authentication are your problem. The third trap: blasting cold lists from your warm domain. One spam campaign can crater a 6-month-warmed sender reputation overnight, taking your entire transactional email pipeline down with it.
What to Do
Audit and fix deliverability in 5 steps: (1) Authenticate: configure SPF, DKIM, and DMARC (set DMARC to p=quarantine then p=reject after 30 days of clean reports). (2) Separate sending domains: marketing email from sub.yourdomain.com, transactional from another subdomain — never mix. (3) Warm new IPs/domains slowly: 50 emails day 1, doubling daily for 4 weeks, before sending campaigns. (4) Monitor with Google Postmaster Tools, Microsoft SNDS, and a deliverability platform (Validity, GlockApps, Litmus). (5) Cull aggressively: any subscriber with 0 opens in 90 days, soft-bounce 3x in a row, or any complaint goes off the list immediately. Inbox-placement rate target: 95%+. Below 90% = active deliverability problem.
Formula
In Practice
Mailgun, SendGrid, and Postmark — the three major transactional email infrastructure providers — publicly publish deliverability benchmarks and warn customers that ESP choice does NOT solve deliverability problems for them. Postmark in particular built their entire brand around 'transactional only' (refusing marketing email) precisely because mixing the two on shared IPs destroys deliverability. Postmark's median inbox-placement rate is reported above 99% to Google's mailboxes specifically because they engineer aggressively for sender reputation and refuse to host the kind of content that would damage it.
Pro Tips
- 01
Run a DMARC report parser (e.g., Valimail, Postmark DMARC) for your first 60 days. Most companies discover 1-3 unauthorized senders sending email FROM their domain — usually a forgotten SaaS tool or a vendor. Each unauthorized sender hurts deliverability and creates a phishing risk.
- 02
Set up Google Postmaster Tools the day you start sending. It's free, it's the only authoritative source for what Google thinks of your domain reputation, and most marketers have never heard of it. If your Postmaster reputation drops to 'Medium' or 'Low,' you have weeks not months to fix it before campaigns start hitting spam.
- 03
Run a 'sunset policy' — auto-unsubscribe anyone with 0 engagement in 90-180 days. Yes, it shrinks your list. Yes, it improves your deliverability dramatically. The unengaged subscriber who 'might re-engage someday' is currently dragging your inbox-placement rate down for everyone else.
Myth vs Reality
Myth
“Bigger email list = better email program”
Reality
A 50K list with 40% engagement outperforms a 500K list with 4% engagement on EVERY metric — opens, clicks, revenue per send, AND inbox placement (Gmail and Outlook downgrade reputation when engagement craters). The 'list size' vanity metric is one of the most expensive mistakes in B2B marketing.
Myth
“Your ESP (Mailchimp, Klaviyo, SendGrid) handles deliverability for you”
Reality
ESPs handle infrastructure, not your sender reputation, list hygiene, or authentication. Switching ESPs to fix a deliverability problem is like changing cars to fix a driver — the underlying behavior is the actual issue. ESPs typically refuse to debug your deliverability problems beyond authentication checks.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your email open rate dropped from 24% to 8% in 4 weeks across all campaigns. Subject lines and content haven't changed. What's the most likely cause?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Inbox Placement Rate
Bulk and transactional email programsElite
98-100%
Healthy
95-98%
Acceptable
90-95%
Problematic
80-90%
Crisis
< 80%
Source: https://www.validity.com (Sender Score / Return Path benchmarks)
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Postmark
2010-present
Postmark built an entire business around the insight that mixing marketing and transactional email destroys deliverability. They explicitly REFUSE to send marketing email — only transactional (password resets, receipts, notifications). The result: their median inbox-placement rate to major mailbox providers exceeds 99%, dramatically higher than competitors who serve both use cases on shared infrastructure. Their thesis: deliverability is engineering, and you cannot 'engineer' deliverability around content that subscribers consistently don't engage with.
Median Inbox Placement
> 99%
Marketing Email Allowed
No
Pricing Premium
~3-5x SendGrid for transactional
Deliverability is fundamentally about WHAT you send, not just HOW. Refusing the wrong content is sometimes the highest-leverage deliverability investment.
SendGrid (Twilio)
2009-present
SendGrid (acquired by Twilio for $3B in 2019) processes 100B+ emails monthly. Their core insight from operating at that scale: customer behavior matters more than infrastructure. They publicly publish deliverability guides warning customers that one spam complaint per 1,000 sends starts to damage reputation; one per 100 sends triggers ISP blocks. SendGrid built reputation-monitoring tooling and an Expert Services team specifically because customer practices — not infrastructure — drive 80%+ of deliverability failures.
Monthly Email Volume
100B+
Acquisition Price
$3B (2019)
Complaint Rate Threshold
0.1% triggers reputation damage
Even the largest email infrastructure providers admit: customer behavior, not infrastructure, drives 80%+ of deliverability outcomes.
Decision scenario
The Cold Email Campaign Decision
You're CMO at a B2B SaaS doing $8M ARR. The new VP Sales pitches a 50,000-prospect cold email campaign using a list bought from a data vendor. He wants to send from your primary domain (yourdomain.com) for credibility. Your transactional email (password resets, billing notices) and warm marketing email both run from this same domain. Inbox placement rate is currently 96%.
Sending Domain
yourdomain.com (single)
Current Inbox Placement
96%
Monthly Transactional Volume
180,000
Monthly Marketing Volume
85,000
Decision 1
VP Sales argues the campaign could generate 200+ leads. The cost of one campaign seems trivial. You know cold email to 50K unverified addresses will produce massive complaint and bounce rates — and from your warm primary domain.
Approve the campaign — one send won't hurt, the lead potential is real, and you can always recover deliverability laterReveal
Refuse to send from the primary domain. Set up a new cold-outreach subdomain (outreach.yourdomain.com), warm it for 4 weeks, and only then run the campaign — accepting it will take 6-8 weeks before the first send✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Email Deliverability into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Email Deliverability into a live operating decision.
Use Email Deliverability as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.