The fastest way to destroy a new sending domain is to use it. Not misuse it — simply send the volume you normally send, on day one, to the list you already have. Mailbox providers have no history for you, no reason to trust you, and a well-trained instinct that an unknown sender producing sudden high volume is a compromised account rather than a marketing team with a launch date.
Email warm-up is the deliberate, gradual ramp that avoids this. It is not a growth hack or a tool you buy; it is a scheduling discipline, and the main thing it demands is patience at exactly the moment your organisation has least of it. This guide covers when warm-up is required, the rules every schedule follows, a concrete 30-day plan, how the problem differs for cold outreach and platform migrations, and why automated warm-up services tend to make things worse.
Warm-up does not build reputation directly. It creates the conditions under which reputation can be built — a steady, observable stream of mail that real people open, click and do not complain about, at a volume small enough that any problem is contained.
The mechanism is straightforward. Providers evaluate your behaviour against a model of what you normally do. A sender with no history has no model, so every message is judged conservatively. Each day of clean sending gives the provider more evidence, and the model tightens. Volume that would be filtered on day three is unremarkable on day thirty, not because anything about the mail changed, but because the sender is no longer a stranger.
This is why the sequence matters more than the total. Thirty thousand messages sent across four weeks in a rising curve builds reputation. The same thirty thousand sent on a Tuesday builds a filtering rule.
Warm-up is not required for every change. It is required whenever the identity a provider evaluates is new or unfamiliar.
Equally, warm-up is not needed when you stay on an established domain and a reputable shared IP pool and your volume stays within its usual range. Adding a new campaign type or changing your template does not require a ramp.
These are separate processes with different timelines, and confusing them leads teams to warm the wrong thing.
| Domain warm-up | IP warm-up | |
| Triggered by | A brand-new sending domain or subdomain | A new dedicated IP or a new IP pool |
| Matters most at | Gmail, Yahoo and Apple, which weigh the authenticated domain | Microsoft and traditional filters, which weigh the connecting IP |
| Typical duration | 4-6 weeks | 30-40 days at volume; 1-2 weeks for smaller senders |
| Survives a platform change? | Yes — the reputation follows the domain | No — a new IP starts from nothing |
| Needed on shared IPs? | Yes, always | No — the pool is already warm |
| Can you shortcut it? | No. Nothing transfers. | No. Buying a "pre-warmed" IP transfers no reputation. |
| Biggest risk | Sending broad volume before engagement history exists | Erratic daily volume, or gaps of 30 days or more |
The practical takeaway for most marketing teams: if you are below roughly 100,000 messages a month, use a reputable shared IP pool and warm only the domain. A dedicated IP requires consistent volume to stay warm, and an underused dedicated IP performs worse than a shared pool because its reputation keeps going cold between sends.
If you are launching a new domain and a new dedicated IP simultaneously, expect the longer of the two timelines and be conservative throughout, because you have two unknowns compounding.
Three things must be true before the first message goes out, because a warm-up built on a broken foundation simply teaches providers something false about you.
The standard pattern is to raise volume by 50% to 100% at each step and hold for two to three days before the next increase. Amazon SES's published guidance doubles daily through the early days; SendGrid's schedule is similar in shape. The exact numbers matter less than the curve.
Warm-up sends should go to the people most likely to open, click and reply — your 30-day engaged segment, and internal addresses before that. You are actively teaching the provider what response your mail generates, so the early evidence should be your best. Widen to 60-day, then 90-day engaged segments as you go, and leave dormant subscribers out of the warm-up entirely.
Gmail, Microsoft, Yahoo and Apple accept new mail at different rates, and Microsoft is consistently the slowest to open up. Splitting your ramp by provider lets you hold volume at Outlook while continuing to increase at Gmail, rather than throttling everything to the pace of the strictest one.
Gaps undo progress. Consistency is itself a signal, and an erratic pattern reads as unpredictable regardless of volume. SendGrid's guidance is blunt: never go 30 days or more without sending on a given IP. If you miss days mid-ramp, resume at the previous step rather than where the calendar says you should be.
The schedule is a plan, not a commitment. If complaints, bounces or deferrals rise at any step, hold volume — or reduce it — until they stabilise. Amazon SES's guidance is explicit that slowing or stopping the increase is the correct response to rising bounce or spam rates. A warm-up that takes six weeks instead of four is a minor inconvenience; a warm-up that damages the domain costs months.
Warm-up traffic should look like the campaigns you actually intend to send: same templates, same From identity, same links, same cadence. A warm-up conducted with plain-text one-liners teaches providers nothing useful about the HTML campaigns that follow, and the shift between them is itself a change in pattern.
The schedule below suits a mid-market sender ramping toward a few hundred thousand messages a month on a new domain. Scale the volumes to your own target — the proportions and the audience progression are the parts to keep.
| Days | Daily volume | Who you send to | What to watch |
| 1-3 | 200-500 | Internal addresses and staff, plus your most engaged 30-day openers | Any hard bounce at all — it means the list is dirty before you start |
| 4-7 | 1,000-2,500 | 30-day engaged segment only | Delivery acceptance; complaints should be effectively zero |
| 8-11 | 5,000-10,000 | 30-day engaged segment | Complaint rate — hold if it exceeds 0.05% |
| 12-15 | 15,000-25,000 | Add the 31-60 day engaged segment | Hard bounce rate; keep it under 0.5% |
| 16-19 | 40,000-60,000 | Add the 61-90 day engaged segment | Per-provider acceptance — Microsoft often lags Gmail here |
| 20-24 | 100,000-150,000 | 90-day engaged plus recent sign-ups | Postmaster Tools spam rate and compliance status |
| 25-30 | Ramp to full volume | Full active list, still excluding dormant subscribers | Everything; hold a day at each step if any metric moves |
Two notes on using this. First, the volumes are totals across all providers; split them proportionally to your list's provider mix, and expect to hold Microsoft back. Second, treat every row as conditional. If the metric in the fourth column moves in the wrong direction, repeat the row rather than advancing.
Senders moving millions of messages a month follow the same curve over a longer period and with more aggressive increases at the top end.
Amazon SES publishes a 30 to 40 day ramp, starting near 1,000 messages on day one and reaching production scale by day 40, with the early days doubling volume per mailbox provider. SendGrid publishes a 41-day hourly schedule and notes that warm-up can take up to 60 days, though most of its customers complete it within 30 and some finish in one to two weeks.
The important caveat both vendors attach is that no published schedule fits every sender. List age, hygiene, engagement and content all shift the appropriate pace. Use the published tables as a shape to follow, and let your own metrics set the speed.
Sales outreach from individual mailboxes follows different constraints, and applying marketing warm-up logic to it produces bad results.
Google Workspace permits 2,000 messages per user per day on paid accounts, and 500 on trial accounts. Those are technical ceilings, not recommendations. A realistic safe volume for cold outreach is 20 to 30 messages per inbox per day once established, starting at 5 to 10 during a three to four week ramp.
The reasoning is behavioural rather than technical: a real person does not send hundreds of near-identical messages a day, so an inbox that does looks automated regardless of whether it stayed inside policy limits. The scaling strategy that follows is horizontal — you add inboxes rather than increasing volume per inbox, typically two or three inboxes per domain across several domains.
Cold outreach should also never run from your primary business domain. Use separate sending domains so that a burned outreach domain does not take your corporate mail with it.
An ESP migration is a warm-up with an extra hazard: you have an existing audience and existing expectations, and a bad migration damages a domain that was previously healthy.
A category of services offers to warm your domain automatically by exchanging mail between networks of seed accounts that open, reply to and mark your messages as important. The appeal is obvious: the ramp happens without touching your real audience or your calendar.
The problem is that the engagement is synthetic. It comes from a network with no relationship to the people you actually want to reach, and it produces three distinct failure modes.
The distinction worth holding onto is between ramping and faking. Gradually increasing volume to real recipients is legitimate and necessary. Manufacturing engagement to simulate a history you do not have is neither, and it is getting easier for providers to spot.
Most warm-up problems announce themselves in the metrics before they become serious. This table maps the common signals to the right response.
| What you see | What it usually means | What to do |
| Hard bounces above 0.5% | The list was not validated before you started | Stop increasing. Run full list validation before resuming. |
| Complaint rate above 0.05% | You widened the audience too fast, or the content does not match what people signed up for | Drop back to the previous segment and hold for 3-5 days. |
| Acceptance fine at Gmail, poor at Outlook | Microsoft weighs IP reputation more heavily and ramps more slowly | Hold volume to Microsoft addresses while continuing elsewhere. |
| Deferrals (4xx) increasing | You are pushing volume faster than the provider will absorb | Reduce the daily increase and lengthen the schedule. Deferrals are a warning, not a failure. |
| Permanent rejections (5xx) | An authentication or compliance failure, not a warm-up problem | Stop and check SPF, DKIM, DMARC alignment and PTR records before sending again. |
| Open rates falling as volume rises | You are reaching less engaged segments faster than the reputation supports | Pause the widening. Hold at the last segment that performed. |
| Everything fine, then a sudden drop | A blocklist entry, often from a spam trap in a newly added segment | Check blocklists immediately. Identify and suppress the segment you last added. |
The general principle: deferrals mean slow down, rejections mean stop and investigate. A 4xx response is a provider throttling an unfamiliar sender, which is warm-up working as designed. A 5xx response is a hard failure that no amount of patience fixes.
Teams often treat the last row of the schedule as the finish line. It is not — reaching target volume and being trusted at that volume are different achievements, and the second one lags the first by a week or two.
Four conditions together indicate a completed warm-up. Your acceptance rate holds at 98% or better across every major provider, not just the friendliest one. Your complaint rate has stayed below 0.10% for at least two consecutive weeks at full volume. Deferrals have returned to baseline rather than merely declining. And a seed test shows inbox placement in line with what you would expect for a permissioned list — 95% or better.
If you hit target volume but deferrals are still elevated, the warm-up is not finished; the provider is still throttling you. Hold at that volume rather than continuing to climb, and let the remaining conditions catch up.
Once it is finished, the obligation does not end — it changes. A warm domain stays warm through consistent sending. Go quiet for a quarter and you will be doing an abbreviated version of this again.
The other warm-up nobody plans for is the one on an established domain. If your normal volume is 200,000 a month and Black Friday means 800,000 in a week, that departure from your model is treated much like an unfamiliar sender's, even though your domain is well established.
The fix is a compressed ramp of two to three weeks before the peak. Begin raising volume in mid-October for a late-November peak, using the extra headroom for genuinely useful sends — early-access previews, wishlist reminders, category content — to your engaged segments rather than padding. You are giving the provider evidence that higher volume from you is normal before the volume that matters arrives.
Two supporting moves make a material difference. Clean the list before the ramp rather than during it, because seasonal campaigns are when dormant subscribers get reactivated and complaints spike. And resist the temptation to mail lapsed segments "because it's Black Friday" — the annual traffic surge is the worst possible moment to introduce unfamiliar recipients, since every other sender is competing for the same filtering headroom.
Email warm-up is the least technically complex discipline in deliverability and one of the easiest to get wrong, because the failure mode is organisational rather than technical. The schedule is simple; holding to it while a campaign calendar pushes the other way is the hard part.
The programme that works is unglamorous: verify authentication, validate the list, register the monitoring dashboards, start small with your most engaged subscribers, roughly double every two to three days, split by provider, send every day, and let the metrics rather than the calendar decide when to advance. Four to six weeks of that produces a domain that providers trust — and no tool, purchased IP, or shortcut produces the same result faster.
Q1. What is email warm-up?
Email warm-up is the practice of gradually increasing sending volume from a new domain or IP address so that mailbox providers can build a reputation for you based on real recipient behaviour. It exists because an unknown sender that suddenly sends high volume is indistinguishable, from a filter's perspective, from a compromised account.
Q2. How long does email warm-up take?
For most marketing senders, four to six weeks. Amazon SES recommends a 30 to 40 day schedule for high-volume senders, and SendGrid notes that warm-up can take up to 60 days, though most of its customers finish within 30. Smaller senders on shared IPs can often complete a domain warm-up in two to three weeks.
Q3. Do I need to warm up if I use a shared IP pool?
You still need to warm the domain, but not the IP. A reputable shared pool is already warm, which is exactly why shared IPs are the better choice for senders below roughly 100,000 messages a month. Your domain, however, is new regardless of what IP it leaves through.
Q4. Can I buy a pre-warmed IP address and skip the process?
No. Reputation is not stored in an IP the way an asset is — it is a record of behaviour associated with that IP and with the domains sending through it. A previously warm IP that suddenly carries a new domain's mail at volume behaves exactly like an unwarmed one, and may perform worse if the prior sender's history was poor.
Q5. Should I use a dedicated IP or a shared IP?
A dedicated IP only makes sense above roughly 100,000 messages a month, because reputation needs consistent volume to stay warm. Below that threshold, a well-managed shared pool will usually outperform a dedicated IP you cannot keep busy, and it removes the warm-up burden entirely.
Q6. Do automated email warm-up tools work?
Gradual volume ramping is legitimate and necessary. Automated warm-up networks that exchange artificial replies between pools of seed accounts are a different thing, and mailbox providers have become good at recognising that traffic pattern. The engagement is synthetic, it looks nothing like your real campaigns, and the drop-off when real sending begins is itself a warning signal.
Q7. How many cold emails can I send per day from a new inbox?
Far fewer than the technical limit. Google Workspace permits 2,000 messages a day on paid accounts, but a realistic ceiling for cold outreach is 20 to 30 per inbox once established, starting at 5 to 10 during a three to four week ramp. Scale by adding inboxes, not by increasing volume per inbox.
Q8. What happens if I miss a few days during warm-up?
Short gaps are survivable but costly, because consistency is itself a reputation signal. SendGrid advises never going 30 days or more without sending on a given IP. If you miss several days mid-ramp, resume at the previous step's volume rather than where the schedule says you should be.
Every provider requirement, threshold and date in this article was verified against the sources below. Re-check them before publication if more than a quarter has passed, since mailbox provider rules continue to change.
 |
