Your campaign is live. Reply rate is 0.3%. Open rate is 8%. Emails are sending fine — at least according to your tool. But something is clearly broken. Most cold email troubleshooting advice tells you to check your subject line. That's almost never the real problem. The real problem is almost always the inbox — and this guide walks through every failure mode we've seen, in order of frequency.
Diagnose Before You Fix Anything
The biggest troubleshooting mistake is changing variables before knowing what's broken. We've seen teams rewrite entire sequences, rebuild their lists, and switch sending tools — when the issue was a single misconfigured DKIM record that took 10 minutes to fix. Run the diagnostic checks below before touching anything else.
The 4-Check Diagnostic Stack
Google Postmaster Tools — Check domain reputation at postmaster.google.com. Good or High = inbox is healthy. Medium = borderline. Unknown or Low = inbox is compromised. This tells you the root cause of 60–70% of cold email failures.
MXToolbox SPF/DKIM/DMARC check — Run mxtoolbox.com/SuperTool.aspx for all three records. All three must show PASS. One failure here explains poor deliverability regardless of inbox reputation.
Mail-tester.com score — Send a test email and check your score. Under 8/10 means a fixable configuration problem. A Litemail pre-warmed inbox consistently scores 10/10 from day one.
Bounce rate last 7 days — Pull bounce data from your sending tool. Over 3% in the last 7 days means list quality is actively damaging your sender reputation.
Diagnostic Result | Likely Problem | Priority |
|---|---|---|
Postmaster: Unknown/Low | Inbox not warmed or blacklisted | Critical — stop sending |
DKIM fail | Misconfigured DNS record | Critical — fix immediately |
Mail-tester under 7/10 | Auth chain broken or IP listed | High — investigate before sending |
Bounce rate over 3% | List quality destroying reputation | High — clean list before next send |
All checks pass, low open rate | Subject line or inbox placement issue | Medium — check placement separately |
DNS Record Failures — The Most Common Fixable Problem
In our testing at Litemail, around 40% of cold email deliverability problems we investigate trace back to a broken DNS record. SPF misconfiguration is the most common. DKIM selector mismatch is second. DMARC policy set incorrectly is third.
SPF Record Problems
The most common SPF mistake is having multiple SPF records on the same domain. You can only have one SPF TXT record. Multiple records cause the SPF check to fail with a "PermError" — which many sending tools don't flag clearly. Run mxtoolbox.com SPF check and look for PermError in the results.
The correct SPF record format for Google Workspace cold email: v=spf1 include:_spf.google.com ~all. For Microsoft 365: v=spf1 include:spf.protection.outlook.com ~all. Don't use -all (hard fail) — it's more aggressive and can cause legitimate emails to fail when forwarded.
DKIM Selector Mismatch
DKIM failures often occur when the DKIM selector in your DNS record doesn't match the selector your sending tool is using. Check which selector your sending platform expects — Google Workspace uses "google" by default. Your DNS record should have a CNAME or TXT record at google._domainkey.yourdomain.com. If that record is missing or pointing to the wrong value, DKIM fails silently and deliverability drops.
DMARC Policy Too Restrictive or Missing
DMARC set to p=reject before your domain is fully established causes legitimate emails to be rejected. Start with p=none to monitor, move to p=quarantine after 30 days of clean data, then p=reject after 60 days if your SPF and DKIM pass rates are consistently above 98%. All Litemail inboxes ship with DMARC pre-configured at the appropriate policy for the account's warmup stage.
Spam Folder Placement: What's Actually Causing It
Emails landing in spam or promotions when your DNS records all pass is a reputation problem — not a configuration problem. The fix is different depending on which folder they're landing in.
Primary Inbox → Spam Folder
This is a sender reputation issue. Your inbox or domain has accumulated negative signals: high complaint rate, high bounce rate, sending to inactive or invalid addresses, or zero engagement on previous sends. Check Postmaster Tools first. If reputation is Low or Unknown, stop sending. A fresh or lightly-warmed inbox can't survive even one campaign to a dirty list.
Primary Inbox → Promotions Tab
Promotions placement is a content signal, not a reputation signal. The most common causes: HTML-heavy emails with multiple links, unsubscribe links that signal marketing rather than personal email, and subject lines with commercial language. Switch to plain-text emails with one link maximum. Remove "unsubscribe" footers from cold outreach sequences — they're not legally required for B2B cold email and they signal mass marketing to Gmail's filters.
Delivered → No Opens at All
This one's not always a deliverability problem. If placement is confirmed primary and opens are near zero, the issue is likely a tracking pixel problem (some clients block pixel tracking) or genuinely disinterested contacts. Test with Litmus or email preview tools to confirm the email is rendering correctly. Then evaluate the list quality — a 0% open rate on a well-placed email usually means the targeting is wrong, not the inbox.
Throttling and Rate Limit Recovery: Step by Step
Throttling is different from blacklisting. A throttled inbox is still functional — it's just temporarily limited by the mail server. Recovery is faster, but only if you don't keep pushing volume while the limit is active.
Pause all sends from the affected inbox immediately. Running sends while throttled deepens the restriction and extends recovery time. 24–48 hours of zero sending is the minimum pause.
Check your hourly send rate in the 24 hours before throttle started. Throttle events are almost always triggered by an unusual send rate spike. Identify what caused it — a sequence restart, an import of a large list, a manual batch send.
Resume at 50% of your pre-throttle daily volume. Don't return to the previous rate immediately. Start at half, hold for 3–5 days, then step back up by 20% every 3 days.
Monitor bounce rate during recovery. Keep it under 2%. Throttle events often happen alongside list quality issues — if the bounce rate caused the throttle, fix the list before resuming.
🚩 The Mistake That Extends Throttle Recovery to 3 Weeks
Switching to a different inbox on the same domain while one inbox is throttled doesn't reset the clock — it extends it. Microsoft and Google track at the domain level, not just the account level. If inbox A is throttled and you spin up inbox B on the same domain and push volume, both inboxes end up restricted. Move to a completely different domain, or pause all sending on that domain during recovery.
Blacklist Recovery: The Realistic Timeline
Blacklisting is the worst-case scenario. Most teams that get blacklisted were using fresh inboxes, skipped list hygiene, or ran the same domain across too many campaigns without cooling off periods. Recovery is possible — but it takes longer than most guides admit.
First, identify which blacklist. Use mxtoolbox.com/blacklists.aspx — it checks 100+ lists simultaneously. Being on Spamhaus is far more serious than being on a smaller list. Spamhaus delisting requires a manual request, evidence of corrective action, and often 7–14 days of review even after you fix the problem.
For smaller lists: fix the underlying issue (list quality, complaint rate, DNS), request delisting, and most smaller lists delist within 24–48 hours. Keep sending volume low during recovery — 20–30 emails per day on the affected domain.
For Spamhaus or major lists: realistically plan for 2–4 weeks before full recovery. Run campaigns on separate pre-warmed domains in the interim. Don't pause your outbound programme — move volume to clean infrastructure while the affected domain recovers.
Fix Infrastructure Problems Before They Need Troubleshooting
Most inbox problems in this guide are preventable with pre-warmed inboxes and automated DNS setup. Litemail delivers inboxes with correct SPF/DKIM/DMARC pre-configured, verified Good or High in Postmaster Tools, and dedicated IPs that don't share reputation with other senders. $4.99/inbox.
Get Pre-Warmed Inboxes from $4.99 →
Works with Instantly, Smartlead, Lemlist, Apollo · Full admin access · Automated DNS · No minimum order
About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach. From $4.99/inbox with automated DNS, dedicated US and EU IPs, and full admin access. View pre-warmed inbox plans →
Related reading:
Cold Email Deliverability Recovery 2026 · SPF Record Errors Troubleshooting · DMARC Not Working Fix Guide 2026 · Outlook Cold Email Blacklist Recovery · Cold Email Inbox IP Reputation Guide
Key Takeaways
Run the 4-check diagnostic stack before changing anything — Postmaster Tools, DNS check, mail-tester.com, and bounce rate data from the last 7 days.
40% of deliverability problems trace back to a broken DNS record — SPF PermError from multiple records is the most common single cause.
Promotions tab placement is a content problem; spam folder placement is a reputation problem. The fixes are completely different — don't conflate them.
During throttle recovery, pause for 24–48 hours then resume at 50% volume. Switching to a different inbox on the same domain during throttle extends the restriction.
Spamhaus delisting takes 7–14 days after corrective action. Plan for 2–4 weeks of reduced capacity on a blacklisted domain and shift volume to clean pre-warmed inboxes during recovery.
Pre-warmed inboxes with automated DNS prevent the majority of the problems in this guide from occurring in the first place — prevention costs less than recovery.
Frequently Asked Questions
Why is my cold email going to spam even though DNS records are configured correctly?
Correct DNS records are necessary but not sufficient. Spam placement despite passing DNS checks usually means sender reputation is Low or Unknown in Google Postmaster Tools — a sign that the inbox has no warmup history or has accumulated negative signals from previous sends. Check Postmaster Tools first. If reputation is anything below Good, stop sending and either warm the inbox or replace it with a pre-warmed one.
How do I check if my cold email inbox is blacklisted?
Use mxtoolbox.com/blacklists.aspx — it checks your domain or IP against 100+ blacklists simultaneously. Check both your sending domain and the IP address of the server you're sending from. A clean domain on a blacklisted shared IP will still have deliverability problems.
What is the difference between throttling and being blacklisted?
Throttling is a temporary rate limit applied by the receiving mail server — it slows your emails but still delivers them eventually. Blacklisting blocks delivery outright. Throttle events show up as delayed delivery in your sending tool. Blacklisting shows up as bounce errors or permanent delivery failures. Both require you to pause sending, but the recovery process is different.
How long does it take to fix cold email deliverability problems?
DNS misconfigurations fix in under an hour once identified. Throttle events typically resolve in 24–48 hours with a sending pause. Reputation recovery (Low or Unknown in Postmaster) takes 2–4 weeks of clean sending at low volume. Blacklist recovery ranges from 24 hours (small lists) to 2–4 weeks (Spamhaus). The fastest path is moving volume to clean pre-warmed inboxes while damaged domains recover.
Should I use a new domain or try to recover a damaged one?
Depends on the severity. For throttle events or minor reputation dips — recover the existing domain. For Unknown/Low Postmaster reputation after a bad campaign, or for blacklist events — provision a fresh pre-warmed domain and inbox. Recovery is possible but slow. A new pre-warmed domain is campaign-ready in 24 hours.
What bounce rate triggers a cold email deliverability problem?
Keep bounce rate under 2% per campaign send. Above 3% in a 24-hour period starts triggering provider flags. Above 5% on a fresh inbox almost guarantees a throttle or suspension event. Use email verification tools before every send — this single step prevents the majority of bounce-related deliverability damage.
Can pre-warmed inboxes prevent cold email troubleshooting problems?
Yes — they prevent most of them. Pre-warmed inboxes from Litemail ship with correct DNS configuration, verified Good/High Postmaster reputation, and dedicated IPs with clean sending history. The DNS misconfiguration problems, the zero-reputation suspensions, and the shared IP blacklisting issues that cause most cold email failures simply don't apply. You still need clean lists and sensible sending schedules — but the infrastructure layer is solved from day one.
Buy Pre-Warmed Email Inboxes & Domains | Litemail
Buy pre-warmed email accounts, inboxes and domains from $4.99/inbox. Google Workspace & Microsoft 365. Automated DNS, US & EU IPs. Setup in 5 minutes.
Related reading:
Cold Email Deliverability Recovery 2026 · SPF Record Errors Troubleshooting · DMARC Not Working Fix 2026 · Cold Email Blacklist Prevention · Outlook Blacklist Recovery
📺 Watch: Cold Email Deliverability Troubleshooting 2026 — search YouTube for walkthroughs from Lemlist or Hunter.io channels covering DNS setup and inbox repair for cold email.
