How to Warm Up a New IP Address for Email Sending

Buy a fresh IP, point it at a hundred thousand recipients on day one, and you will burn it within hours. Mailbox providers treat sudden volume from an unknown source as a hostile signal. IP warmup is the gradual process of teaching the major receivers that you are a legitimate, well-behaved sender.

What an IP reputation actually is

Each major mailbox provider keeps a running score for every sending IP that ever connects to it. The score is built from a long list of signals:

• Volume sent over time, day-by-day and hour-by-hour.
• Bounce rate (especially hard bounces).
• Complaint rate (recipients clicking "this is spam").
• Spam-trap hits (mailing addresses the receiver has set up specifically to detect bad list practice).
• Engagement — opens, clicks, replies.
• Authentication — SPF, DKIM, DMARC results.
• Volume consistency — sudden spikes or sudden silences are both suspicious.

A new IP starts with no score. Some receivers treat that as neutral; most treat it as slightly negative, on the principle that legitimate senders have history.

Why warmup works

By starting at low volume and ramping deliberately, you:

• Give receivers a chance to observe your behaviour before you matter to them.
• Demonstrate consistent volume over weeks rather than days.
• Build engagement signal from your most engaged recipients first.
• Spot reputation problems early, when the damage is small and fixable.

Before you start: prerequisites

None of this matters if the basics are wrong. Verify all of these are in place before sending the first message from your new IP:

1. Forward-confirmed reverse DNS — see our PTR guide.
2. The PTR matches the EHLO hostname.
3. SPF record includes the new IP.
4. DKIM is signing every outbound message with your domain.
5. DMARC is published, even at p=none.
6. You're not on any major DNSBL (the IP is fresh; it shouldn't be, but check).
7. Bounce processing is in place — you must be able to suppress hard bounces immediately.
8. Feedback loops enrolled with Microsoft (JMRP), Yahoo (CFL) and any other receiver that supports them.

The 30-day warmup schedule

This is the schedule we use for new transactional IPs, scaled to a target of around 100,000 messages per day per IP. Adjust the absolute numbers to your target.

Days 1–3: introduction

• Send 50 to 100 messages per day.
• To your most engaged recipients only — people who have opened or clicked in the last 30 days.
• Spread the volume across the major receivers in roughly the proportions of your list (e.g. 60% Gmail, 25% Outlook, 10% Yahoo, 5% other).
• Pace at one message every few seconds, not bursts.

Days 4–7: doubling

• Roughly double the daily volume each day: 200, 400, 800, 1,500.
• Still engaged recipients only.
• Watch bounce and complaint rates daily — a sudden spike means stop and investigate before continuing.

Days 8–14: building

• Continue doubling until you hit about 25% of your target volume.
• Start including moderately-engaged recipients (opened in last 90 days).
• Begin checking Google Postmaster Tools and Microsoft SNDS daily — you should start seeing data after about a week.

Days 15–21: ramping

• Push to 50% then 75% of target volume.
• Include dormant recipients carefully — this is when most warmups go wrong, because the dormant cohort has the highest bounce and complaint rate.
• Throttle by destination domain — a per-receiver cap prevents one mailbox provider's bad day from affecting the others.

Days 22–30: full volume

• Reach 100% of target by day 30.
• Sustain that volume daily for at least another two weeks before declaring the warmup complete.
• Continue monitoring — reputation can decay quickly if a campaign goes wrong.

The metrics to watch every day

• Hard bounce rate. Should stay below 2%. Above 5% = stop and investigate. Above 10% = burn risk.
• Complaint rate. Below 0.1% is safe. Above 0.3% triggers the Gmail/Yahoo bulk-sender threshold and your reputation collapses.
• Per-receiver delivery rate. If Gmail drops to 80% delivered while Outlook is at 99%, you have a Gmail-specific problem.
• Spam folder placement. Use a seed-list service (GlockApps, Inboxally) to track which percentage of your sends land in inbox vs spam at each receiver.
• Postmaster Tools data. IP and domain reputation panels at Google and SNDS at Microsoft.

What to do when something goes wrong

The bounce rate spikes

Stop the warmup immediately. Identify the bounce reason — usually a stale segment that you mistakenly included. Suppress the bouncing addresses, wait 48 hours, then resume at the previous day's volume rather than continuing the ramp.

One receiver starts blocking

Check the SMTP rejection reason. If it's reputational (4.7.x or 5.7.x), that receiver has decided your IP is suspicious. Two options: pause sending to that receiver while continuing elsewhere, or contact the receiver's postmaster team directly. Microsoft and Yahoo both have well-documented enrolment processes; Gmail does not.

You hit a spam trap

If you suddenly find yourself on Spamhaus, you almost certainly hit one of their spam traps. The fix is list hygiene — remove any address you can't prove engaged with you in the last 90 days. Then submit a delisting request and wait.

Domain warmup: the often-forgotten counterpart

If your sending domain is new (not just the IP), you need to warm both at the same time. Domain reputation is increasingly weighted by Gmail and Yahoo over IP reputation, because IPs change but domains don't. Practical implication: if you're moving from one ESP to another while keeping the same sending domain, you can warm faster than if you're starting from scratch on both.

Multiple-IP warmup

If you're warming up multiple IPs at once (for a pool), the simplest approach is to run all of them through the same warmup schedule in parallel, distributing volume evenly across the pool. This actually warms each IP slower than warming one at a time, but it builds the whole pool to production capacity together.

How long until you can stop being careful?

Realistically, an IP needs three months of consistent, healthy sending before its reputation is robust enough to absorb a bad day without major disruption. Even after that, big volume changes (a 10x spike for a holiday campaign) require you to slow back down. Reputation is something you maintain forever, not a problem you solve once.

For more on the broader picture, see our complete deliverability guide and our walkthrough of Google Postmaster Tools.