Module 5 · Lesson 10 of 25

Why warming exists

Part of KumoMTA: High-Volume Sending Engine — IP Warming Strategies & Pools.

Fresh IPs send tiny volumes (a few hundred/day) and slowly scale up. Send 100k from day-one and Gmail's spam filter slams you for a month.

Warming curves (rough industry consensus):

Day Daily volume per IP Notes
1 50 All to most-engaged recipients
2 100
3 500
5 1,000
7 2,500
14 10,000
21 50,000
30 100,000+ Fully warm for most ESPs

During warming you MUST:

  • Send to your most engaged segment first.
  • Maintain bounce rate <2% and complaint rate <0.1%.
  • Send consistent volumes — gaps look like signs of compromise.
  • Sign with DKIM, align SPF + From, publish DMARC.

KumoMTA's job: enforce the daily caps and rotate through the warming pool so no single IP exceeds its bucket.

Sign in to keep track of what you have read.

Pulse · self-hosted sending

Own the infrastructure your pipeline depends on.

One install script on your own server. Pulse sets up the MTA, mailboxes, certificates and dashboard; you add domains and start sending.

# on a fresh Ubuntu server
$ cd pulse && sudo ./install.sh
→ docker compose up · kumomta · stalwart · caddy
→ dashboard ready on https://pulse.yourdomain.com
$

Also from us:Beat — monitoring that tells you the fixConsulting — $65/hr, no retainer