IP Warming: How to Build Sender Reputation on a New IP Address

IP warming is the process of gradually building a sending reputation on a new IP address before you use it for full-volume email. When an IP address is brand new — no sending history, no reputation — mailbox providers treat it with suspicion. Gmail, Yahoo, Microsoft, and others all assume that an unknown IP blasting out thousands of emails is probably a bad actor until proven otherwise. IP warming is how you prove otherwise, and skipping it is one of the most common reasons new senders hit immediate deliverability problems.

Why New IPs Need to Warm Up

Every IP address that sends email accumulates a reputation over time. Mailbox providers maintain internal scores based on factors like complaint rates, bounce rates, sending consistency, and authentication status. A brand-new IP has no score at all, which means it gets the benefit of the doubt at low volumes but triggers throttling and deferrals the moment it tries to send at scale.

This throttling manifests as 421 temporary deferral errors in your SMTP logs. The receiving server is essentially saying: I'll accept a little mail from you while I evaluate your behavior, but I'm not going to process high volume until you've demonstrated you're a legitimate sender. If you ignore the deferrals and keep hammering the server, you'll accelerate the reputation damage and risk a permanent block.

Building a Warming Schedule

A typical IP warming schedule for a dedicated sending IP looks something like this over the first four weeks:

• Week 1: 200–500 emails per day, sent to your most engaged recipients — people who have opened or clicked recently
• Week 2: 1,000–5,000 per day, expanding to active subscribers from the past 30–60 days
• Week 3: 10,000–25,000 per day, broadening to the past 90 days of engagement
• Week 4: 50,000–100,000+ per day, gradually incorporating older subscribers who still opted in

These are rough guides, not hard rules. The right pace depends on your list quality, your domain's existing reputation, and the volume targets you're working toward. The principle stays consistent: start small with your best recipients and scale only when you see clean delivery metrics — low bounce rates, negligible complaint rates, no throttling patterns emerging.

Warming With Engagement-First Sending

Sending to your most engaged subscribers first during warmup isn't just a reputation strategy — it's practical. Engaged recipients are more likely to open, less likely to complain, and more likely to move mail from spam to inbox if it lands there, which is a strong positive signal to filtering systems. Their behavior during the warmup period helps establish the baseline reputation that the IP will carry going forward.

Never warm an IP by blasting a purchased list or cold contacts. High bounce rates and spam complaints during the warmup period will kill your IP's reputation before it's even established. Once an IP develops a poor reputation early on, it's very difficult to recover — often it's easier to get a new IP and start fresh than to rehabilitate a badly warmed one.

Domain Warming vs IP Warming

Your IP and your domain each carry independent reputations. Warming your IP doesn't automatically mean your domain has a good reputation, and vice versa. If you're using a new sending domain alongside a new IP, you need to warm both simultaneously. The domain reputation signal is increasingly important — Gmail in particular places significant weight on the domain rather than just the sending IP.

If your domain is established and has a strong existing reputation, it can actually help smooth out the IP warming process. Mailbox providers see that the sending domain has a good track record even if the new IP is unknown, which often results in faster warm-up times and fewer deferrals in the early days.

Monitoring During Warmup

During IP warming, monitoring matters more than at any other time. Track your delivery rates, bounce rates, complaint rates, and deferral patterns daily. Key things to watch for:

• Bounce rates above 2% suggest list quality problems — slow down and clean your list before continuing
• Complaint rates above 0.08% suggest you're sending to disengaged recipients — tighten your engagement filters
• 421 deferral rates above 10% suggest you're sending too fast — drop your daily volume and let the queue work through backlogs naturally
• 554 hard rejections from a major ISP suggest a blocklisting event — pause sending to that ISP and investigate before continuing

SMTP logs are your best diagnostic tool during this phase. If your sending platform has a deliverability dashboard, review it daily. The data you collect during warmup is also valuable later — it gives you a baseline to compare against when deliverability issues come up months down the line.

Shared IP vs Dedicated IP Warming

If you're sending through a shared IP pool, your provider handles IP warming on your behalf — the pool's existing reputation means new senders on shared infrastructure can typically send at volume sooner. The tradeoff is that you share that reputation with every other sender on the pool.

On a dedicated IP, you control your own reputation entirely — but you're starting from zero. The warmup process described here applies to dedicated IPs specifically. For most senders, a dedicated IP makes sense once you're sending reliably above 50,000 emails per month and have the discipline to maintain the practices that keep its reputation strong.

If you're setting up new sending infrastructure, review MailDog's SMTP relay service for guidance on IP configuration and reputation management. The documentation covers how reputation is tracked and what metrics to watch. You can also reach out to MailDog support if you're managing a complex warmup scenario with multiple IPs or domains and need guidance on the right pacing strategy.