kern.services
Running Your Own Mail Server Is Still Worth Considering
Photo by Zon Dasein on Unsplash
•
email self-hosting privacy ops ai automation

Running Your Own Mail Server Is Still Worth Considering

Why self-hosting email with modern tools like mox or mailcow is much less painful than its reputation suggests — from initial IP deliverability to backups, updates, and AI-assisted operations.

Every few months, the same discussion comes up among developers and small business owners looking to leave Google Workspace or Microsoft 365. People compare privacy-focused alternatives — Mailbox.org, Fastmail, Posteo, Proton, Tuta, or newer efforts like Mozilla’s Thundermail — and quickly notice that every managed provider comes with trade-offs in client support, pricing, or trust.

Sooner or later, someone brings up self-hosting, and someone else immediately shuts it down: sender reputation will put your mail straight into spam, and maintaining a mail server is a full-time job.

I still host my own mail, more out of tradition than ideology. My honest impression today is much less dramatic: it works reliably, ongoing effort is low if you know your way around Linux, and modern software is worlds apart from stitching Postfix, Dovecot, and SpamAssassin together by hand. At the same time, I completely understand anyone who would rather pay a few euros a month and write support tickets instead of answering them.

Picking a modern stack

You no longer need half a dozen daemons and glue scripts to run a clean mail server:

  • mox (my default recommendation) — A modern, single-binary open-source mail server built specifically for low-maintenance self-hosting. It handles SMTP, IMAP, SPF, DKIM, DMARC, and TLS out of the box and runs comfortably on the smallest Hetzner ARM instance.
  • mailcow — The right choice when you want a full groupware suite with a polished web UI, shared mailboxes, tagging, contacts, and calendars (SOGo). Heavier as a Docker stack, and also available managed (e.g. via Servercow ).
  • Stalwart — I do not have any experience with this one, but it looks promising and worth watching if you want a modern all-in-one server that speaks JMAP alongside IMAP and CalDAV.

With all of these options, you don’t have to abstain from using AI - with Ironbrain , my MCP Service, you can interact with your IMAP servers as comfortable as working with Gmail or Microsoft 365.

Getting past the initial reputation hurdle

Installing the server is easy; convincing the rest of the internet to trust a fresh cloud IP is the real work. The first few days can be bumpy, but delivery settles down quickly if you follow a clear sequence:

  • Check the IP and setup first: Cloud IPs sometimes inherit a blocklist entry from a previous customer. Check your IP and domain against Spamhaus and MXToolbox right away — spinning up a new VM with a clean IP is often faster than fighting delisting forms. Once configured, send a quick test message to mail-tester.com to verify headers, TLS, and authentication in one go.
  • Get DNS right before sending: Matching forward and reverse DNS (PTR) for the mail hostname, plus clean SPF, DKIM, and DMARC records. Tools like mox generate the exact records for you.
  • Register with major postmasters and delisting portals: Proactively set up monitoring or request allowlisting/delisting with the major receivers while keeping initial mail volume normal:
  • Mind Telekom’s Impressum rule: In Germany, Telekom is consistently the fussiest receiver. They expect a website with a valid legal notice (Impressum) directly on the mail server’s hostname before they allowlist your IP. Putting a tiny static page there on day one avoids days of bounces and manual emails with their postmaster team.

Day-two operations: backups, updates, and AI

Once delivery runs smoothly, keeping a mail server healthy comes down to a few disciplined habits — and AI assistants have made the surrounding work noticeably lighter:

  • Off-site backups with alerting: Nightly encrypted backups (for example Borg to an external storage box) covering mail data and configuration, paired with a small health check that alerts you if a backup fails or goes stale.
  • A calm update rhythm: Updating a single binary like mox takes minutes; for a Docker suite like mailcow, a monthly routine of checking disk space, verifying the latest backup, and pulling the new release keeps things predictable alongside automatic TLS renewal and OS patches.
  • AI for sysadmin chores: You still shouldn’t run blind shell commands on production mail infrastructure, but an AI assistant in the terminal turns annoying chores into ten-minute tasks — verifying DNS records, reading cryptic Rspamd headers or bounce codes, writing backup check scripts, and keeping runbooks current.
  • AI for mail automation on your own terms: Most commercial AI email tools assume Gmail or Microsoft 365. Owning standard IMAP, SMTP, and CalDAV endpoints lets you connect assistants cleanly — with read-only access on personal inboxes, dedicated send accounts, or human-in-the-loop approval (as I built for my own setup with Ironbrain MailCal ).

Bottom line

If you want cloud storage, video calls, and someone else on call on Sunday in one package, buy a managed mailbox. If you already run a couple of Linux servers, though, self-hosted email doesn’t deserve its scary reputation: pick a lean stack like mox, do the DNS and postmaster homework once, automate your backups, and it quietly does its job for years.