Module 1 · Lesson 2 of 26

When (and when not) to self-host with Mailcow

Part of Mailcow: Self-Hosted Mail Server Mastery — Introduction to Mailcow.

Self-hosting mail in 2026 is harder than ever. Inbox providers (Gmail, Microsoft 365, Yahoo) are aggressive about new senders, dynamic IPs, and weak authentication. Mailcow makes the operations easy — it does not solve deliverability for you.

Good fits for Mailcow:

  • Internal mail for a team of 5–500 with a clean static IP and reverse DNS.
  • Custom-domain mailboxes for an agency or boutique hosting product.
  • High-control workloads (legal, healthcare) where you cannot send through a third party.

Poor fits:

  • Bulk marketing or cold outreach — use a dedicated sending platform like KumoMTA or a relay.
  • Residential or dynamic IPs — most providers refuse mail from these ranges.
  • Anyone who cannot keep a server patched within 48 hours of a CVE.

Cost reality check (2026):

Item Typical monthly cost
VPS (4 vCPU / 8 GB / 80 GB SSD) $20–$40
Static IPv4 with clean reputation included or +$2
Backup storage (S3-compatible) $1–$5
Your time (4 hrs/month maintenance) priceless

🎯 Rule of thumb: self-hosting beats $6/user/month Google Workspace once you cross ~10 mailboxes — but only if you actually maintain it.

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