IP warmup explained: who needs it, who does not, and what a schedule actually looks like
Receivers trust a sending IP in proportion to what they have seen from it, and a new IP has no history. Warmup is the process of building that history without triggering the defences built for sudden senders. Most application senders should never do it, because it is a job for the infrastructure they send through.
IP warmup is sending gradually increasing volume from a new IP address so receivers can build a reputation for it before it sends at full rate. It matters for a dedicated IP that will carry tens of thousands of messages a day. A sender on an established shared pool does not warm anything, and a low-volume sender on a dedicated IP never accumulates enough history for the IP to be trusted at all.
Receiving mail servers trust a sending IP address in proportion to what they have seen from it. An IP that has sent well-received mail at a steady rate for a year gets the benefit of the doubt. An IP nobody has heard from is treated as what it most likely is: a freshly compromised machine, or a spammer who just moved. Warmup is the process of turning the second into the first without tripping the defences built for exactly that transition.
Most guides on the subject are written for senders with millions of messages a month and dedicated infrastructure. Most application senders are not that, and the first thing to know about warmup is whether it applies to you at all.
What reputation is attached to
Receivers score two things separately: the IP address the connection came from, and the domain the message claims to be from, as authenticated by DKIM and DMARC. Both start at zero for a new sender. Both are built by the same evidence: volume, consistency, complaint rate, bounce rate, and how recipients interact with the mail.
The two behave differently when you switch providers. A domain’s reputation follows you, because you take the domain with you. An IP’s reputation stays with the IP, because the IP belongs to whoever provides it. This is the fact that decides who needs to warm what.
Who needs IP warmup
A sender with a dedicated IP and real volume. If you are the only sender on an IP and you will be putting tens of thousands of messages a day through it, the IP’s history is entirely your history, and you have to build it from nothing. That is IP warmup, and there is no shortcut through it.
Who does not
A sender on a shared or provider-managed pool. The IPs already have history, built by everyone who sent through them before you. You inherit it on your first message. Your job is to not damage it, which is a different job from building it.
A low-volume sender on a dedicated IP. This is the case that surprises people. An IP that sends three hundred messages a day never accumulates enough evidence for receivers to form a strong opinion of it. It sits permanently in the “not much data” zone, which is treated with mild caution forever. For a sender under a few thousand messages a day, a dedicated IP is a worse position than a well-maintained shared one, and warming it does not change that. The volume is simply not there.
Anyone starting a new sending domain. You do not need IP warmup. You do need to understand that the domain is new, and the same gradual approach applies to it: consistent volume, engaged recipients, no sudden bursts. This is domain warmup, and it is the version of this problem that transactional senders actually meet.
What a schedule looks like
For a dedicated IP that will carry real volume, the shape is the same everywhere: start small, increase daily, watch the response, slow down when a receiver pushes back.
A representative ramp:
| Day | Messages per day | Notes |
|---|---|---|
| 1 | 200 | Your most engaged recipients only |
| 2 | 500 | |
| 3 | 1,000 | |
| 4 | 2,000 | |
| 5 | 5,000 | Hold here for two days if deferrals appear |
| 7 | 10,000 | |
| 10 | 25,000 | |
| 14 | 50,000 | |
| 21 | 100,000 |
The numbers are indicative, and the receivers differ. Some tolerate roughly doubling daily; others throttle harder and want a slower slope. The signals to watch, per receiving domain, are:
- Deferrals with
4.7.xcodes and text about rate or reputation. This is the receiver saying “slower”. Hold at the current volume for a day or two rather than pushing through. - Complaint rate. Warmup mail should go to your most engaged recipients precisely so this stays near zero. A complaint rate above 0.1% during warmup is a stop signal.
- Bounce rate. Sending to stale addresses during warmup teaches receivers that the new IP mails dead mailboxes. Clean the list first.
- Placement, where you can see it. Seed addresses at the major receivers tell you when mail starts landing in spam, which is the receiver’s judgement showing before it becomes a deferral.
Two rules that apply throughout. Send every day; a gap of several days partly resets the process, because consistency is part of the evidence. And send real mail, not test traffic: receivers score engagement, and a warm-up of messages nobody opens builds a reputation for sending mail nobody opens.
Why transactional mail is easier to warm
Transactional mail is the ideal warmup traffic, which is a small consolation for senders who have to do it. Every message goes to a person who caused it and is expecting it. Open rates are high, complaint rates are near zero, and the volume is naturally steady rather than campaign-shaped. A new IP carrying only receipts and password resets builds a reputation quickly, and a receiver looking at it sees exactly what it wants to see: a machine sending mail people want, at a rate that does not spike.
The corollary is the thing to avoid. Do not warm an IP with a marketing send. The complaint rate on a promotional campaign is normal for marketing and catastrophic for a new IP, and it teaches every receiver the wrong lesson about the address on day one.
Where Pharos fits
Pharos sends from IPs dedicated to Pharos, with history that predates your account, so a new sender does not warm an IP and does not start from zero on infrastructure. What you bring is the domain, and its reputation is yours to build the same way as anywhere: steady, expected, authenticated mail. Isolated IPs are available on request for senders whose volume justifies one, and a warmup plan is part of that conversation rather than something to work out afterwards.
Questions this raises
Do I need a dedicated IP?
Only at sustained volume, roughly 50,000 messages a day or more, and only if you are prepared to be the sole author of that IP's reputation. Below that, an IP sends too little for receivers to form a view, and a well-run shared pool with established history delivers better than a dedicated IP that is quiet most of the day.
Does a new domain need warming too?
Yes, and it is the warmup most application senders actually do, usually without noticing. Receivers track reputation per domain as well as per IP, and a domain with no history is treated with the same caution. Starting a new sending domain at modest, consistent volume to engaged recipients is domain warmup, and it takes a few weeks.
What happens if I skip warmup on a dedicated IP?
Receivers see a burst from an unknown source, which is what a compromised machine looks like, and respond with temporary deferrals, throttling, or spam placement. The damage is not permanent, but it costs weeks: you end up doing the warmup anyway, from a worse starting position.
Sources
Know when the rules change.
Gmail, Yahoo and Microsoft change what they require from senders. Pharos changes too — a capability, a limit, a price, something retired. Both change what you have to do to keep sending, so this list sends one email when either happens.
check your email
Confirm from the email we just sent, and you're on the list.