# How to Warm Up a New Sending IP: Schedule, Signals, Mistakes

> A practical IP warm-up guide: how to ramp volume on a new sending IP, which signals to watch at each mailbox provider, and the mistakes that reset reputation.

Source: https://pidgely.com/blog/ip-warmup-guide/ · Published: 2026-10-12 · Pidgely

IP warm-up is the process of gradually increasing the volume sent from a new IP address so mailbox providers can build a reputation for it from positive signals. Start with a small daily volume sent only to your most engaged recipients, increase it step by step (often doubling every day or two) while watching deferrals, bounces and complaints per provider, and slow down whenever a receiver pushes back. A typical warm-up takes from a few weeks to more than a month, depending on your target volume.

## Why new IPs need warming

Mailbox providers such as Gmail, Yahoo and Microsoft score every sending IP. A brand-new IP has no history, and a sudden burst of traffic from an unknown address is exactly what a compromised server or a snowshoe spam operation looks like. Receivers respond with throttling (`421` deferrals), spam folder placement or blocks.

Warm-up gives them a steady, predictable stream of mail that people open, reply to and do not report, so the IP accumulates positive reputation before it carries full volume. M3AAWG's sender best practices describe the same principle: ramp volume gradually and prioritize engaged recipients.

Note that domain reputation now matters as much as IP reputation, especially at Gmail. A warm IP will not save mail from a domain with a poor history, and a good domain helps a new IP warm faster.

## Before you send the first message

Get the fundamentals right first, because warm-up amplifies whatever you start with.

- **Reverse DNS**: the IP has a PTR record pointing to a hostname that resolves back to it, for example `mta1.example.com`.
- **Authentication**: SPF, DKIM with your domain and a DMARC record are live and aligned.
- **TLS**: your MTA offers STARTTLS on outbound connections.
- **Feedback loops**: register for Yahoo's complaint feedback loop and Microsoft's JMRP/SNDS, and verify your domain in Google Postmaster Tools.
- **Bounce processing**: hard bounces are suppressed immediately, before the second send.
- **Clean list**: remove addresses that have not engaged in a long time. Old lists are where spam traps live.

## A sample warm-up schedule

There is no universal schedule, and published ones vary widely. The table below is a conservative starting point for one IP, measured as messages per day **per major provider** (Gmail, Microsoft, Yahoo each counted separately):

| Day | Messages per provider per day |
| --- | --- |
| 1-2 | 50-100 |
| 3-4 | 200-300 |
| 5-6 | 500-750 |
| 7-8 | 1,000-1,500 |
| 9-11 | 2,500-4,000 |
| 12-14 | 6,000-10,000 |
| 15-21 | 15,000-40,000 |
| 22+ | Increase toward target while signals stay clean |

Two rules matter more than the exact numbers:

1. **Ramp per provider, not globally.** If 60% of your list is on Gmail, Gmail sees most of your traffic. Each receiver builds its own opinion.
2. **Let the signals set the pace.** If a step produces deferrals or a jump in complaints, hold at that level, or step back, for a few days.

Send consistently every day. A schedule that sends 5,000 on Monday and nothing until Thursday looks less trustworthy than a steady daily flow.

## What to send

Order your audience by engagement and start at the top:

1. **Transactional mail** (receipts, notifications, password resets): expected and rarely reported.
2. **Recent openers and clickers** of your marketing mail.
3. **Recently registered users.**
4. Everyone else, only once the IP is established.

If you migrate from another provider, you can move streams gradually: route a percentage of each campaign to the new IP and increase it daily, keeping the old IP for the rest.

## Signals to watch

### SMTP responses

Your MTA logs are the earliest signal, often hours before any dashboard updates. Group responses by receiving domain and enhanced status code:

```text
421 4.7.0 [TSS04] Messages from 203.0.113.10 temporarily deferred due to unexpected volume or user complaints
421 4.7.28 Our system has detected an unusual rate of unsolicited mail originating from your IP address
451 4.7.650 The mail server [203.0.113.10] has been temporarily rate limited due to IP reputation
550 5.7.1 Service unavailable, Client host [203.0.113.10] blocked using Spamhaus
```

Deferrals (`4xx`) mean "slow down"; block-list rejections (`5xx` naming a list) mean "stop and investigate".

### Provider dashboards

- **Google Postmaster Tools**: IP reputation, domain reputation, spam rate. According to Google's sender guidelines, keep the spam rate below 0.1% and never reach 0.3%.
- **Microsoft SNDS**: per-IP traffic color (green, yellow, red) and trap hits.
- **Feedback loop complaints**: any complaint during warm-up deserves a look at what was sent and to whom.

### Your own metrics

- Hard bounce rate per send (a high rate means a stale list).
- Open and click rates by provider (a sudden drop at one provider often means spam folder placement).
- Time-to-deliver (rising queue age means throttling).

## Common mistakes

- **Sending a full campaign on day one** because "the IP is ready". It is configured, not trusted.
- **Using warm-up to clear an old list.** Spam traps and invalid addresses hit hardest when reputation is thinnest.
- **Retrying deferrals aggressively.** Hammering a server that returned `421` with immediate retries makes throttling worse. Use exponential backoff.
- **Treating deferrals as bounces** and suppressing valid addresses.
- **Ramping globally instead of per provider**, so one dominant provider gets overloaded.
- **Too many IPs for the volume.** Spreading 50,000 messages a day across ten IPs means none of them sends enough to build a stable reputation.
- **Going quiet after warm-up.** Inconsistent volume erodes the reputation you just built.

## Warm-up checklist

- [ ] PTR, SPF, DKIM and DMARC verified
- [ ] Postmaster Tools, SNDS and feedback loops registered
- [ ] Hard-bounce suppression active
- [ ] Audience segmented by engagement
- [ ] Per-provider daily caps configured
- [ ] Deferral rate, bounces and complaints reviewed daily
- [ ] Volume held or reduced at the first sign of pushback

Pidgely assigns IP pools per stream and ramps new IPs automatically, capping per-provider volume and backing off on deferrals, so you do not have to maintain a warm-up spreadsheet by hand.

## Frequently asked questions

### How long does IP warm-up take?

Typically several weeks, depending on target volume and engagement. A low-volume sender may be fully warm in two to four weeks, while senders targeting millions of messages per day often need six weeks or more.

### What should I send during warm-up?

Your best mail to your most engaged recipients: transactional messages and campaigns to people who opened or clicked recently. Avoid old lists, reactivation campaigns and cold addresses.

### What do I do if I get 421 deferrals during warm-up?

Slow down. A 4xx deferral is the receiver telling you it is not yet ready to accept that rate. Hold or reduce volume at that provider, keep retrying deferred messages with backoff, and resume increasing only when deferrals subside.

### Do I need to warm up a shared IP?

No. Shared IPs already carry traffic and reputation from other senders. Warm-up applies to new dedicated IPs and, to a lesser degree, to new sending domains.

### Can an IP go cold again?

Yes. Mailbox providers have limited memory of an IP's history. After weeks of inactivity, treat the IP as partially cold and ramp up again rather than resuming full volume.