EmaReach Playbook

Cold Email Deliverability:
The System That Lands.

Most teams burn domains chasing volume. At EmaReach, we engineer reputation first — and scale from a foundation that lasts. This is the exact infrastructure-first framework we run for every customer.

Book a Demo

No lock-in. Setup in days, not weeks.

Core principle

System > CopyReputation > VolumeLongevity > Spikes

35–40/ inbox / day

Safe daily send cap

Per mailbox after warmup

7+days

Warmup before scale

Minimum ramp period

<2%bounce

Hard reputation limit

Exceed this and domains burn

3-layerauth

SPF · DKIM · DMARC

Required before day one

Chapter 1

Most teams are playing the wrong game.

What most teams think

“Send more = get more replies.”

The result: burned domains, 2% open rates, and campaigns that die in weeks.

How we run it at EmaReach

Infrastructure + reputation drives outcomes.

Build the system right once, and it compounds — month after month.

Chapter 2

Infrastructure calculator for cold email scale

Enter your target daily send volume. We calculate root domains, sending domains, and inbox count using a fixed cap of five subdomains per root and safe per-inbox limits.

Root domains needed

5

At least 1,200 sends/day capacity per root with our defaults.

Subdomains per root (fixed)

5

We do not allow more than 5 subdomains per root domain.

Sending domains per root

6

1 apex + 5 subdomains

Total sending domains

30

Inboxes per sending domain

5

Default used to hit your volume safely.

Daily volume per inbox

40

Human-like daily cap per mailbox.

Total managed inboxes

150

Achievable daily volume

6,000

Matches your target.

Live math

5 root domains × (5 subdomains + 1) × 5 inboxes × 40 emails/day = 6,000 emails/day

Sized for your target of 6,000 emails/day. If one sending domain is flagged, the impact is about 0.67% of total daily sends.

Monthly volume (30-day month)

180,000 emails / month

Based on your target of 6,000 emails/day × 30 days.

Want this infrastructure running for your team?

We handle the entire setup — domains, inboxes, warmup, and monitoring.

Book a demo
Chapter 3 — 4

What we enforce on every single send.

Sending behavior we enforce
  • We spread sends across 8-10 hours
  • We randomize delays between each email
  • We mimic realistic human sending behavior
  • We avoid sudden volume spikes per inbox

Sending 500 emails in one burst is a high-risk spam pattern.

Technical backbone at EmaReach

SPF

We configure SPF so mailbox providers can verify sending authorization.

DKIM

We sign outbound mail with DKIM to improve trust and alignment.

DMARC

We enforce DMARC policy so your domain has a clear trust model.

Custom tracking domain

We route tracking through branded domains to avoid spammy link patterns.

Separate tracking domain

We isolate tracking reputation from core sending reputation.

If this layer is missing, inbox placement drops no matter how good the copy is.

Chapter 5

Our most critical outbound system

New inboxes start with zero trust. We ramp carefully and build real interaction signals.

Warmup ramp-up timeline

Day 1-7

5-10 emails/day

Day 8-14

15-20 emails/day

Day 15-21

25-30 emails/day

Day 7+

35-40 emails/day

Warmup signals we track

  • Replies (not just sends)
  • Marking messages as important
  • Manual spam rescue signals where needed
  • Natural back-and-forth conversation behavior

Tools help, but realistic behavior is what builds domain trust over time.

Chapter 6

A bad list will burn a good domain.

Your sending infrastructure can be perfect — and a dirty list will still destroy your reputation within a campaign.

What we verify before every send
  • Remove hard bounces before every campaign send
  • Verify emails with ZeroBounce or similar before import
  • Never send to scraped or unverified cold lists
  • Re-verify stale lists older than 6 months
  • Keep bounce rate under 2% to protect domain reputation
  • Segment by engagement — suppress contacts with zero opens after 3 touches
What happens when you skip verification

Bounce rate > 5%

Immediate domain trust hit — providers flag the sending pattern

Spam trap hits

Can trigger blacklisting across major email filters

Low open rate on bad lists

Poisons your overall domain engagement score

Verification is not optional. Unverified imports are the #1 cause of sudden bounce spikes.

Chapter 7

Write like a person. Deliver like infrastructure.

Spam filters read your copy. So do recipients. The rules below apply to both.

Plain text first

Emails that look like they came from a real person outperform HTML newsletters for cold outreach every time.

3–5 lines per message

Short, confident messages signal intent. Long walls of text read like marketing blasts and trigger spam filters.

One clear ask per email

A single low-friction call-to-action drives more replies than listing multiple options or CTAs.

Avoid spam trigger words

