How to Warm Up a New Email IP and Domain: My 6-Week Production Schedule

Every email guide tells you to "warm up your IPs." Almost none of them tell you exactly how. They say "start slow and gradually increase" — but how slow? How gradual? What does "gradually" look like in an actual PowerMTA config file?

I've warmed up dozens of IPs and domains for high-volume email infrastructure. Some went perfectly. Some got me blacklisted within 72 hours because I moved too fast or made a rookie mistake. This guide is the result of all those experiments — the exact 6-week schedule I now follow for every new IP and domain, with real config snippets and the monitoring checkpoints I use to know when it's safe to increase volume.

1. What Is Email Warmup and Why It Matters in 2026

Email warmup is the process of gradually increasing the volume of emails sent from a new IP address or domain to build a positive sender reputation with ISPs (Internet Service Providers) like Gmail, Yahoo, and Outlook.

Why does this matter? Every IP address starts with zero reputation. ISPs don't know if you're a legitimate business or a spammer. They make this decision based on your sending behavior during the first few weeks. If you blast 50,000 emails from a brand-new IP on day one, the answer is obvious to them: you're a spammer.

In 2026, warmup is more critical than ever because:

• Google and Yahoo enforce strict sender requirements — bulk senders (5,000+ emails/day) must have SPF, DKIM, DMARC alignment, one-click unsubscribe, and spam complaint rates below 0.1%
• AI-powered spam filters now analyze sending patterns, engagement signals, and volume ramps in real-time — not just content
• Microsoft Outlook has become significantly stricter, throttling or blocking senders with no established reputation
• Shared blacklists propagate faster — one mistake can get you listed on 10+ DNSBLs within hours

2. IP Warmup vs Domain Warmup — What's the Difference?

This is a distinction that most guides completely ignore, and it's cost me deliverability more than once. There are two separate reputations you need to build:

The critical insight: A warmed IP with a cold domain will still land in spam. A warmed domain on a cold IP will get throttled. You must warm both simultaneously. In my setup, I always register new sending domains at least 2-4 weeks before I even start sending from them — this gives the domain age, which ISPs factor into reputation scoring.

3. Prerequisites Before You Start Warming Up

Before you send your first warmup email, every one of these must be in place. Missing even one will undermine your entire warmup:

DNS Authentication (Non-Negotiable)

• SPF Record: Lists your sending IP as authorized for your domain. Keep it under the 10 DNS lookup limit.
• DKIM Signing: 2048-bit RSA key, configured in PowerMTA's domain directive. See my DKIM setup guide.
• DMARC Policy: Start with p=none during warmup to collect data. Move to p=quarantine once you're confident all legitimate mail is authenticated.

Infrastructure Checklist

• Reverse DNS (PTR): Every sending IP must have a PTR record pointing to your mail hostname. Without this, Gmail and Yahoo reject at the SMTP handshake.
• Dedicated warmup vMTA: In PowerMTA, I create a separate Virtual MTA specifically for warmup traffic with conservative rate limits. See my vMTA config.
• Clean seed list: Your first warmup emails should go to addresses you know are valid — team members, personal accounts, engaged subscribers. Never start warmup with a cold list.
• Bounce processing: Your bounce handling must be active from day one. A single unprocessed hard bounce during warmup is far more damaging than one during normal production.

4. My 6-Week IP Warmup Schedule

This is the exact schedule I follow for every new dedicated IP. The daily volumes assume you're sending to a mix of ISPs (Gmail, Yahoo, Outlook, corporate). If you're sending primarily to one ISP (like Gmail), reduce these numbers by 30-40%.

5. Warmup Progression Phases

Here's how I think about the warmup process — not as a linear schedule, but as four distinct phases, each with a specific goal and graduation criteria:

Phase 1 — Foundation (Days 1-7): The goal is simply to prove you're a legitimate sender. Send only to addresses you control or that you know will engage. Every open, reply, and "not spam" click during this phase trains ISP filters that your IP is trustworthy.

