How to Warm Up a Dedicated IP Address for Email

Learning how to warm up a dedicated IP address comes down to one thing: earning the trust of each mailbox provider before you push real volume through an IP that has no history. A brand-new dedicated IP starts with a neutral-to-cold reputation. Send too much too fast, and Gmail, Outlook.com or Yahoo will throttle, defer or block you.

The idea that trips people up is that reputation is not global. It accrues separately at each receiving provider. So you do not run one warmup — you run a parallel ramp against every destination that matters, and you read each provider's feedback on its own terms.

This guide covers the ramp itself, how the big providers differ, how to read deferrals, and the cutover problem most guides skip: moving your existing sending volume onto the new IP without stranding the reputation you already built.

The short answer#

Start small and grow slowly. On day one, send a modest volume — often a few hundred to a couple of thousand messages — to your most engaged, most recent recipients. Increase the daily volume in steps, roughly doubling every day or two, and watch each provider's response before you push higher.

There is no single official schedule. Google's own guidance is qualitative: start with a low sending volume to engaged users and slowly increase it over time, and avoid sudden volume spikes. The exact numbers depend on your target volume and how each provider reacts.

A full warmup commonly takes about four to eight weeks to reach a high steady-state volume. It ends not on a calendar date but when you can send your target daily volume to a provider without deferrals climbing and without your spam-complaint rate rising.

Before you start#

Warmup fails fastest when the fundamentals are missing. Fix these before you send a single message — a cold IP has no reputation to absorb a mistake.

• Authentication in place. SPF, DKIM and DMARC must be set up and aligned for the sending domain. Yahoo requires both SPF and DKIM for bulk senders plus a DMARC policy of at least p=none; Microsoft enforces SPF, DKIM and DMARC for domains sending over 5,000 messages a day.
• Postmaster visibility. Enrol the domain in Google Postmaster Tools and Microsoft SNDS so you can watch reputation, deferrals and spam rate per provider as you ramp.
• A clean, engaged list. Warm on people who open and reply. Suppress old, unverified and role addresses — a new IP cannot afford bounces or complaints.
• One-click unsubscribe. Marketing mail to Gmail, Yahoo and Apple must carry a working one-click unsubscribe header (RFC 8058). Missing it is now a compliance failure, not a nicety.
• A defined target volume. Know the daily volume you are ramping toward; it sets how long the ramp takes and how aggressive each step can be.

How to warm up the IP, step by step#

The procedure is the same for every provider. What changes is how fast each one lets you grow, which is why you watch them separately as you go.

1. 1

   Split your audience by engagement

   Rank recipients by recency and engagement. Warmup mail goes to the most engaged first — people who opened or clicked in the last 30 to 90 days. They generate the opens and replies that build positive reputation and rarely complain.

2. 2

   Send a small first-day volume

   Begin with a low volume spread evenly through the day, not in one burst. Google's guidance is explicit: send at a consistent rate and avoid sending in bursts. A burst from a cold IP looks like a spam cannon.

3. 3

   Increase gradually, and per provider

   Roughly double the daily volume every day or two, but read each provider on its own. If Gmail is accepting cleanly while Outlook.com is deferring, hold the Outlook.com portion and keep growing the rest.

4. 4

   Watch the metrics that matter

   Track deferral (4xx) rate, bounce rate and spam-complaint rate per provider in Postmaster Tools and SNDS. Keep the Gmail spam rate below 0.10% and never let it reach 0.30%; keep Yahoo complaints below 0.3%.

5. 5

   Hold or step back when signals turn

   A rising deferral or complaint rate at one provider means you are moving too fast for that provider. Hold that day's volume, or drop back a step, until the signal clears — then resume the ramp.

6. 6

   Reach and hold steady state

   When you can send your target daily volume to each provider without deferrals climbing, the IP is warm. Keep sending consistently — a warm IP that goes quiet for weeks cools off and needs re-warming.

Moving existing volume onto the new IP#

Here is the part most guides skip. If you already send from another IP — a shared pool or an old dedicated IP — you cannot just flip a switch. Reputation does not transfer between IPs. The new IP starts cold no matter how good the old one's standing is.

So run both in parallel. Keep sending your established volume from the old IP, and layer the new IP's warmup on top. Each day, shift a growing slice of traffic to the new IP as it earns capacity, while the old IP carries the rest. Only when the new IP is fully warm do you retire the old one.

Should you split traffic during warming? Yes — that is the mechanism. Split by percentage (move 5%, then 10%, then 25% of volume to the new IP), or split by provider so you can ramp Gmail and Outlook.com at their own pace. The point is that no provider ever sees a sudden jump.

How Gmail, Outlook.com and Yahoo differ#

Each provider runs its own reputation system and its own bulk-sender rules. Warm against all of them at once, but expect different thresholds and different feedback. The table below reflects each provider's published guidance as of August 2026 — verify against the live postmaster page before you rely on a number.

What deferrals mean, and what to do when it stalls#

A deferral is a temporary rejection — an SMTP 4xx response such as 421 or 452 that means 'not now, try again later.' During warmup, deferrals are normal and even useful: they are the provider throttling an IP it does not yet trust. Your mail server retries them on its own.

Treat the deferral rate as your throttle signal. A low, steady level is fine. A sharp rise from one provider means you pushed that provider's volume up faster than its trust is growing. Hold or drop back that provider's volume until retries clear, then resume.

A 5xx response is different. That is a permanent rejection — a hard bounce or an outright block — and it points to a reputation or authentication problem, not a pace problem. Stop increasing volume, check your spam rate and authentication, and fix the cause before you send more.

• Spam rate climbing toward 0.10% at Gmail: pause the ramp, tighten to your most engaged recipients, and let the rate recover before growing again.
• Deferrals from one provider only: hold that provider's volume and keep ramping the others — reputation is per-destination.
• A sudden block right after a volume jump: you spiked. Drop back to the last volume the provider accepted cleanly, then grow more slowly.

A faster way — and where AI Emaily does and does not fit#

The genuinely faster way to warm a dedicated IP is not to do it by hand. Established sending platforms — Amazon SES, SendGrid, Postmark, Mailgun and others — provide dedicated IPs and, in several cases, automate the ramp for you, pacing volume against each provider's limits so you do not babysit the schedule. If you send real bulk volume, that is where this job belongs.

We build AI Emaily, and we will be plain about the boundary: it is an AI-native email client, not an email service provider. It does not send campaigns, does not warm sending IPs, and cannot change your sending reputation — no client can. If you are warming an IP, use the platforms above, not us.

What AI Emaily does is the other side of the same inbox: the mail that arrives. It triages, drafts replies in a voice you configure, and its spam protection filters junk and cold outreach so the inbox you monitor stays manageable. That is the adjacent job — the receiving side — and it is the only claim we make on this page.