“Deliverability Slim” — Why Your Cold Email Lands in Spam and How to Fix the Infrastructure

You wrote a solid email. The subject line is tight. The offer is clear. You hit send — and nothing happens. No replies. No bounces. Just silence.

In most cases, the email didn’t land in spam because the copy was bad. It landed in spam because the infrastructure was never set up correctly. This is what we call “deliverability slim” — a campaign running on zero foundation, wondering why it isn’t working.

This post covers exactly why cold email deliverability fails and the precise infrastructure steps to fix it permanently.

Why Cold Email Lands in Spam: The Real Reasons

Most founders assume deliverability is about avoiding spam trigger words. It isn’t. Google and Microsoft’s spam filters have been machine-learning-based for years — they don’t keyword-scan your emails. What they do evaluate is sender reputation, and sender reputation is built on infrastructure.

The most common causes of poor cold email deliverability, in order of frequency:

• Missing or misconfigured DNS authentication — SPF, DKIM, and DMARC records tell receiving mail servers that your domain is legitimate. If any are missing or wrong, emails fail authentication checks and go to spam.
• Sending from a brand-new domain or inbox — A domain or address with no sending history has zero reputation. ISPs treat it with suspicion by default. You must warm it up before sending at volume.
• Sending too much, too fast — Even from a warmed domain, a sudden spike in send volume triggers spam filters. Most sequencing tools let you do this without warning you.
• High bounce rates — Sending to unverified lists inflates your bounce rate. A bounce rate above 3% damages your sender reputation significantly. Above 5% can get your domain blacklisted.
• Spam complaint rates above 0.1% — Google’s threshold is strict. More than 1 complaint per 1,000 emails sent and your deliverability deteriorates quickly.
• Sending from your primary domain — Your main company domain should almost never be used for cold outreach. If it gets blacklisted, your transactional email — invoices, onboarding, notifications — goes down with it.

The Cold Email Infrastructure Stack

Good deliverability isn’t a setting you toggle. It’s a stack of components that work together. Here’s what that stack looks like.

1. Separate sending domains

Register one or more domains specifically for cold outreach — never your main domain. These should be close variations: if your company is acme.com, register acmehq.com, getacme.com, or useacme.com. Each is disposable if reputation deteriorates. Your main domain stays clean. Budget: $10–15/year per domain at Namecheap or Cloudflare. Start with 2–3.

2. Authenticate every sending domain

Configure three DNS records before sending a single email from any domain:

• SPF — Specifies which mail servers are authorised to send for your domain. Add a TXT record pointing to your sending provider.
• DKIM — A cryptographic signature that verifies your email wasn’t tampered with in transit. Your sending tool generates the key; you add it as a DNS record.
• DMARC — Tells receiving servers what to do when SPF/DKIM fails. Start with p=none to monitor, then move to p=quarantine once sending is clean.

Verify all three at MXToolbox before sending anything. If any fail, fix them first.

3. Warm up every inbox

Inbox warmup simulates real email activity on a new address — sending and receiving emails with a network of other warmed inboxes, marking them as important, rescuing them from spam. It builds a sending reputation before you run outbound.

Tools that handle this automatically: Instantly (included in all plans), Smartlead (built in), Lemwarm (standalone). Run warmup for a minimum of 14 days. 21–30 days is better. During warmup, keep limits low: 10 emails/day in week 1, 20–30 by week 3.

4. Rotate inboxes as you scale

Rather than sending 500 emails/day from one inbox, send 25 emails each from 20 inboxes. This distributes your sending across multiple IP addresses and reputation pools. Tools like Instantly and Smartlead handle rotation automatically — you set up the inboxes, the tool distributes the sends.

5. Verify every list before sending

Every contact should have a verified email address before you send. Unverified lists have bounce rates of 5–15%, which is enough to destroy a domain’s reputation in days. Use MillionVerifier or NeverBounce on every list. Remove any email flagged as invalid or risky. Target a bounce rate below 2% — ideally under 1%.

6. Monitor reputation weekly

Set up Google Postmaster Tools for every sending domain. It shows you spam rate, domain reputation, IP reputation, and authentication status from Google’s perspective. Check weekly. If your spam rate creeps above 0.08%, pause and diagnose before continuing. Also check your domains against common blacklists monthly using MXToolbox’s blacklist checker.

The Deliverability Setup Checklist

• Register 2–3 sending domains (not your main domain)
• Create 2–3 Google Workspace inboxes per domain
• Configure SPF, DKIM, and DMARC on every domain
• Verify all DNS records with MXToolbox
• Start inbox warmup (minimum 14 days before sending)
• Verify your lead list with MillionVerifier before sending
• Set up Google Postmaster Tools for each domain
• After warmup: start sending at 20–30 emails per inbox per day maximum
• Scale volume gradually — never more than 50 emails/inbox/day in month one

What Good Deliverability Actually Looks Like

With this stack in place, you should expect: inbox placement rate of 90%+ (test with mail-tester.com), open rates of 40–60% on well-targeted campaigns, bounce rate below 2%, spam complaint rate below 0.1%, and domain reputation showing “High” in Google Postmaster Tools.

If your open rates are below 20%, deliverability is the first thing to fix — not the copy, not the offer, not the targeting. The emails aren’t being seen.

---