Phase 2 — Ramp (Days 8-21): Gradually expand to your broader subscriber base. This is where per-ISP throttling becomes critical — Gmail has different tolerance thresholds than Yahoo. Monitor delivery rates per ISP, not just overall.

Phase 3 — Scale (Days 22-35): You can begin introducing cold outreach in small batches alongside your warm traffic. The warm traffic acts as a "reputation anchor" — its high engagement signals offset the lower engagement of cold emails.

Phase 4 — Production (Days 36+): Your IP should now have a "High" reputation in Google Postmaster Tools. You can operate at full production volume, but continue monitoring daily. Reputation can drop at any time if list hygiene slips.

6. How I Configure Warmup in PowerMTA

Here's the actual PowerMTA configuration I use for a warmup vMTA. The key is the max-msg-rate directive — I manually update it as I progress through the warmup schedule:

# /etc/pmta/config — Warmup vMTA Configuration

# ============================================
# vMTA: Warmup (New IP being warmed)
# ============================================
<virtual-mta mta-warmup>
    smtp-source-host 192.168.1.12 mail-wu.yourdomain.com

    # WEEK 1: Foundation phase
    <domain *>
        max-smtp-out          3         # Very few simultaneous connections
        max-msg-per-connection 5
        max-msg-rate           5/h      # Start at 5 emails per hour
        smtp-greeting-delay    1s       # Slow, natural-looking delivery
        retry-after            30m
        bounce-after           3d
        max-errors-per-connection 2
    </domain>

    # Gmail — Extra conservative during warmup
    <domain gmail.com>
        max-smtp-out          2
        max-msg-per-connection 3
        max-msg-rate           2/h      # Only 2/hour to Gmail initially
    </domain>

    # Outlook — Also very conservative
    <domain outlook.com>
        max-smtp-out          2
        max-msg-per-connection 3
        max-msg-rate           2/h
    </domain>
</virtual-mta>

As I progress through each phase, I update the max-msg-rate:

After each config change, I reload PowerMTA without restarting to apply the new rates:

# Apply config changes without dropping active connections
sudo pmta reload

# Verify the new rates are active
pmta show vmtas

7. Domain Warmup: The Strategy Most Guides Miss

Most warmup guides focus exclusively on IP warmup. But in 2026, domain reputation is equally important — and in some cases, more important. Google Postmaster Tools tracks reputation at the domain level, not the IP level.

My Domain Warmup Strategy

1. Register the domain 2-4 weeks early. Domain age is a ranking factor. A 30-day-old domain with active DNS records is far more trusted than one registered yesterday.
2. Set up DNS immediately. As soon as you register, add SPF, DKIM (publish the public key), and DMARC records. Even before you send a single email, having these records active starts building your domain's identity.
3. Use a "cousin" domain. Never use your primary business domain for cold outreach. Register a related domain (e.g., getbrand.com instead of brand.com). If the outreach domain gets blacklisted, your main domain stays clean.
4. Start domain warmup alongside IP warmup. Your first warmup emails should use the new domain as the From address, sent through the new IP. This warms both simultaneously.
5. Monitor domain reputation separately. Use Google Postmaster Tools to track your domain's reputation independently from your IP reputation. They can diverge — a strong IP with a weak domain still lands in spam.

Domain Types to Avoid for Cold Outreach

8. How I Monitor Warmup Progress

During warmup, I check these tools and metrics every single day. The moment any metric goes red, I pause and investigate before sending another email.

Google Postmaster Tools (Primary)

This is the single most important monitoring tool during warmup. Here's what I look for:

• Domain Reputation: Should progress from "N/A" → "Low" → "Medium" → "High" over the 6-week period. If it drops from Medium to Low, immediately reduce volume by 50%.
• Spam Rate: Must stay below 0.1%. If it hits 0.3%, stop all campaigns and investigate.
• Authentication: SPF, DKIM, and DMARC pass rates should all be 100%. Any failure means a DNS misconfiguration — fix immediately.
• Delivery Errors: Track the rate of "Rate limited" and "Suspected spam" errors. A spike during warmup means you're increasing volume too fast.

Key Metrics I Track Daily During Warmup

PowerMTA Queue Monitoring

