Cold email outreach operates under fundamentally different infrastructure constraints than permission-based marketing email. The complaint rates from cold outreach are structurally higher than from opt-in lists — you're reaching people who didn't ask to hear from you, so the percentage who mark as spam is always going to be higher than from engaged subscribers. This means cold email requires dedicated sending infrastructure that's completely isolated from marketing email, smaller per-domain volume limits, more aggressive inbox rotation, and continuous deliverability monitoring to catch degradation before it becomes unrecoverable damage.

Best practices
following industry standards reduces deliverability failures 80%
Data-driven
measuring before and after every change is essential
ISP feedback
use Postmaster Tools, SNDS, and FBL data to guide decisions
Iterative
email deliverability is never a one-time fix — it requires ongoing monitoring

How Cold Email Infrastructure Differs from Marketing Email

Cold email operates in a structurally different deliverability environment:

  • Complaint rate: 0.2–1% is typical for cold email vs 0.05–0.10% for opt-in marketing email. This means cold email must use infrastructure that can tolerate higher complaint signals without contaminating higher-value sending.
  • Sending volume per domain: Large volume from a single domain signals bulk cold email to spam filters. Effective cold email infrastructure uses many domains at low volume each rather than one domain at high volume.
  • Inbox aging: Email inboxes used for cold outreach accumulate negative reputation signals over time. Regular rotation and inbox replacement maintains fresh deliverability.
  • Authentication requirements: Same as marketing email — SPF, DKIM, DMARC are mandatory for any deliverability. The 2024 Gmail/Yahoo requirements apply to any sender above 5K/day including cold outreach.

How Many Domains and Inboxes You Need

The required scale depends on your target daily outreach volume:

Daily sends targetDomains neededInboxes neededNotes
50–200/day2–33–6Conservative; appropriate for testing
200–500/day4–68–15Small-scale outreach programme
500–2,000/day10–2020–50Medium-scale; requires active management
2,000–10,000/day30–7060–150Large scale; dedicated infrastructure required

General rules: approximately 30 emails per inbox per day maximum to maintain good deliverability. One inbox per domain for most setups (2–3 for larger sending volume per domain). Warm each domain and inbox before running campaigns.

Domain selection for cold outreach: use domains similar to your main domain (variations, with different TLDs, or descriptive terms) but never your primary business domain. Protect your main domain by keeping cold outreach completely separate.

Domain and Inbox Warming for Cold Outreach

Cold email warming differs from IP warming for marketing email because the volume per domain/inbox is much lower:

Week 1: 2–5 emails/day per inbox (real conversations with colleagues/contacts)
Week 2: 5–10 emails/day per inbox (continue real email + first outreach)
Week 3: 10–20 emails/day per inbox
Week 4+: Up to 30 emails/day per inbox at full campaign speed

Many cold email platforms (Instantly, Lemlist, Apollo) have built-in warmup modes that automatically send emails between warmup network inboxes to simulate real engagement before campaigns start.

Key requirements during warming:

  • Use a domain age of at least 2–3 weeks before starting outreach (very new domains get aggressive spam treatment)
  • Ensure SPF, DKIM, and DMARC are configured before warming begins
  • Configure a matching website (even a simple landing page) at the domain — domains with no associated website look suspicious
  • Use a professional Google Workspace or Microsoft 365 inbox, not generic SMTP

Daily Sending Limits That Preserve Deliverability

Respecting per-inbox limits is more important than maximising daily volume:

  • 30 emails/day per inbox maximum for Google Workspace or Microsoft 365 inboxes used for cold outreach. Going above this generates rate-limiting and accelerates reputation degradation.
  • Send with gaps between emails: Sending 30 emails in rapid succession looks automated. Platforms with built-in send-time randomisation (sending one email every 3–10 minutes) perform better than batch sending.
  • Respect weekend patterns: Sending Friday afternoon to Monday morning produces worse deliverability — the emails sit unread over the weekend, increasing the proportion that are marked as spam or ignored entirely when recipients return.
  • Business hours delivery: Aim for delivery during the recipient's local business hours (7am–6pm) for best open and reply rates. Most cold email platforms support timezone-aware scheduling.

Technical Configuration Checklist

For each cold email domain:

  • SPF record: v=spf1 include:_spf.google.com -all (for Google Workspace) or equivalent for your provider
  • DKIM: Enable in Google Workspace Admin or Microsoft 365 admin console
  • DMARC: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com (minimum)
  • Custom tracking domain for link tracking (avoid using ESP's shared tracking domain)
  • Custom bounced email handler (configure bounce processing so invalid addresses are suppressed)
  • Unsubscribe link in all emails (required by Gmail/Yahoo 2024 requirements; also CAN-SPAM)

Monitoring Cold Email Deliverability

Cold email deliverability degrades gradually before it fails catastrophically. Monitor these signals:

  • Open rate trend per inbox: A declining open rate from a specific inbox (without changing content) indicates that inbox's reputation is degrading. Retire or re-warm it.
  • Reply-to-open ratio: If opens stay constant but replies decline, your content or targeting is the issue, not deliverability.
  • Bounce rate: Above 3% indicates poor list quality requiring verification before further sends.
  • Spam placement (weekly seed test): Use GlockApps or Instantly's inbox placement testing to check where emails from each domain are landing. Test at least once per week for active campaigns.
  • Domain blacklist monitoring: Check all sending domains monthly against MXToolbox. Any blacklist listing requires immediate investigation and domain rest or replacement.