How Email Warmup Actually Works (And Why Most Teams Skip It)
Email warmup gradually builds a new mailbox's sending reputation by simulating normal human email behavior before real outreach begins. Skipping it is the most common reason a new domain lands in spam permanently.
Email warmup is the process of gradually increasing sending volume from a new mailbox while generating positive engagement signals — opens, replies, and inbox placement — so mailbox providers learn to treat the sender as legitimate before real outreach begins.
The reason it exists: providers like Google and Microsoft evaluate senders on behavior over time, not on a single message. A brand-new domain that sends 300 emails on day one is exhibiting a pattern that closely matches a spam operation, regardless of what the emails say. The content is almost irrelevant to that judgment.
Skipping warmup doesn't produce slightly worse results. It frequently produces a domain that lands in spam and stays there, and recovering a burned domain is considerably harder than warming a fresh one.
What actually happens during warmup
Four mechanisms run simultaneously.
Gradual volume ramp. A new mailbox starts very low — around 5 emails per day is typical — and increases over roughly two to four weeks toward its target sending volume. The curve matters more than the endpoint: a mailbox jumping from 5 to 200 in a day exhibits the same suspicious pattern as one that started at 200.
Engagement simulation. Warmup emails circulate through a network of participating mailboxes that open them, reply to some, and mark them as important. These are exactly the signals providers use to distinguish wanted mail from unwanted mail, and a new mailbox otherwise generates none of them.
Spam-folder recovery. When a warmup email lands in a recipient's spam folder, the receiving mailbox moves it to the inbox and marks it as not-spam. This is one of the strongest positive corrections available, because it directly contradicts the filter's classification.
Content variation. Warmup emails use varied, natural-sounding content rather than identical templates. Identical repeated content across a network is itself a detectable pattern, which would defeat the purpose.
The part most warmup discussions skip: DNS comes first
Warmup cannot fix an unauthenticated domain. If SPF, DKIM, and DMARC aren't correctly configured, you're building reputation for a sender that providers can't verify — which caps how much reputation is achievable regardless of how patient the ramp is.
The order that works:
- 1.Configure SPF, DKIM, and DMARC on the sending domain and verify each independently resolves
- 2.Then start warmup — not simultaneously, since records take time to propagate and warmup sends during that gap are wasted
- 3.Then send real outreach — only after the mailbox has reached target volume with acceptable inbox placement
A related discipline: warmup traffic should run on domains isolated from your live campaign domains. Mixing them means warmup patterns and real campaign patterns compound into one reputation signal, and a problem in either contaminates the other.
How to know when a mailbox is actually ready
"It's been three weeks" is not readiness. Two conditions should both be satisfied:
- —Inbox placement rate — warmup emails from this mailbox are consistently landing in the inbox rather than spam or promotions
- —Minimum ramp duration — the mailbox has been warming long enough to establish a pattern, typically at least two weeks
Both, not either. A mailbox with good placement after four days hasn't established a history; a mailbox with three weeks of poor placement has established the wrong one, and increasing its volume will make things worse rather than better.
If placement is poor at the end of a warmup period, the correct response is diagnosing the cause — usually DNS misconfiguration, a domain with prior history, or a blacklisted IP — rather than pushing the mailbox live and hoping.
Warmup doesn't survive contact with a bad list
This is the failure mode that catches teams who did everything else right. A perfectly warmed mailbox sending to an unverified list will burn its reputation within days.
Hard bounces are the fastest reputation destroyer available. Verify email addresses before sending — syntax, MX record, and catch-all detection — and suppress hard bounces permanently rather than retrying them.
Two further constraints that apply regardless of warmup quality:
- —Spam complaint rate under 0.3% — Google and Yahoo's bulk sender requirements set this threshold for senders at volume, and crossing it results in throttling or blocking
- —One-click unsubscribe via the List-Unsubscribe header — a required mechanism for bulk senders, and not satisfied by a link in the email body alone
Warmup builds reputation. List hygiene and compliance are what prevent you from spending it in a week.
Why teams skip it
Three reasons, all understandable and all expensive.
It takes weeks and produces nothing visible. A founder who set up four sending domains on Monday wants to send on Tuesday. Warmup asks for three weeks of no output, which is genuinely hard to accept when pipeline is the pressure.
The damage is invisible and delayed. Skipping warmup doesn't produce an error message. Emails send successfully, the dashboard shows them as delivered, and they land in spam folders you never see. The failure is silent, which makes it easy to misattribute to copy quality months later.
It seems like a large-sender problem. It isn't. New domains are scrutinized more heavily than established ones precisely because they have no history, so a small sender on a fresh domain is often in a worse position than a large sender on an old one.
The practical checklist
Before your first real campaign from a new mailbox:
- —SPF, DKIM, and DMARC configured and independently verified
- —Custom tracking domain set up (not a shared one)
- —Warmup running on isolated domains, starting at ~5 emails/day
- —Minimum two weeks of ramp completed
- —Inbox placement rate acceptable and stable, not just improving
- —Target list verified, with hard bounces suppressed
- —List-Unsubscribe header implemented
- —Per-mailbox daily sending cap set below the provider's own limit
The last item catches people: provider limits apply regardless of your warmup status. A fully warmed Gmail mailbox still has a daily ceiling, and hitting it repeatedly is its own reputation signal.
FAQ
Typically two to four weeks from a new mailbox to full sending volume. Readiness depends on both elapsed ramp time and measured inbox placement, not on the calendar alone.
Around 5 per day at the start, increasing gradually. The rate of increase matters as much as the starting point — sudden volume jumps produce the same suspicious pattern as starting high.
An established domain with good sending history needs less warmup than a fresh one, but a new mailbox on that domain still needs a ramp. Domain age helps; it doesn't eliminate the requirement.
No. Warmup builds reputation for a correctly configured sender. It cannot compensate for missing SPF/DKIM/DMARC records, an unverified list, or a blacklisted domain — those need to be fixed first.
Emails send successfully but frequently land in spam, and because there's no error, the problem stays invisible while reputation degrades. A domain that establishes a poor reputation early is significantly harder to recover than one warmed properly from the start.
Below 0.3%. Google and Yahoo's bulk sender requirements set this threshold for high-volume senders, and exceeding it can result in throttled or blocked delivery.