Back to Blog
team@tinypod.app

Self-Hosting Your Own Email: Why You Probably Shouldn't

Self-hosting email is technically possible but practically painful. Deliverability, spam, reputation — here's the honest truth.

emailself-hostingopinionguide

Can You Self-Host Email?


Yes. Should you? Probably not.


The Problems


Deliverability

Big email providers (Gmail, Outlook) are aggressive about filtering. A new mail server IP has zero reputation. Your emails will land in spam.


IP Reputation

If your VPS IP was previously used for spam (common), you start in a hole. Some IP ranges are permanently blacklisted.


SPF, DKIM, DMARC

You need all three configured correctly. One mistake and your emails are rejected or marked spam.


Spam Filtering

You need to filter incoming spam. SpamAssassin, rspamd, or similar. This needs ongoing tuning.


Security

Email servers are high-value targets. A compromised mail server can send spam, damaging your IP reputation permanently.


Maintenance

Email never sleeps. If your server goes down at 2 AM, emails bounce. Bounced emails damage your reputation further.


When Self-Hosting Email Makes Sense


  • You're a sysadmin willing to dedicate significant time
  • You have a clean dedicated IP
  • You're receiving only (not sending)
  • Compliance requires it

  • Better Alternatives


    Managed Email

  • Migadu — affordable, privacy-focused
  • Fastmail — reliable, CalDAV included
  • Proton Mail — encrypted, Swiss privacy

  • Hybrid Approach

  • Self-host everything except email
  • Use a managed email provider
  • Forward to your self-hosted apps

  • What to Self-Host Instead


    Self-host the parts of email that are easy:

  • Webmail client (Roundcube) connected to managed email
  • Email aliases (SimpleLogin, addy.io)
  • Mailing lists (Listmonk)

  • Email is the one service where the self-hosting community widely agrees: the juice isn't worth the squeeze.