Deliverability

Cold email deliverability guide

Everything that decides whether your cold email is read or filtered — domain setup, authentication, warmup, volume, list quality, bounces, replies and monitoring — in the exact order to fix it in.

Why deliverability breaks

Deliverability failures are rarely one dramatic mistake. They are three quiet ones, compounding.

One missing DNS record

A single missing or misconfigured SPF, DKIM or DMARC entry can silently route every send straight to spam, with no error shown anywhere.

Reputation decays fast

A cold or newly-purchased domain has zero sending history — providers throttle and filter aggressively until you prove consistent, low-complaint behavior.

One bad list ruins the domain

A single unverified list with a high bounce rate can tank a domain's reputation for weeks, dragging every future campaign down with it.

The six pillars of deliverability

Infrastructure

Dedicated sending domains, correct MX and a custom tracking domain that matches your brand.

Authentication

SPF, DKIM and DMARC aligned and published before your first send.

Reputation

Warmup for two to four weeks, then ramp volume gradually per mailbox.

List hygiene

Verified addresses, no catch-alls at scale, and aggressive suppression.

Content signals

Plain text, few links, no spam trigger phrases and a real unsubscribe path.

Volume pacing

Stay under provider limits, spread sends across the day and rotate mailboxes.

Domain setup

Use a lookalike domain for outbound so campaign activity can never affect your primary domain. Point the correct MX records at your receiving infrastructure and add a custom tracking domain with valid TLS that matches your brand.

Never send cold email from your primary domain

A reputation problem on your outbound domain is recoverable. The same problem on the domain your invoices and support email leave from is not.

In MunchReach, a domain has to pass DNS verification before any mailbox on it can go active — see Email Accounts.

SPF

SPF publishes a TXT record listing which mail servers are authorized to send on behalf of your domain.

Add one SPF TXT record per domain — multiple SPF records invalidate each other.

v=spf1 include:_spf.munchreach.app ~all

DKIM

DKIM adds a cryptographic signature to each message so receiving servers can verify it wasn't altered in transit.

Publish the selector record supplied for your sending domain.

selector._domainkey.yourdomain.com → v=DKIM1; k=rsa; p=MIGfMA0...

DMARC

DMARC tells receiving servers what to do when SPF or DKIM fail, and where to send aggregate failure reports.

Start at p=none while you monitor reports, then tighten once alignment is clean.

v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Publish all three before your first send

Authentication changes propagate within hours, but reputation is cumulative — fixing DNS after a bad launch does not undo the damage.

Mailbox setup

Connect mailboxes only on verified domains. Each mailbox is connection-tested when it is added, and the result is recorded so you can see when a connection starts failing. Scale sending by adding mailboxes rather than pushing a single mailbox harder.

Best practice

Rotate sends across several mailboxes and spread them through the working day rather than firing a batch at one time.

Warmup

Warm up for two to four weeks before campaign traffic, then ramp gradually. This conservative four-week schedule keeps reputation intact.

PeriodVolumeNotes
Week 15–10 emails/dayWarmup network only, internal replies encouraged
Week 215–25 emails/dayWarmup continues, first small campaign batches allowed
Week 330–40 emails/dayReal campaign traffic, monitor bounce and complaint rate daily
Week 4+40–50 emails/dayFull campaign volume if bounce stays under 2%, complaints under 0.1%

MunchReach's warmup engine paces this automatically and keeps running alongside campaign traffic.

Sending volume

Cap a healthy warmed mailbox at 30–50 emails per day. Stay under provider limits, spread sends across the day and rotate mailboxes. Scale by adding mailboxes, never by pushing one mailbox harder.

List quality

Verify every address before import, avoid catch-all domains at scale because those recipients cannot be verified, and suppress aggressively. On import, MunchReach reports every skipped row with a reason: invalid, duplicate in the file, or already in the workspace.

Catch-all lists inflate invalid sends

Catch-all recipients accept everything, so verification tools cannot tell a real mailbox from a dead one. Sending to them at volume hurts reputation.

Bounce management

Keep bounce rate under 2%. Hard bounces should be suppressed immediately and never retried — a repeated send to a dead address is one of the strongest negative signals a provider tracks. Pause and investigate the list rather than the copy when bounces spike.

Unsubscribe handling

Every message needs an unsubscribe link or a plain-text opt-out. Opt-outs must be honoured across the whole workspace, not just the campaign that triggered them, and suppression has to apply before the next batch is queued.

Complaints matter more than unsubscribes

Keep complaints under 0.1%. Making the opt-out obvious is what keeps that number low.

Reply management

Replies are the strongest positive signal a mailbox can generate, so route them somewhere they get answered. Sequences stop automatically on reply, bounce and unsubscribe, so a prospect never receives a follow-up after answering. Every reply lands in the Unified Inbox, threaded onto the original conversation.

Campaign practices

Keep the first email plain text with at most one link and no attachments. Multiple links, tracking pixels and image-heavy HTML all add risk. Use variables with fallbacks so a missing field never breaks a sentence, and check the unresolved variable report before launching.

Three to four touches over 10–14 days is the sweet spot — after that, response rate per additional email drops sharply. Ready-made structures live in the cold email template library.

Setup in the right order: buy a sending domain, publish DNS records, warm up the mailbox, then send small, measure and scale — increasing only while bounces stay under 2%.

Monitoring deliverability

Watch bounce rate, complaint rate and reply rate daily during a ramp. This is what good inbox placement looks like on a properly authenticated, warmed domain sending under 50 emails per day per mailbox with a verified list.

Inbox78% of test sends
Promotions / Other tab14%
Spam6%
Blocked / not delivered2%

The analytics funnel separates a delivery problem from a copy problem: delivery falling off points at infrastructure, healthy delivery with no replies points at the message.

Pre-launch checklist

  • SPF record exists and passes alignment
  • DKIM signature verifies for the sending domain
  • DMARC published and monitored
  • Custom tracking domain with valid TLS
  • Bounce rate under 2% and complaints under 0.1%
  • Every list verified before import
  • Unsubscribe link or plain-text opt-out in every message
  • Warmup running continuously on every mailbox
We went from 40% spam placement to consistent inbox delivery just by fixing DMARC alignment and slowing our ramp down.
Marcus WebbFounder, B2B lead gen agency
FAQ

Common questions

Everything you need to know about MunchReach.

Check your setup in minutes

Connect a mailbox and MunchReach validates authentication, warmup status and sending limits automatically.