Module 12 · Lesson 25 of 25

Continuous deliverability tuning

Part of KumoMTA: High-Volume Sending Engine — Observability, Alerting & Deliverability Tuning.

Deliverability isn't a one-time setup — it's a weekly review cycle.

Weekly checklist:

  1. Pull Gmail Postmaster Tools — domain reputation, IP reputation, complaint rate.
  2. Pull Microsoft SNDS — IP color (green/yellow/red), filter results.
  3. Pull MailVitals (or competitor) for inbox placement seed test.
  4. Review top bounce categories per tenant — adjust suppression aggressiveness.
  5. Adjust shaping.toml for destinations that throttled.
  6. Rotate DKIM selector if >12 months old.
  7. Re-check DMARC enforcement: still p=reject? aggregate reports clean?

Quarterly:

  • Warm a fresh IP pair as cold-standby (so you have warm spares for emergencies).
  • Audit shaping.toml against actual queue behavior — old rules go stale.
  • Run inbox placement tests across all major destinations.

Annually:

  • Rotate DKIM keys (new selector, retire old after 30 days).
  • Re-evaluate IP pool sizes vs sending volume.
  • Renegotiate IP block leases with hosting provider if needed.

🌍 Deliverability is the long game. Process beats heroics.

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