Self-host your mail server

Original Article ↗ Hacker News Discussion ↗

Self‑hosting an email server promises greater control, independence from large providers, and some insulation from government or corporate scanning of private messages. Commenters note that modern tools and turnkey stacks (e.g., Mailcow, Stalwart, Mail‑in‑a‑Box, rspamd) make basic setup and spam filtering quite manageable, especially on a VPS with a clean IP and proper SPF/DKIM/DMARC. However, many argue that reliable outbound delivery to major providers has become so fragile—due to IP reputation systems, blacklists, and opaque filtering—that for most people it’s safer to host only inbound mail or simply use a paid provider while keeping a custom domain for portability.

Overall sentiment on self‑hosting email

  • Strongly mixed views.
  • Some report 10–20+ years of smooth self‑hosting with few issues.
  • Others describe it as a constant headache, especially for outbound delivery, and say they would never do it again given cheap hosted services.

Difficulty and operational burden

  • Receiving mail and basic stack setup (Postfix/Dovecot/rspamd, etc.) is seen as straightforward by many.
  • The hard part is long‑term maintenance: keeping up with standards (SPF/DKIM/DMARC, DANE, certs), spam filtering, and debugging intermittent, opaque issues.
  • Several emphasize that being a mail admin is a real job; doing it well in spare time is non‑trivial.

Deliverability & IP reputation

  • Widely cited as the main problem, not spam filtering itself.
  • Even with correct SPF/DKIM/DMARC, PTR, and clean IPs, people report:
    • Messages silently dropped or going to spam, especially at large providers (Gmail, Outlook/Hotmail, Yahoo, Microsoft‑hosted domains).
    • IP ranges from popular VPS providers sometimes effectively “burned” by past abuse.
  • Others report near‑perfect deliverability for many years, attributing success to:
    • Long‑lived, clean IPs; reputable ASes; sometimes business‑grade or colo connections.
    • Occasional manual whitelisting requests.
  • Many recommend SMTP relays (SES, smtp2go, MailPace, etc.) as cheap insurance.

Privacy, control, and decentralization

  • Pro‑self‑hosting arguments:
    • Avoid lock‑in and arbitrary account bans.
    • Keep data out of large providers, especially under regulatory scanning regimes.
    • Preserve email’s decentralized nature; more independent servers counter centralization.
  • Counterarguments:
    • Email is inherently two‑party; if the other side uses a big provider, they still see content.
    • For many, offline clients plus custom domains on a hosted provider give “enough” control.

Architectures and tools

  • Mentioned stacks/solutions: Stalwart, Mailcow, Mail‑in‑a‑Box, docker‑mailserver, iRedMail (paid version preferred), maddy, classic Postfix+Dovecot+rspamd, qmail.
  • Hybrid patterns:
    • Self‑host inbound storage, relay outbound via third‑party.
    • Home servers using VPS relays to bypass ISP port blocks or reputation issues.

Alternatives and middle ground

  • Common recommendation: buy your own domain and use a provider that supports custom domains and aliases; this gives portability without admin burden.
  • Some propose cooperative/community‑run hosting as a compromise between full DIY and big providers.