# Check delivery stats per domain — critical during warmup
pmta show topdomains --sort=connections

# Monitor deferred messages (sign of throttling)
pmta show queues | grep -i defer

# Watch for 421/550 blocks in real-time
tail -f /var/log/pmta/delivery.log | grep -E "421|550|blocked|spam"

External Monitoring Tools

• MXToolbox Blacklist Check: Run daily during warmup. Getting listed on even one DNSBL during warmup can cascade into bigger problems. If you do get blacklisted, here's my recovery guide.
• Mail-Tester.com: Send a test email before each volume increase to verify your spam score hasn't degraded.
• GlockApps / Folderly: If you have the budget, these show actual inbox placement rates across Gmail, Yahoo, and Outlook — not just delivery confirmations.

9. 5 Warmup Mistakes That Got Me Blacklisted

Every one of these is a mistake I made in production. Learning from these cost me weeks of recovery time and, in one case, an entire IP that I had to abandon:

1. The "I'll just send 5,000 on day one" mistake. Early in my career, I thought warmup was optional. I set up a fresh IP, loaded a campaign of 5,000 emails, and hit send. Within 4 hours, the IP was listed on Spamhaus ZEN and three other DNSBLs. Gmail returned 550 permanent blocks. The IP was effectively dead — I had to get a new one and start over. Lesson: There are no shortcuts. Follow the schedule.

2. Warming up with a purchased email list. I used a "verified" list from a data broker for warmup because I didn't have enough engaged subscribers. The list was 60% invalid addresses, and my bounce rate hit 15% within the first 200 emails. Google flagged the domain as a spam source within 48 hours. Lesson: Only warm up with addresses you know are valid — team accounts, personal emails, confirmed subscribers.

3. No per-domain throttling during warmup. I set a global rate limit of 100/hour but didn't configure domain-specific rules. Gmail received 60% of my warmup traffic (because most of my test list was Gmail). That's 60 emails/hour to Gmail from a brand-new IP — way too aggressive. Gmail throttled me with 421 blocks, and my domain reputation dropped to "Low." Lesson: Always configure per-domain limits, especially for Gmail. I now cap Gmail at 2/hour during Week 1.

4. Ignoring soft bounces. I was processing hard bounces correctly but letting soft bounces (4xx) retry indefinitely. After 5 days of retrying the same deferred messages, my queue built up to 3,000+ messages. When they finally delivered, it created a volume spike that triggered ISP alarms. Lesson: Set bounce-after 3d during warmup. Let soft bounces fail after 3 days instead of the default 4.5 days.

5. Skipping weekend monitoring. I was diligently checking metrics on weekdays but assumed things would be fine over the weekend. On a Saturday, a batch of warmup emails hit a spam trap that I had missed during list verification. By Monday morning, the IP was on two blacklists and my inbox placement had dropped from 95% to 40%. Lesson: During the 6-week warmup, monitoring doesn't take weekends off. I now set up automated MXToolbox alerts that notify me immediately of any new blacklist appearance.

10. When to Know Your IP Is Fully Warmed

Don't guess — use objective criteria. I consider an IP "fully warmed" when ALL of these conditions are met simultaneously for at least 7 consecutive days:

Once all criteria are met, I migrate the IP from the warmup vMTA to its production vMTA configuration with full production rate limits. But even after graduation, I never stop monitoring — reputation can drop at any time due to list quality issues, content changes, or ISP policy updates.

Frequently Asked Questions

Conclusion

Email warmup isn't glamorous, and it requires patience. But it's the difference between an IP that consistently delivers to the inbox and one that gets blacklisted within the first week. The 6-week schedule in this guide is what I follow for every new IP I bring into production — no exceptions, no shortcuts.

The key principles: start conservatively (20/day, not 200), warm both IP and domain simultaneously, configure per-ISP throttling from day one, monitor daily with Google Postmaster Tools, and never increase volume when metrics are declining.

If you want this entire warmup process handled for you — server setup, DNS configuration, warmup scheduling, and ongoing monitoring — check out my Email Infrastructure Setup services.