the email sender IP warmup schedule that actually works
A week-by-week IP warmup schedule for email senders, with daily volume targets, monitoring benchmarks, and what to do when things go wrong.
You just provisioned a dedicated IP for sending email. The temptation is to start blasting. Resist it.
A new IP address has zero reputation with ISPs. Gmail, Outlook, Yahoo, and every other major provider treats unknown senders the way a bouncer treats someone without ID: you're not getting in until you prove you belong. An email sender IP warmup schedule is how you prove it, message by message, over several weeks.
This guide walks through a practical warmup plan, the benchmarks that tell you it's working, and what to do when ISPs push back. If you're building agents that send email and would rather skip managing IPs entirely, .
What IP warmup actually does#
Every IP address carries a reputation score that ISPs track independently. When your IP is new, that score is neutral. Not good, not bad. ISPs don't know if you're a legitimate sender or a spammer who just spun up fresh infrastructure to dodge blocklists.
Warmup is the process of sending small volumes of email from the new IP, then gradually increasing over time. Each batch of emails that gets opened, replied to, and not reported as spam builds your reputation. Each batch that bounces, gets flagged, or goes ignored chips away at it.
The math is straightforward: ISPs sample your early sends heavily. If you send 50 emails on day one and 48 land in the inbox with good engagement, that's a strong signal. If you send 5,000 on day one and 2,000 bounce because your list is stale, you've just told Gmail you're a spammer. Recovering from that takes weeks, sometimes months.
A week-by-week email sender IP warmup schedule#
Here's a schedule that works for most senders with clean lists and reasonable engagement. Adjust the starting volume down if your list hasn't been validated recently, or up if you have a track record with the same domain on a different IP.
| Day | Daily volume | Notes |
|---|---|---|
| 1–2 | 50 | Send only to your most engaged recipients |
| 3–4 | 100 | Monitor bounce rates after each batch |
| 5–7 | 250 | Check spam complaint rates (target: under 0.1%) |
| 8–10 | 500 | If bounces stay under 2%, proceed |
| 11–14 | 1,000 | Watch for throttling responses from major ISPs |
| 15–21 | 2,500 | You should see consistent inbox placement by now |
| 22–28 | 5,000 | Spread sends across the day, don't batch at once |
| 29–35 | 10,000 | Approaching full volume for most senders |
| 36–42 | 25,000 | Only if your list supports this volume |
| 43+ | Full volume | Maintain steady sending patterns going forward |
A few things about this schedule.
Start with your best recipients. Days 1 through 7 should go to people who have opened or clicked in the last 30 days. These recipients are most likely to engage, which sends positive signals to ISPs. Sending to your full list on day one is the single most common warmup mistake.
Don't skip days. ISPs track consistency. Sending 500 emails on Monday, zero on Tuesday, then 2,000 on Wednesday looks erratic and suspicious. Send every day during warmup, even if the volumes are small.
Spread sends across hours. Dumping 5,000 emails at 9:00 AM sharp triggers rate limiting at most providers. Space your sends across a 4 to 6 hour window minimum. Mailgun's own warmup tool caps Stage 1 at 1,000 per day and Stage 2 at 2,500 per day, which lines up roughly with weeks two and three of this schedule.
Benchmarks to watch during warmup#
Numbers matter more than instinct during this process. Track these four metrics daily.
Bounce rate should stay below 2%. Above 3% is a warning sign. Above 5% means you should stop sending and clean your list before continuing. Hard bounces (invalid addresses) damage reputation faster than soft bounces (full mailboxes, temporary failures). If your agent is hitting 550 denied by policy errors, that's a permanent rejection, and stacking those up during warmup can tank an IP in days.
Spam complaint rate needs to stay below 0.1%. That's one complaint per thousand emails. Gmail's Postmaster Tools will show you this metric directly. If complaints spike above 0.3%, pause warmup and investigate your content or list quality.
Open rate during warmup should be higher than your normal average because you're targeting engaged recipients first. If open rates drop below 15% during the first two weeks, either you're not targeting the right segment or your emails are landing in spam already.
Deferral rate is the percentage of emails that receive temporary 4xx responses from ISPs. Some deferrals are normal during warmup. ISPs use them to slow down unknown senders. If deferrals spike above 10%, reduce your daily volume by half and hold for a few days before ramping again.
What breaks a warmup (and how to recover)#
Three scenarios derail most warmup schedules.
The first is sending too much too fast. You jumped from 500 to 10,000 because things were going well. ISPs noticed. Your deferral rate spiked, some emails bounced, and now Gmail is throttling everything from your IP. The fix: drop back to the last volume that was working and hold for a full week before increasing again. Don't try to make up for lost time by sending more.
The second is bad list hygiene. You started warmup with an unvalidated list and hit a bunch of spam traps or dead addresses in the first week. Your bounce rate is sitting at 8% and your reputation is already damaged. The fix: stop sending immediately. Run your entire list through a verification service. Remove anything that bounced, any address older than six months without engagement, and any role-based addresses like info@ or support@. Restart warmup from day one with the clean list.
The third is inconsistent content. You warmed up with transactional emails (order confirmations, receipts) then switched to marketing newsletters at full volume. ISPs treat these as different sending patterns. If you send both types, warm up each one separately, and consider using separate IPs or subdomains for each category.
Why agents make IP warmup painful#
If you're building AI agents that send email, warmup creates a specific problem: agents don't send on predictable schedules.
A human marketer sends a newsletter every Tuesday at 10 AM. An agent sends when its task completes, which might be 3 emails on Monday, 47 on Wednesday, and zero on Thursday. This bursty pattern is exactly what ISPs flag as suspicious during warmup. We covered several related pitfalls in our breakdown of agent email setup mistakes.
Agents also tend to send to new recipients constantly rather than re-engaging a stable list. Every outbound email goes to someone who has never received mail from this IP before. ISPs weigh first-contact emails more heavily in reputation scoring because spam is almost always sent to people who didn't ask for it.
You can work around this by building send-rate limiting into your agent's logic, queuing messages and releasing them on a schedule that matches the warmup plan above. But that means your agent sits on completed tasks waiting for a send window, which defeats the purpose of automation.
The other option is using infrastructure where someone else has already done the warmup. Shared IP pools with established reputation let you send from day one without a ramp-up period. This is how services like LobsterMail, Postmark, and Mailgun's shared tier work. Your emails ride on IPs that have been sending clean mail for months or years. The tradeoff is that you share reputation with other senders on the pool, so one bad actor can affect everyone. Good providers mitigate this by monitoring senders and removing abusers quickly.
For most agents sending under a few thousand emails per day, a well-managed shared pool outperforms a freshly warmed dedicated IP. You skip the 6-week warmup, avoid the monitoring overhead, and your agent can send the moment it has something to say.
Tip
If your agent sends fewer than 500 emails per day, a dedicated IP almost never makes sense. The warmup timeline alone costs you six weeks of lost productivity, and low daily volumes don't generate enough signal to build strong IP reputation anyway.
If you're running an agent that needs email and don't want to spend six weeks nursing an IP, and your agent handles the rest in about 30 seconds.
Frequently asked questions
How long does a full IP warmup take?
Most warmup schedules run 4 to 8 weeks depending on your target daily volume. Senders aiming for under 5,000 emails per day can often finish in 3 to 4 weeks. Higher volumes need the full 6 to 8 week ramp.
Can I skip IP warmup if my domain already has good reputation?
Domain reputation and IP reputation are tracked separately by most ISPs. A strong domain helps your emails during warmup, but a brand-new IP still needs gradual volume increases. You'll likely progress faster, but you can't skip the process entirely.
What's the difference between dedicated and shared IP warmup?
Dedicated IPs start with zero reputation and require a full warmup schedule. Shared IPs already have established reputation from other senders on the pool, so you can send immediately. The tradeoff is that shared IPs tie your deliverability partly to other senders' behavior.
Do I need a warmup schedule for transactional email?
Yes. ISPs don't distinguish between transactional and marketing email at the IP level. If you're sending from a new IP, all email types need warmup. Some senders separate transactional and marketing traffic on different IPs and warm each independently.
What bounce rate is too high during warmup?
Keep bounces below 2%. Anything above 3% is a warning sign, and above 5% means you should pause, clean your list, and restart from day one. Hard bounces from invalid addresses hurt reputation faster than soft bounces.
How do I check my IP reputation during warmup?
Google Postmaster Tools shows reputation for Gmail. Sender Score at senderscore.org covers broader reputation. Talos Intelligence from Cisco and Microsoft SNDS cover Outlook. Check all of them since each ISP scores independently.
What happens if I send too many emails too early in warmup?
ISPs will start deferring your emails with 4xx responses or rejecting them outright with 5xx errors. Your reputation score drops, and recovering means reducing volume and holding steady for days or weeks. Following the schedule is always faster than rushing and recovering.
Does LobsterMail require IP warmup?
No. LobsterMail uses pre-warmed shared infrastructure, so your agent can send email immediately after creating an inbox. There's no warmup period, no DNS setup, and no reputation management required on your end.
Should I warm up a new subdomain alongside a new IP?
Yes. If you're using a new subdomain like mail.yourdomain.com that has never sent email, it needs reputation building at the same time as the IP. Domain warmup follows the same gradual ramp.
Can AI agents follow an IP warmup schedule on their own?
They can, but it requires building send-rate limiting and queue management into the agent's logic. The agent needs to throttle itself to match the schedule instead of sending whenever a task finishes. Most agent builders find pre-warmed infrastructure simpler than coding warmup logic from scratch.
What's the best day of the week to start IP warmup?
Tuesday or Wednesday. Mondays see high global email volume, which increases competition for inbox space. Friday engagement tends to drop over the weekend, making your early signals weaker. Midweek starts give you the strongest engagement data from your first sends.
Is LobsterMail free?
The Free tier costs $0 per month with no credit card required and includes up to 1,000 emails per month. The Builder tier at $9 per month adds up to 10 inboxes, 500 sends per day, and custom domain support.
