Warming up a dedicated IP
A brand-new sending IP has no reputation. Mailbox providers treat sudden volume from an unknown IP with suspicion, so you "warm" it — start small and ramp up gradually while keeping your mail clean. This guide covers how, and how to do it on BlacklistGuard.
Why warming matters
Providers like Gmail, Yahoo, and Outlook build a reputation for each sending IP based on the volume, consistency, and quality of its mail. An IP with no history that suddenly sends large volumes looks exactly like a spammer, so mail gets throttled, deferred, or filtered to spam. Warming establishes a track record of wanted mail before you send at full volume.
Before you start
- Authenticate first. Your sending domain must have SPF, DKIM, and DMARC in place — see Verify SPF, DKIM & DMARC. Warming an unauthenticated domain is wasted effort.
- Have engaged recipients. Warming works by sending to people who want your mail and will open it. If your list is old or unengaged, clean it (and consider validating it) first.
- Know your target volume. The ramp depends on where you're going — warming to 10,000/day looks different from warming to 1,000,000/day.
The principles
There's no single official warm-up schedule — the right pace depends on your volume and how engaged your recipients are. But the principles are consistent across mailbox-provider and industry guidance (Google, Yahoo, and M3AAWG):
- Start small, increase gradually. Begin with a low daily volume and raise it step by step, only as long as your metrics stay healthy.
- Send to your most engaged recipients first. Opens and clicks from real people are the positive signal that builds reputation. Save your least-engaged contacts for last.
- Be consistent. Send every day at a steady, predictable volume rather than in large irregular bursts. Providers reward consistency.
- Spread across providers. Warm Gmail, Yahoo, and Outlook addresses in roughly even proportion so you build reputation everywhere, not just one inbox.
- Watch and react. If bounces or complaints climb, hold volume steady (or pull back) until they settle before increasing again.
An example ramp
This is an illustrative schedule for warming toward a few hundred thousand messages a day — adjust the numbers to your own target and engagement. The shape matters more than the exact figures: small start, steady daily increases, full volume over several weeks.
| Week | Approx. daily volume | Audience |
|---|---|---|
| 1 | Hundreds → low thousands | Most engaged (opened in last 30–90 days) |
| 2 | Increase ~2× each step | Engaged |
| 3–4 | Continue ramping | Widen to regularly-active recipients |
| 4–8 | Approach full volume | Full list (engaged segments still first each send) |
Most providers want to see a few weeks of consistent, clean sending before they fully trust a new IP — plan for a 4–8 week ramp for substantial volumes, longer if you're going very large.
Doing it on BlacklistGuard
BlacklistGuard gives you the controls to warm at your own pace — there's no automatic warm-up curve, which means you stay in charge of the ramp:
- Throttle the IP. Set per-IP and per-domain sending throttles (messages per hour / per day) and raise them step by step as you progress through the ramp.
- Target engaged recipients. Use segments to send the early sends only to recipients who've opened or clicked recently.
- Route through the warming IP. Use a routing rule or Virtual MTA so the warm-up traffic goes out on the dedicated IP you're warming.
- Watch the numbers. Track delivery, bounces, and complaints on the Deliverability and Bounces & complaints reports as you go.
Metrics to watch
Healthy warming keeps these in range — if any spike, stop increasing and investigate before continuing:
- Bounce rate — keep it low (well under a couple of percent). High bounces mean list problems that will hurt the new IP.
- Spam-complaint rate — Google asks senders to stay under 0.30% and ideally below 0.10%. The same target is a good rule everywhere. Set up feedback loops so you actually see complaints.
- Deferrals / blocks — temporary 4xx deferrals during warming are normal as providers rate-limit a new IP; sustained blocks mean you're ramping too fast.