IP Warming: Gradual Sending Explained

Mailbox providers treat a sudden flood of mail from an unfamiliar IP as suspicious. A spammer's pattern is to acquire an address and immediately blast at full volume, so providers learned to distrust exactly that behavior. Warming an IP means doing the opposite: start small, raise volume gradually, and let providers observe that recipients react well.

The goal of warmup is to build history. An IP with no track record is a blank slate that filters default to caution on. By sending modest, well received mail and increasing volume in measured steps, you give providers the data they need to assign a trustworthy reputation. Skip the warmup and you risk landing in spam or getting throttled from day one.

Warmup applies to genuinely new or dormant IPs. For cold email on real Google Workspace or Microsoft 365 mailboxes, the IP ranges are already trusted and provider managed, so the warmup focus shifts to your domains and mailboxes rather than the IP itself. This guide covers the IP ramp principles, which apply to both. For the domain side, see domain warmup best practices and the broader cold email warmup guide.

Warmup is a controlled ramp. You begin with a small daily volume, send to engaged recipients who open and reply, and increase the daily count in steady increments while watching the response. Each clean day adds to the IP's history and earns a little more trust, which lets you raise volume the next step.

The mechanics rest on three principles:

1. 1Start low. Begin well below your target volume so any early misstep is small and recoverable.
2. 2Increase gradually. Raise volume in measured steps, not jumps. A rough rule is to grow daily volume by a modest percentage each day rather than doubling.
3. 3Favor engagement. Mail that gets opened and replied to sends the strongest positive signal. Warmup networks simulate this with real inbox interactions.

Providers weight recent, consistent behavior, so the ramp must be steady. A gap or a spike resets trust and can force you to start over. The whole exercise is about teaching the filter that this IP behaves like a legitimate sender, one predictable day at a time. Validity's deliverability guidance reinforces that gradual, consistent ramping is the foundation of a stable sender reputation.

Below is a sample ramp for warming a new IP over roughly four weeks toward a moderate daily volume. Treat the numbers as a starting template, not a law. Adjust to your target volume and slow down at any sign of trouble.

The key is the shape of the curve, not the exact figures. Volume rises smoothly, with checkpoints to verify reputation before each big step. If a checkpoint shows trouble, you hold or step back rather than push forward.

For cold email, per mailbox limits keep daily volume far lower than these IP scale numbers, since cold sending spreads across many mailboxes. See our cold email sending volume limits guide and email sending limits for Google and Microsoft for the per mailbox ceilings that govern cold ramps.

Warmup is not fire and forget. You watch a handful of signals at each checkpoint and let them dictate whether you advance, hold, or pull back.

The rule is simple: green signals mean advance to the next step, yellow signals mean hold at the current volume until they clear, and red signals mean step back and diagnose. Pushing volume through warning signs is how warmups fail.

Microsoft's SNDS and Google's Postmaster Tools are your primary windows into how providers see the IP. Pair them with inbox placement tests so you catch spam foldering that the dashboards alone might not reveal. Our Google Postmaster Tools guide explains how to read each metric.

Most failed warmups come from a short list of avoidable errors. Knowing them up front saves weeks of lost progress.

The two most expensive mistakes are ramping too fast and letting volume gap. Both reset the trust you spent days building. Consistency beats speed every time. A slower ramp that never stumbles reaches full volume sooner than a fast ramp that crashes and restarts.

Authentication is a precondition, not a step. If SPF, DKIM, and DMARC are not in place before you start, the warmup is built on sand. Our DNS setup guide covers the records, and why cold emails go to spam connects these mistakes to inbox outcomes.

Doing all of this by hand across many mailboxes is tedious and error prone. You would have to schedule the ramp, generate engaged replies, watch the signals daily, and pull back the moment something slips, for every mailbox. That is why warmup is usually automated.

The quality of that automation depends heavily on the network behind it. Many warmup tools route interactions through a shared pool, where your mailboxes exchange warmup mail with strangers' mailboxes. If that pool contains low quality or abused accounts, the engagement signal is weak and the pool itself can carry risk.

InboxKit takes a different approach with an isolated warmup network rather than a shared pool. Your mailboxes warm within a controlled environment of real Google Workspace and Microsoft 365 accounts on US IPs, so the engagement signals are genuine and the network is not exposed to unknown senders. The ramp, the engagement, and the monitoring are handled for you, and InfraGuard checks blocklists every six hours, watches DNS, and auto pauses sending if it detects a problem during or after warmup.

The practical advice: whether you automate or warm by hand, respect the ramp, watch the signals, and never let volume gap. The schedule and the signals in this guide are the foundation. Automation just removes the manual labor of executing them consistently.