- IP warming, defined
- IP warming is the scheduled increase of sending volume from a new IP address, giving receiving providers time to build a reputation for it instead of meeting an unexplained surge.
A workable schedule starts near 50 messages a day, doubles roughly weekly, and reaches full volume over four to eight weeks. Split the daily total across providers in proportion to your list.
Order your recipients by engagement and send to the top first. Openers and repliers produce the positive signals this whole exercise exists to generate.
Watch bounce and complaint rates between steps and treat them as a brake. Crossing 0.3% complaints during warming is a reason to stop and investigate rather than continue.
Domain warming follows the same logic on a different axis, and at Gmail it is the more important of the two. A new IP under an established domain warms considerably faster than both being new at once.
How ZapBounce reports it
A warming schedule is only as good as the list under it, so verify before the first day rather than after week three. Bounces during warming carry more weight than at any other time, because there is no history to absorb them.
Splitting each day's volume by mailbox provider
Reputation is kept separately by each mailbox provider, so a warming plan is really several plans running side by side. Say your target is 30,000 messages a day and your list is 52% Gmail, 24% Microsoft, 9% Yahoo and 15% everyone else.
On a day when the schedule allows 800 sends, that's about 416 to Gmail, 192 to Microsoft, 72 to Yahoo and 120 to the rest. Keeping the mix proportional matters. If your most engaged segment happens to be 90% Gmail, sending only to them warms Gmail nicely and leaves Microsoft seeing a brand-new IP in week five, at full volume.
Build each day's send by picking the most engaged recipients within each provider, in those proportions. It takes a bit more segment work up front, and it means every provider sees the same gradual curve.
What a provider sounds like when it wants you to slow down
Providers tell you when you're going too fast. The message arrives as a temporary 4xx deferral, and your platform's logs will show it.
Gmail's typically reads 421 4.7.28 with text about an unusual rate of mail from your IP. Outlook's consumer service uses 421 RP-001, saying the connecting IP has exceeded its rate limit. Yahoo sends 421 4.7.0 [TSS04], telling you messages are temporarily deferred due to unexpected volume or user complaints.
A handful of these on a given day is normal during warming, and your platform will retry and get through. Treat a rising share as the brake. If more than a few percent of attempts to one provider are being deferred, hold that provider at the current volume for several days, or step down one level, while the others continue on schedule.
Don't respond by retrying faster. Hammering a server that has asked you to wait is the behavior the limit exists to catch.
IP warming: common questions
What does a warming schedule look like?
Around 50 messages on day one, roughly doubling each week, reaching target volume over four to eight weeks.
Who should receive warming sends?
Your most engaged subscribers, in order. The exercise records their behavior, so start with the people who reply.
What if metrics worsen mid-warming?
Hold volume or step back until they recover. Continuing to plan through rising complaints defeats the purpose.