惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

月光博客
月光博客
MyScale Blog
MyScale Blog
博客园 - Franky
The Cloudflare Blog
IT之家
IT之家
Blog — PlanetScale
Blog — PlanetScale
博客园 - 聂微东
WordPress大学
WordPress大学
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
T
The Blog of Author Tim Ferriss
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
罗磊的独立博客
Google DeepMind News
Google DeepMind News
P
Proofpoint News Feed
Martin Fowler
Martin Fowler
aimingoo的专栏
aimingoo的专栏
J
Java Code Geeks
腾讯CDC
雷峰网
雷峰网
Microsoft Azure Blog
Microsoft Azure Blog
G
Google Developers Blog
博客园 - 【当耐特】
美团技术团队
云风的 BLOG
云风的 BLOG

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
IP Warmup for New Mail Servers: Complete 2026 Guide
Dhiraj Chatp · 2026-05-18 · via DEV Community

Dhiraj Chatpar

You just deployed your new KumoMTA or PowerMTA server. You have clean IPs, perfect DNS, and a million emails queued to send. Stop. If you send that volume immediately, you'll be blacklisted within 48 hours. This guide explains why IP warmup matters and exactly how to do it right.


Why IP Warmup Is Non-Negotiable

Internet service providers (Gmail, Outlook, Yahoo, Apple Mail) use sender reputation as their primary spam filter. Reputation is a score between -10 and 10 attached to your sending IP address, built from:

  • Volume history — How much email you send and how consistently
  • Bounce rate — Percentage of invalid recipients
  • Complaint rate — How many recipients mark you as spam
  • Spam trap hits — Emails sent to dormant/harvested addresses
  • Engagement — Read, click, reply rates on your messages

A brand new IP has zero reputation. ISPs treat zero-reputation IPs as high-risk by default. Sending high volume from a cold IP is the fastest way to signal to every major ISP that you're a spammer.


The 8-Week IP Warmup Schedule

This schedule works for any major ISP. Adjust based on your bounce and complaint data.

Phase 1: Verification (Days 1–7)

Before sending anything, verify your infrastructure:

  • [ ] SPF, DKIM, and DMARC DNS records are live and passing
  • [ ] Your From domain matches your sending domain
  • [ ] List is double opt-in — zero purchased or scraped lists
  • [ ] Postmaster tools registered: Gmail Postmaster, Microsoft SNDS
  • [ ] Dedicated IPs assigned (minimum 2 for rotation)

Phase 2: Soft Launch (Days 8–14)

Day 8–10: 500 emails/day

  • Send to your most engaged subscribers only (opened in last 30 days)
  • No HTML formatting — plain text preferred
  • No attachments, no images
  • Watch bounce rate: must stay below 2%

Day 11–14: 2,000 emails/day

  • Expand to 60-day engaged segment
  • Include simple HTML (logo + text)
  • Track complaint rate: must stay below 0.1%

Phase 3: Ramp (Days 15–28)

Day Volume
15–17 10,000/day
18–20 25,000/day
21–24 75,000/day
25–28 150,000/day

Phase 4: Scale (Days 29–56)

Week Volume
5 300,000/day
6 600,000/day
7 1,000,000/day
8+ Full volume

Golden rule: Never increase by more than 2–3x week-over-week once above 50K/day. Faster ramps trigger ISP throttling.


MTA-Level Warmup Controls

KumoMTA: Traffic Shaper Warmup

Use Lua scripting to enforce warmup caps automatically:

-- Warmup traffic shaper per IP pool
kumo:define_traffic_shaper({
  name = 'warmup-phase-1',
  max_message_rate = 50,    -- ~5,000/day assuming 8h active
  max_outbound_connections = 10,
})

kumo:define_traffic_shaper({
  name = 'warmup-phase-3',
  max_message_rate = 500,
  max_outbound_connections = 50,
})

-- Assign senders to warmup pools
kumo:define_smtp_source({
  name = 'warmup-sender-1',
  shaper = 'warmup-phase-1',
  egress_pool = 'warmup-pool-1',
})

Enter fullscreen mode Exit fullscreen mode

PowerMTA: Per-IP Rate Limiting

domain IP-address-pool warmup-pool-1
  ip-pool warmup-pool-1
    max-msg-rate 50/m
    max-rcpt-per-msg 1
    max-smtp-out 10

Enter fullscreen mode Exit fullscreen mode

Rotate IPs through progressively larger pools as reputation builds.


Monitoring Dashboard

Track these metrics daily during warmup:

Metric Good Warning Danger
Bounce rate < 2% 2–5% > 5%
Complaint rate < 0.1% 0.1–0.5% > 0.5%
Spam trap hits 0 1–2/week 3+/week
Inbox placement > 95% 85–95% < 85%

Set up Gmail Postmaster Tools and Microsoft SNDS alerts for reputation drops.


What Breaks Warmup (And How to Recover)

Problem: Bounce Spike

Cause: Sending to invalid addresses — likely a dirty list
Fix: Pause sends immediately. Scrub your list against email verification API. Resume at 50% of previous volume.

Problem: Complaint Spike

Cause: Recipients don't remember opting in, or subject lines are misleading
Fix: Review your subject lines. Re-engage dormant subscribers with a confirmation email before resuming.

Problem: Blacklisted by Spamhaus

Cause: Sending to spam traps or very high bounce rates
Fix: Remove hard bounces immediately. Submit delist request at spamhaus.org. Wait 24–48h before resuming.

Problem: Gmail Promotions Tab

Cause: Normal for marketing email; not a deliverability problem
Fix: Gmail's Promotions tab is not a blacklist. Focus on open rates and click rates regardless of tab placement.


Conclusion

IP warmup is not optional — it's the foundation of your sender reputation. A proper 8-week warmup gives you inbox placement that lasts years. Rush it and you'll spend months recovering from blacklists and ISP throttling.

The investment is in the setup: proper traffic shaping, monitoring dashboards, and a clear rollback plan. With KumoMTA's Lua scripting or PowerMTA's IP pools, warmup can be automated and hands-off after the initial configuration.

Need help designing your IP warmup strategy? PostMTA's deliverability engineers have warmed hundreds of IP ranges across Gmail, Outlook, Yahoo, and regional ISPs. We'll build your warmup playbook, configure your MTA, and monitor your first 90 days until you're hitting full volume with 98%+ inbox rates.

👉 Talk to a deliverability specialist →