IP warming explained: schedules and best practice

IP warming is the practice of introducing new sending infrastructure gradually: starting with small volumes of your best mail to your most engaged recipients and growing daily sends over weeks, so mailbox providers can build a behavioural history before seeing scale. It exists because reputation systems treat unknown identities at high volume as the signature of a spam operation, and because there is no way to transfer history onto a fresh IP. The same logic applies to new domains and, during ESP migrations, to the new platform's entire sending path.

Why cold infrastructure gets filtered

Providers score reputation from history, and a new IP has none: no complaint baseline, no engagement record, no volume pattern. Compromised servers and snowshoe spam operations also appear as sudden high volume from fresh addresses, so filters respond to the pattern with deferrals, throttling, and spam foldering until evidence accumulates. Warming is not a trick to bypass this; it is cooperating with it, feeding the models the history they need at a pace they accept.

The shape of a warming plan

Warming, structurally

1
Authenticate before the first message
SPF, aligned DKIM, DMARC with reporting, forward-confirmed reverse DNS. A clean identity starts neutral instead of suspect.
2
Lead with your best mail
Transactional messages and the most engaged subscriber segments go first; their opens, clicks, and replies are the positive evidence being banked.
3
Grow volume on a curve, split by provider
Increase daily volume roughly 30 to 50 percent per step, distributing across Gmail, Microsoft, Yahoo and the rest, since each provider builds its own picture.
4
Throttle on pushback
4.7.x deferrals are the pacing signal: hold or reduce volume at the complaining provider until they clear, then resume. The schedule is a ceiling, not a quota.
5
Reach steady state, then stay consistent
Four to eight weeks typically lands full volume. Afterward, consistency is the maintenance: reputation systems keep modeling your normal.

What warming is not

Warming is volume ramping with real mail to real recipients. It is not the automated warmup services that exchange scripted messages and fake engagement between bot mailboxes: those patterns are fingerprintable, Google states plainly that third-party warmup does not improve reputation and can violate its policies, and the gains evaporate the moment real recipients enter the picture. If a plan involves synthetic opens or replies, it is not a warming plan.

Warming also cannot fix what it carries: a cold IP warmed with a stale list bakes complaints and bounces into the fresh identity, which is worse than no history at all. The list work precedes the infrastructure work, always.

When warming applies

New dedicated IPs, always. New sending domains and subdomains, yes, at the domain-reputation layer, even on warm IPs. ESP migrations, structurally: the new platform's IPs are cold even though your domain is not, which is why migrations run both platforms in parallel and shift volume gradually. Shared IP pools mostly exempt small senders, since the pool's existing history carries them, which is one honest argument for shared infrastructure below roughly 100k messages weekly. Returning from a long sending pause lands in between: reputation decays, and a domain quiet for months deserves an abbreviated re-warm rather than a full-volume restart.

Frequently asked questions

How long does warming take?

Four to eight weeks to full volume for most senders, driven by target volume and how providers respond. High-volume senders and Microsoft-heavy audiences sit at the long end. The deferral signals, not the calendar, set the real pace.

Can I speed it up if my domain reputation is excellent?

Somewhat at Gmail, where domain identity carries weight; barely at Microsoft, where the IP itself must earn trust. A strong domain shortens the suspicion phase, and skipping the ramp still produces deferrals.

What if I ignore warming and send full volume on day one?

Expect deferrals and spam foldering within days, followed by a slower climb out than the ramp would have cost: providers treat the spike as suspect and remember it. Warming is cheaper than recovering.

Do warming schedules from ESPs fit everyone?

They are reasonable templates keyed to volume tiers. Adapt them to your provider mix and let deferral behaviour override the printed numbers; the schedule that matters is the one the receivers are accepting.

Key takeaways

New IPs and domains start unknown, and unknown at volume reads as spam; warming builds the missing history
Authenticate first, lead with engaged recipients and transactional mail, grow 30 to 50 percent per step
Deferrals are the pacing signal: hold at the complaining provider, and expect Microsoft to be slowest
Synthetic engagement warmup services are not warming; real mail to real recipients is the only accepted evidence
Warming applies to new IPs, new domains, ESP migrations, and returns from long pauses, and cannot compensate for a bad list