IP Warmup Strategies 2026: Complete Guide to Building Sender Reputation

Your sender reputation is the single most important factor determining whether your emails land in the inbox or the spam folder. New sending IPs start with zero reputation — and the fastest way to destroy your deliverability for months is to skip the warmup process.

This guide covers the complete IP warmup strategy for 2026: ISP-specific requirements for Gmail, Outlook, Yahoo, and Apple Mail; automated warmup Lua policies; traffic shaping during the ramp period; and the exact rollback procedures if something goes wrong.

---

Why IP Warmup Matters in 2026

Gmail, Yahoo, and Microsoft apply machine learning reputation models to every sending IP. These models evaluate:

• Volume trajectory — Sudden spikes trigger abuse filters
• Complaint rate — >0.1% complaints gets you throttled or blocked
• Bounce rate — Hard bounces damage reputation faster than soft bounces
• Engagement rates — Opens, clicks, and reply rates signal legitimacy
• Authentication status — SPF, DKIM, and DMARC alignment affect trust scoring

New IPs have no history, so every ISP treats them as potentially malicious until proven otherwise. The warmup process builds that proof systematically.

---

ISP-Specific Warmup Requirements

Gmail (Google Workspace / Gmail.com)

Gmail is the largest single mailbox provider in the world. Gmail's reputation system is the strictest — a botched Gmail warmup affects your deliverability for 60-90 days.

Gmail warmup schedule (recommended 8-week ramp):

Week	Daily Volume	Notes
1	50-100 msgs/day	Only highly engaged recipients (opened in last 30 days)
2	200-500 msgs/day	Continue engaged users, watch complaint rate
3	1,000-2,000 msgs/day	Add moderately engaged users
4	5,000-10,000 msgs/day	Monitor Gmail Postmaster Tools daily
5	25,000-50,000 msgs/day	Check spam rate < 0.1%, complaint rate < 0.05%
6	100,000-200,000 msgs/day	ISP trust building phase
7	400,000-800,000 msgs/day	Approach full volume
8	Full volume	Continuous monitoring via Postmaster Tools

Critical Gmail requirements:

• SPF, DKIM, and DMARC must all pass before starting warmup
• Use Gmail Postmaster Tools to monitor reputation in real time
• If complaint rate exceeds 0.1%, pause immediately and investigate

Microsoft 365 / Outlook / Hotmail

Microsoft's Smart Network Data Services (SNDS) and Outlook.com's filtering are slightly more forgiving than Gmail, but still require systematic warmup.

Microsoft warmup approach:

• Similar 8-week schedule to Gmail
• Monitor via SNDS (snds.azurewebsites.net) — free IP reputation data
• Outlook.com complaint threshold: 0.1% (same as Gmail)
• Microsoft's filtering is more sensitive to hard bounces than soft

Yahoo Mail

Yahoo's filtering improved significantly in 2024-2025 with their mandatory DMARC requirements. Yahoo uses complaint rate as the primary reputation signal.

Yahoo warmup:

• 6-week ramp is sufficient for most senders
• Monitor via Yahoo Postmaster (postmaster.yahoo.com)
• Complaint rate must stay below 0.1%
• Yahoo is more tolerant of volume spikes than Gmail

Apple Mail (iCloud)

Apple's Mail Privacy Protection (MPP) introduced in 2021 changed how Apple measures engagement. MPP sends opens automatically, which means Apple-based open rates are inflated and unreliable for reputation.

Apple-specific considerations:

• Focus on click rates rather than open rates for Apple recipients
• Apple's filtering is generally lenient for legitimate senders
• High complaint rates from Apple users will still trigger filtering

---

Automated KumoMTA Warmup Lua Policy

This is a production-ready Lua policy for KumoMTA that implements automated IP warmup with adaptive throttling:

lua
-- /etc/kumomta/warmup_policy.lua
-- Automated IP warmup for KumoMTA

-- Warmup schedule: messages per day by week
local WARMUP_SCHEDULE = {
    week1 = 100,
    week2 = 500,
    week3 = 2000,
    week4 = 10000,
    week5 = 50000,
    week6 = 200000,
    week7 = 800000,
    week8 = nil, -- nil = full volume, based on ISP feedback
}

-- IP pool for rotation during warmup
local WARMUP_IPS = {