IP warming: a schedule that works and when you need one at all

A new IP has no sending history, so providers apply caution: they throttle, defer, and watch. IP warming is the process of establishing that history by sending a predictable, slowly increasing volume of mail that recipients want. It applies to a dedicated IP you control. If you send through a shared pool at a large ESP, you do not warm the IP — you warm your domain, and the pool's reputation is the provider's problem.

Decide whether you need a dedicated IP first

A dedicated IP is worth it when you have enough steady volume to keep it warm and you want your reputation isolated from other senders. It is actively worse than a shared pool when your volume is low or lumpy, because a mostly-idle IP looks dormant, and mail from a dormant IP gets treated as new again. The rule of thumb that holds up: if you cannot send a meaningful amount every single day, including the quiet weeks, stay in a well-run shared pool. The same logic applies to sending twice a quarter — a dedicated IP will make those two sends worse than a shared pool would.

A four-to-six week ramp

Volumes below are per day, per IP, assuming your recipients are engaged and your bounce rate is near zero. Split each day's send across providers in roughly the proportion your list has, and send at a steady rate rather than dumping the day's total in one burst.

Order recipients by recency of engagement and work outward. The first week should go to people who opened or clicked in the last 30 days; the segment that has not engaged in a year should be last, or never.

Let the SMTP responses set the pace

The schedule is a plan; the responses are the truth. Read them.

421 4.7.0 [IP] Our system has detected an unusual rate of unsolicited mail
     -> you are going too fast for this provider. Hold volume, retry later.
450 4.2.1 The user you are trying to contact is receiving mail too quickly
     -> recipient-side rate limit, usually harmless, keep the retry queue sane.
550 5.7.1 ... blocked using Spamhaus
     -> a hard block, not a pace problem. Stop, find the source, request review.

Persistent 4xx deferrals from one provider mean hold that provider's volume flat for a few days while the others continue. A 5xx block means stop increasing anything and investigate. Do not treat retries as progress: a high retry rate inflates your apparent volume while teaching the provider that your mail is unwanted.

What to watch, and what you can no longer watch

Track hard bounces (keep under 1%), complaint rate, deferral rate per provider, and inbox placement per provider from seed mailboxes. For IPs you own, Microsoft SNDS gives you per-IP complaint and trap data, which is the best free per-IP signal available. For Gmail, Postmaster Tools still gives you spam rate, authentication and delivery errors — but its IP and domain reputation charts have been retired, so there is no per-IP reputation grade to check any more. Spam rate under 0.3%, and ideally under 0.1%, plus seed placement, is the replacement.

What not to do

Do not warm an IP without authentication in place; SPF and DKIM must pass and align before the first send, or you are teaching providers about an unauthenticated stream. Do not warm several IPs at once with the same volume split across them — you get several half-warm IPs instead of one warm one. Do not pause for a week in the middle; a gap undoes more than it saves, and resuming at your previous volume looks like a spike. Do not start the ramp with a reactivation campaign to cold recipients, which is the single most common way a warm-up turns into a block. And do not warm an IP with traffic you generated for the purpose — mail nobody asked for, at volume, on a new IP, is the exact shape providers are looking for.

That last point now has a sharper edge for domains, which is where most synthetic warming happens. Validity launched the Heatwave blocklist on 3 September 2026 targeting synthetic reputation warming: pools of controlled mailboxes manufacturing opens, clicks and replies. It lists domains rather than IPs, launched with over a million of them, and feeds live filtering, with lookup at lookup.validity.tools and reviews via its /delist path. Ramping real mail is defensible; fabricating interaction is the thing under scrutiny, and nobody outside Validity knows where the thresholds sit.

After the ramp

Keep volume steady, keep the list clean, and expect to re-warm if you go quiet for several weeks or move to a new IP. Reputation is attached to behaviour over time, so the maintenance is just the ramp's last row repeated.

MailPilot handles the mailbox and domain side of this rather than the MTA side: it warms mailboxes over OAuth or SMTP/IMAP including Amazon SES, SendGrid, Mailgun and Postmark, measures real per-provider inbox placement so you can see which provider is throttling you, and tracks per-mailbox reputation daily alongside SPF, DKIM and DMARC checks.