Terms like 'free', 'guarantee', 'act now', or excessive punctuation pattern-match to bulk spam and hurt placement.

Personalization that lands

First name, company, and a single relevant context signal (industry, role, recent news) makes each email feel 1:1.

What works

“Hey [First Name], saw you're scaling your SDR team — wanted to share how [Company] is handling reply rates right now. Worth a quick call?”

What doesn't

“GUARANTEED results! Our FREE platform helps 10,000+ companies drive MASSIVE ROI. Click here to schedule a demo, download our whitepaper, and start your free trial TODAY!!!”

Chapter 8

A reply is the most powerful deliverability signal.

Every reply tells mailbox providers this email was wanted. We track engagement at every stage of the funnel — not just opens.

SignalImpactWhy it matters
Direct reply receivedHighThe strongest positive spam signal — a reply tells every provider the email was welcomed.
Thread continuationHighMulti-turn conversations build domain trust over time and compound inbox placement.
Marked as important / starredMediumIndicates positive intent from the recipient — boosts sender reputation with Gmail especially.
Link clickLow–MediumRelevant but weaker than a reply. Don't optimize for clicks over replies — it trains the wrong behavior.
UnsubscribeNegativeHigh unsubscribe signals list-fit problems. Keep it under 0.5% to avoid algorithmic penalties.

EmaReach tracks reply threads, not just sends

Our reply-detection system monitors inboxes for responses, logs conversation threads, and feeds engagement data back into your sending cadence automatically — so active threads never get interrupted by automated follow-ups.

Chapter 9

Never launch blind. Test before every sequence.

EmaReach includes built-in deliverability testing — no third-party integrations required to verify placement before you scale.

Required

Verify SPF, DKIM, and DMARC all pass before first send

Required

Run a spam score check on your email content and HTML

Required

Test inbox placement across Gmail, Outlook, and corporate filters

Recommended

Send to a seed list covering major email providers

Recommended

Monitor open rates in the first 48 hours as an early placement indicator

Recommended

Run a re-test after any major sequence or content change

What EmaReach's built-in testing covers

Domain authentication check

Validates SPF, DKIM, and DMARC records are properly configured and passing before any campaign launches.

Inbox placement probe

Sends test messages to seed inboxes across major providers and reports where mail lands — inbox, spam, or promotions.

Warmup domain mail test

Runs a pre-flight check on newly warmed domains to confirm they're ready for live outbound volume before scaling.

Chapter 10 — 12

The mistakes that kill campaigns — and the mindset that fixes them.

Why teams still fail
  • Open rates can collapse to around 2%
  • Messages start landing in spam or promotions
  • Domains burn quickly and lose trust
  • More domains cannot fix weak reputation systems
The EmaReach operator mindset

Wrong question

“How many emails can I send?”

Right question

“How long can I keep this domain alive?”

The game is protecting domain health while scaling predictable outbound. Longevity compounds — short-term volume doesn't.

Your starter playbook

Ready to run this yourself?
Here's exactly where to start.

Follow these five steps in order. Don't skip the warmup. Don't rush the scale.

  1. Start with 5-10 domains
  2. Use 2-3 inboxes per domain
  3. Warm up for 2-3 weeks before scale
  4. Begin at 20-30 emails per inbox/day
  5. Increase volume only when placement is stable
Book a Demo

We set up, manage, and protect your entire sending infrastructure.

FAQ

Common questions about cold email deliverability

Answers to the most frequently asked questions about our infrastructure, warmup process, and sending best practices.

How long does cold email warmup take?

A safe warmup takes 21-28 days, starting at 5-10 emails/day and gradually increasing. Rushing warmup is the #1 cause of domain burns.

How many inboxes do I need at scale?

EmaReach recommends 2-3 inboxes per sending domain, 5-6 sending domains per root, and a daily cap of 40 emails per inbox. Use the infrastructure calculator above to size your exact setup.

What causes cold emails to land in spam?

Main causes: missing SPF/DKIM/DMARC, high bounce rates from unverified lists, sending too fast on new domains, spam-trigger words in content, and low engagement signals.

What is the safest daily email limit per inbox?

35-40 emails per inbox per day is the safe cap after a full warmup. Exceeding this creates sudden volume spikes that trigger spam filters across all major providers.

Can EmaReach handle our entire cold email infrastructure?

Yes. EmaReach sets up, manages, and monitors your full sending infrastructure — domains, inboxes, warmup, authentication, and deliverability testing — so your team can focus on pipeline, not plumbing.

Still have questions?

Our team handles setup, warmup, and monitoring — just tell us your volume target.

Book a Demo