Contents
IP warming is the process of systematically building sending reputation on new IP addresses by gradually increasing volume while maintaining high engagement rates. ISPs have no prior history with a new IP — they apply conservative default filtering until sufficient data accumulates to classify the sender. Attempting to send production volume from a cold IP produces deferrals and blocks that damage the IP's reputation before it has had a chance to establish one. The warming protocol determines whether a new IP becomes a productive sending asset or a liability.
Section 1
Core Warming Principles
- Start with engaged subscribersOnly send to recipients who have opened or clicked within the last 30 days during early warming phases. Engagement signals teach ISPs that recipients want your mail.
- Never rush the scheduleIf you're seeing high deferral rates, extend the current phase — do not continue the ramp. Forcing volume through a deferring IP worsens reputation, not improves it.
- Monitor daily, not weeklyCheck Google Postmaster Tools and SNDS data every day during warming. A reputation signal change requires same-day response, not end-of-week review.
- Separate warming from productionWarm new IPs while your existing infrastructure handles production volume. Never migrate production traffic to warming IPs — only when warming is complete.
- ISP-specific warming schedulesGmail, Outlook, Yahoo, and European ISPs warm at different rates. Build separate volume ramps per ISP, not a single combined schedule.
Section 2
IP Warming Volume Ramp Schedule
| Week | Gmail/day | Outlook/day | Yahoo/day | EU ISPs/day | Notes |
|---|---|---|---|---|---|
| 1 | 500 | 200 | 300 | 100 | Engaged only (opened 30d) |
| 2 | 1,000 | 500 | 700 | 300 | Monitor deferral rate |
| 3 | 2,500 | 1,000 | 1,500 | 700 | Expand to 60d engaged |
| 4 | 5,000 | 2,500 | 3,000 | 1,500 | Check Postmaster reputation tier |
| 5 | 10,000 | 5,000 | 7,000 | 3,000 | Expand to 90d engaged |
| 6 | 25,000 | 10,000 | 15,000 | 7,000 | Full active list |
| 7 | 50,000 | 25,000 | 35,000 | 15,000 | Verify HIGH reputation |
| 8 | 100,000+ | 50,000+ | 75,000+ | 35,000+ | Production volume — warming complete |
Section 3
PowerMTA Configuration for IP Warming
# Warming domain blocks — conservative limits that increase weekly # Week 1-2: Very conservativevirtual-mta-pool warming-pool # Only the new IP max-smtp-out tuning 2 max-conn-rate 0.2/s max-msg-rate 25/h # ~600/day retry-after 30m mx-rollup gmail.com # Week 5-6: Moderatevirtual-mta-pool warming-pool max-smtp-out 5 max-conn-rate 0.5/s max-msg-rate 500/h # ~12,000/day retry-after 20m mx-rollup gmail.com # Week 8+: Full production (warming complete)virtual-mta-pool production-pool # Move to production pool max-smtp-out 8 max-conn-rate 1/s max-msg-rate 300/h retry-after 15m mx-rollup gmail.com # Alternative: control volume at injection layer (recommended) # Submit only the warming schedule volume to PowerMTA # No need to change MTA config weekly — just control injection volume
Section 4
Monitoring Warming Progress
# Daily monitoring checklist during warming: # 1. Google Postmaster Tools # - IP reputation tier (target: progress from MEDIUM to HIGH over 4-6 weeks) # - Domain spam rate (must stay below 0.07% throughout warming) # - Delivery errors tab — look for specific error pattern increases # 2. PowerMTA accounting log format — deferral rate per IP per ISP grep "gmail.com" /var/log/pmta/accounting-YYYYMMDD.csv | \ awk -F, '$8 ~ /^4/ {deferred++} $8 == "250" {delivered++} \ END {printf "Deferral rate: %.1f%%\n", deferred/(delivered+deferred)*100}' # 3. Microsoft SNDS — check warming IP status # Target: GREEN throughout warming (YELLOW = slow down, RED = stop) # 4. Bounce rate monitoring # Hard bounce rate above 2% = list quality problem # Investigate source segment and suppress invalid addresses before continuing
Section 5
Common Warming Problems and Responses
| Problem | Cause | Response |
|---|---|---|
| 421 deferrals at Gmail during week 1-2 | Normal — new IP has no reputation | Continue at current volume; don't accelerate |
| 421 4.7.0 reputation deferrals | Too aggressive; list quality issue | Reduce volume 50%; extend phase by 1 week |
| Hard bounce rate above 2% | List contains invalid addresses | Run validation; suppress invalid before continuing |
| SNDS showing yellow on week 3+ | Complaint rate elevated | Switch to 30-day engaged only; reduce volume 30% |
| Postmaster Tools MEDIUM after 5 weeks | Low engagement rates | Revert to engaged-only list; extend warming 2 weeks |
FAQ
Frequently Asked Questions
How long does PowerMTA IP warming take?
Should I warm IPs with engaged or unengaged subscribers?
How do I configure PowerMTA to enforce IP warming volume limits?
What should I do if an IP gets a deferral during warming?
Can I warm multiple IPs simultaneously?
Operating PowerMTA at production volume?
We manage PowerMTA environments for high-volume senders — configuration, IP warming, daily reputation monitoring, and operational response. Fully managed. No self-service.
