​

Cold Email Deliverability Guide

Deliverability — not copy, not targeting — is the single largest determinant of cold email campaign performance. Without proper infrastructure, authentication, and warm-up, roughly 46% of emails never reach the recipient’s inbox. Fully authenticated senders are up to 2.7x more likely to land in the primary inbox, which means fixing your DNS records is as much a pipeline initiative as hiring another SDR.

​

Why deliverability is the #1 factor in cold email success

Most teams that struggle with cold email blame copy or list quality first. They rewrite subject lines, swap CTAs, and rebuild their ICP — while half their emails sit in spam folders unseen. When agencies audit underperforming campaigns, they routinely find deliverability sitting at 50–60% inbox placement. That means 40–50% of outreach volume produces zero impressions, zero opens, and zero pipeline. The math is unforgiving. If you send 1,000 cold emails with a 50% inbox placement rate, only 500 arrive. At a 5% reply rate on delivered emails, that’s 25 replies. Improve inbox placement to 90% and you get 900 delivered, yielding 45 replies from the same list — an 80% increase in output with zero change to copy, targeting, or volume. Every percentage point of deliverability compounds directly into meetings booked. Deliverability breaks down into three layers: authentication (proving you are who you claim to be), reputation (building trust through consistent sending behavior), and content (avoiding the patterns spam filters flag). Most failures happen at layers one and two — the infrastructure — long before content enters the equation.

​

What infrastructure do you need for cold email?

Cold email infrastructure requires four non-negotiable foundations: dedicated sending domains, proper authentication records, warmed IP addresses or accounts, and monitoring systems. Skip any one of these and you are building on sand. Dedicated sending domains. Never send cold email from your primary business domain. Use secondary domains (e.g., getacme.com or acmeleads.com instead of acme.com) so that if a domain takes a reputation hit, your main corporate email remains unaffected. For volume campaigns, rotate across multiple sending domains — if one gets flagged, the others continue operating. Sending limits per account. Sending 500 emails from one inbox destroys deliverability. Sending 30 emails per day from 17 accounts protects each domain’s reputation while maintaining total throughput. Cap each sending account at 30–50 campaign emails per day and scale horizontally by adding accounts, not by increasing volume per account. Dedicated vs. shared IPs. Shared IP addresses mean your deliverability is at the mercy of other senders on that pool. One bad actor can tank the reputation for everyone. Dedicated IPs give you full control over your sender reputation, but they require proper warm-up — ISPs treat new IPs with zero history the same way a bank treats someone with no credit score. Custom tracking domains. Default tracking domains from outreach tools are shared across thousands of senders. Setting up a branded CNAME (e.g., track.getacme.com) isolates your tracking reputation from other senders and looks cleaner to spam filters.

​

SPF, DKIM, and DMARC explained simply

These three authentication protocols are DNS records that prove to receiving mail servers that you are authorized to send email from your domain. Google, Yahoo, and Microsoft (as of May 2025) all enforce these for bulk senders. Without them, your emails get spam-foldered or outright rejected. SPF implementation. Add a TXT record listing every service authorized to send on your behalf. Example: v=spf1 include:_spf.google.com include:sendgrid.net ~all. Keep total DNS lookups at or below 10 per RFC 7208 — exceeding this limit returns a PermError that silently breaks authentication. DKIM implementation. Generate a key pair in your email platform, publish the public key as a TXT record, and enable signing. Use a minimum 1,024-bit key; 2,048-bit is preferred for stronger security. A missing character in the p= value or unsupported key length will cause silent failures. DMARC implementation. Start with p=none (monitoring mode) to collect data on your authentication results without blocking any mail. Review DMARC aggregate reports for 2–4 weeks to identify any legitimate senders that aren’t passing SPF or DKIM. Then tighten to p=quarantine and eventually p=reject. Research from Valimail shows that 75–80% of domains with a DMARC record struggle to enforce it, usually because SPF and DKIM weren’t properly configured first. Verification. After publishing all three records, wait 24–48 hours for DNS propagation. Then send a test email to a Gmail account, open “Show original,” and confirm you see SPF: PASS, DKIM: PASS, DMARC: PASS. Check Outlook headers for authentication results as well.

​

Common spam triggers and how to avoid them

Spam filters evaluate hundreds of signals. These are the ones that most frequently kill cold email campaigns: Content triggers:

• ALL CAPS in subject lines or body text — triggers both algorithmic and human spam reports
• Excessive punctuation (multiple exclamation marks, question marks)
• Deceptive or clickbait subject lines that don’t match body content
• Risky attachments (PDFs, ZIP files) in first-touch cold emails
• HTML-heavy formatting, colored fonts, or multiple images in what should read like a plain-text conversation
• Link-heavy emails — more than one or two links signals promotional content

Technical triggers:

