Self-Hosted Email: Why You Probably Shouldn't

Self-hosting email is the final boss of the self-hosting hobby. You can run your own web servers, databases, file storage, and monitoring dashboards on a $5 VPS without breaking a sweat. Email is different. Email is a federated system where your ability to send messages depends entirely on whether Gmail, Outlook, and Yahoo decide your server is trustworthy — and their default answer is no. This is the one service where even experienced self-hosters pay someone else.

What Running an Email Server Actually Requires

An email server is not one piece of software. It's a stack. You need an MTA (mail transfer agent) like Postfix to send and receive mail. You need an IMAP server like Dovecot so your email client can read messages. You need spam filtering — SpamAssassin or rspamd — because without it, your inbox becomes unusable within hours. You need virus scanning, because email is still the primary vector for malware distribution. You need TLS configured correctly for encryption in transit. And you need a web interface unless you plan to use only a desktop client.

Then there's the DNS. Email requires at minimum four DNS record types configured correctly: MX records pointing to your server, SPF records declaring which IPs are authorized to send on your behalf, DKIM records providing a cryptographic signature for outbound messages, and DMARC records telling receiving servers what to do when authentication fails. Get any one of these wrong and your mail either doesn't arrive or lands in spam. Get all of them right and your mail might still land in spam, because DNS configuration is necessary but not sufficient for deliverability.

Projects like Mail-in-a-Box and Mailu exist to simplify this stack. Mail-in-a-Box bundles Postfix, Dovecot, Roundcube webmail, rspamd, and automatic DNS configuration into a single installer. Mailu does something similar with Docker containers. Both of them genuinely reduce the setup from a multi-day project to a few hours. Neither of them solves the actual problem.

The Deliverability Wall

The actual problem is deliverability, and it's not a technical problem — it's a political one. Gmail, Outlook, and Yahoo collectively handle the vast majority of consumer email. [VERIFY: exact market share figures vary by source, but these three providers are consistently cited as handling 70-80%+ of consumer email.] They decide whether your message reaches an inbox or a spam folder, and their filtering is aggressive, opaque, and biased against small senders.

When you set up a new email server on a fresh VPS IP, you have no sender reputation. The major email providers treat unknown senders the same way a nightclub bouncer treats someone without an ID — you're not getting in until you prove yourself. "Proving yourself" means sending small volumes of legitimate email, getting recipients to open and interact with it, not triggering any spam complaints, and doing this consistently for weeks to months. It's called IP warming, and it's as tedious as it sounds.

The problem compounds because VPS IP addresses are frequently recycled. The IP you get from Hetzner or DigitalOcean may have been used by a spammer last month. It might already be on blacklists you've never heard of. Checking and delisting from blacklists — there are dozens of them — is another maintenance task that email self-hosters discover the hard way. You can do everything right technically and still have your mail rejected because the previous tenant of your IP was sending fake Viagra ads.

Google has also tightened its requirements significantly. As of 2024, bulk senders need to meet strict authentication requirements (SPF, DKIM, DMARC all passing), maintain spam complaint rates below 0.1%, and support one-click unsubscribe. [VERIFY: Google's February 2024 sender requirements update — specific thresholds may have been updated since.] These requirements are reasonable for large senders with ops teams. For a self-hoster sending personal email from a single IP, they represent a compliance burden that never ends.

The Maintenance Reality

Even after you get through the initial setup and IP warming, email servers require ongoing attention at a level that other self-hosted services don't.

Queue monitoring is daily work. Email that can't be delivered sits in a queue, and queues that grow unchecked mean something is wrong — maybe a remote server is temporarily down, maybe your IP got blacklisted again, maybe a configuration change broke outbound delivery. You need to watch the queue, understand why messages are stuck, and fix the underlying issue before the queue becomes a problem.

Blacklist monitoring is weekly work. Services like MXToolbox can check whether your IP appears on major blacklists, but new blacklists appear regularly, and delisting procedures vary from "fill out a form" to "send an email to an address that may or may not be monitored." Some blacklists delist automatically after a period of clean sending. Others require manual requests. A few are essentially permanent unless you change IPs.

Storage management is ongoing. Email accumulates. Attachments accumulate faster. Without active management — quotas, archival policies, pruning old messages — your mail server's disk will fill up. This is true on any platform, but on a managed service like Fastmail, storage is the provider's problem. On your server, it's another thing to monitor.

Security patching is critical. Email servers are high-value targets. An exploited mail server doesn't just compromise your messages — it becomes a spam relay, which gets your IP blacklisted everywhere, which means your legitimate email stops working too. Postfix and Dovecot need to be kept current. The web interface needs to be kept current. The spam filter needs to be kept current. One missed patch is all it takes.

The Cost Comparison That Ends the Debate

Fastmail costs $5/month for personal use. Google Workspace starts at $6/month per user. Both give you reliable deliverability, spam filtering that's been trained on billions of messages, storage measured in gigabytes, mobile apps, calendar integration, and a support team. Neither will wake you up at 3am because your MX record expired.

A self-hosted email server costs a VPS ($5-10/month for a server with enough resources), your time for setup (8-20 hours depending on your experience), your time for IP warming (weeks of careful sending), your time for ongoing maintenance (2-4 hours/month if nothing goes wrong, significantly more when something does), and the ongoing risk that your messages simply don't reach their destination.

Even if you value your time at $0, the deliverability problem makes self-hosted email a worse product than a $5/month Fastmail account. Your self-hosted server will have worse spam filtering, worse deliverability, no mobile app (unless you configure one), and no support when things break. You're paying more in time to get a service that works less reliably. The math doesn't close.

The r/selfhosted community — people who self-host everything from file storage to media servers to DNS — overwhelmingly recommends against self-hosting email. That's not because they lack the technical skill. It's because they tried it, fought the deliverability battles, and concluded that email is the one service where paying a provider is the rational choice.

What Mail-in-a-Box and Mailu Actually Simplify

These projects deserve credit for what they do. Mail-in-a-Box turns a multi-day Postfix/Dovecot configuration marathon into a 30-minute installer. It handles DNS configuration, generates the right SPF/DKIM/DMARC records, sets up Roundcube webmail, configures spam filtering, and gives you a management dashboard. For the setup phase, it's excellent.

Mailu does the same thing with Docker — containerized Postfix, Dovecot, rspamd, and a web interface, deployable with a docker-compose file. For people who are already running Docker on a VPS, Mailu integrates cleanly with existing infrastructure. The architecture is sound and the project is actively maintained.

What neither project can simplify is the deliverability problem. They can configure your DNS records correctly. They can set up authentication properly. They cannot make Gmail trust your IP. They cannot prevent your VPS's IP from landing on blacklists. They cannot replicate the sender reputation that Fastmail and Google have built over decades. The setup is the easy part. Deliverability is the hard part, and no software can solve it for you — it's a relationship between your server and every other mail server on the internet.

The One Exception

There is a legitimate use case for self-hosted email infrastructure, and it's not personal email. It's transactional email at scale — order confirmations, password resets, notification emails — where you need to control the sending pipeline and the volume justifies dedicated infrastructure.

But even here, the standard advice is to use a specialized service. Postmark, Amazon SES, Resend, and Mailgun exist specifically for transactional email. They maintain IP reputation across their networks, handle bounces and complaints automatically, provide delivery analytics, and charge fractions of a cent per email. Amazon SES costs roughly $0.10 per 1,000 emails. [VERIFY: SES pricing may have changed; check current AWS pricing page.] At those rates, the build-vs-buy decision for transactional email is as clear as it is for personal email — buying wins.

The truly self-hosted transactional email use case — where you operate your own SMTP infrastructure for application email — exists primarily in organizations with regulatory requirements that prohibit third-party email processing, or at volumes where even SES pricing becomes significant. If you're reading a self-hosting guide on the internet, you're probably not in either category.

The Bottom Line

Self-host your web servers. Self-host your databases. Self-host your file storage, your media server, your git repos, your monitoring dashboards. Self-host everything that makes sense to self-host. But pay someone for email. The deliverability problem is not a technical challenge you can solve with better configuration — it's a trust network that takes years to build and seconds to lose. Fastmail at $5/month is the best deal in self-hosting, because it's the service that lets you self-host everything else without wasting time on the one service that fights you every step of the way.

This is part of CustomClanker's Self-Hosting series — the honest cost of running it yourself.