• Missing or misconfigured SPF, DKIM, or DMARC records
• Shared tracking domains flagged by other senders’ behavior
• Sending from a domain with no warm-up history
• High bounce rates (above 2% total, with any hard bounces raising flags)
• Spam complaint rates approaching 0.3% — Google’s threshold for restricting sender privileges

Behavioral triggers:

• Sending 200+ emails per day from a single account
• Sudden volume spikes (going from 10 emails/day to 500 overnight)
• Low engagement rates (few opens, no replies) signaling recipients don’t want your mail
• No unsubscribe mechanism — Google, Yahoo, and Microsoft all require RFC 8058 one-click unsubscribe headers for bulk senders

What works instead: Keep emails between 25–100 words. One clear ask. Plain-text formatting. Dynamic personalization fields that show clear relevance to the recipient. A/B test two subject lines and two body variants per campaign, keep the winner, iterate.

​

Domain warm-up process and timeline

Warm-up is the process of gradually increasing sending volume on a new domain or IP to build positive sender reputation with mailbox providers. Skip it and ISPs treat your email the way a bank treats someone with no credit history — every small misstep triggers suspicion. Scorecard targets at steady state:

• Inbox placement: 80% or higher on seed tests
• Bounce rate: under 2% total, hard bounces near zero
• Spam complaint rate: under 0.1% (well below Google’s 0.3% enforcement threshold)
• Reply rate: 3–5% or higher by week three or four

​

Monitoring and blacklist management

Deliverability is not a set-and-forget configuration. It requires continuous monitoring with automated guardrails that catch problems before they compound. Core metrics to track weekly:

• Inbox placement rate — the percentage of emails landing in primary inbox vs. spam/promotions (target 80%+)
• Open rate — sudden dips signal deliverability issues, not copy problems
• Reply rate — the ultimate signal of healthy deliverability plus relevant messaging
• Bounce rate — pause any sending account that exceeds 2% on a send
• Spam complaint rate — monitor via Gmail Postmaster Tools; investigate any spike toward 0.1%

Inbox placement testing. Run recurring seed tests by sending to test accounts across Gmail, Outlook, and Yahoo. This tells you exactly where your emails land — primary inbox, promotions tab, spam folder, or blocked entirely. Run these tests before launching new campaigns and weekly during active sends. Blacklist monitoring. Hundreds of blacklists exist, and landing on even one can cascade into deliverability problems across providers. Automated monitoring tools check your sending IPs and domains against these lists and alert you when you’re flagged. If blacklisted, the remediation process varies by list — some require a formal delisting request, others clear automatically after the offending behavior stops. Auto-pause guardrails. Set rules to automatically pause a sending account if bounce rate exceeds 2%, spam complaint rate rises toward 0.3%, or inbox placement dips below your threshold (typically 75%). Fix the underlying issue, re-warm for 3–5 days, then resume. This prevents a single bad send from burning an entire domain’s reputation. Troubleshooting common issues:

• High bounces: Pause sends immediately. Re-verify the contact segment. Remove recently acquired or unvalidated domains. Resume at a lower daily cap after verification passes.
• Spam placement spike: Confirm SPF/DKIM/DMARC alignment is passing. Disable link tracking temporarily. Reduce daily caps by 50%. Re-warm the affected inbox for 3–5 days.
• Complaint spike: Check that one-click unsubscribe headers are functioning. Refine targeting criteria. Suppress non-engagers (contacts who haven’t opened in 2+ campaigns) faster. Monitor Postmaster spam rate for 72 hours before resuming full volume.

​

DIY deliverability vs. managed infrastructure

The gap between knowing what to do and executing it consistently across dozens of domains and accounts is where most in-house teams break down. Here’s how the two approaches compare in practice: The deciding factor is usually not cost — it’s consistency. DIY works when someone owns deliverability as their primary job. It fails when it’s one of fifteen responsibilities on a marketing ops person’s plate, because the monitoring gaps and configuration drift accumulate silently until pipeline craters.

​

How Outbound System manages deliverability

We treat deliverability as infrastructure, not an afterthought. Every client engagement includes dedicated sending domains with full SPF, DKIM, and DMARC configuration; automated warm-up sequences before any campaign launches; continuous inbox placement monitoring across Gmail, Outlook, and Yahoo; and auto-pause guardrails that protect domain reputation from runaway bounces or complaints. This infrastructure layer is why our campaigns consistently produce the reply rates and meeting volumes our clients see — the copy and targeting matter, but only because the infrastructure ensures those emails actually arrive in primary inboxes. For a deeper look at how we build and execute cold email campaigns end to end, see our cold email service page. For context on how cold email compares to other outbound channels, read our outbound lead generation guide.

---

Ready to stop losing pipeline to deliverability problems? Book a call to see how we build and manage the infrastructure behind high-performing cold email campaigns.

---