Email Self-Hosting: Is It Worth It?

Among all the things you can self-host, email is the most contentious. Some people say it is the ultimate expression of digital independence. Others say it is the one thing you should never try to run yourself. The truth, as usual, is somewhere in the middle.

Why Self-Host Email?

The fundamental argument for self-hosting email is the same as for anything else: control. Google reads your email to serve you ads. Microsoft scans attachments for malware and sends telemetry about what you open. ProtonMail encrypts your inbox but holds the keys. With a self-hosted mail server, you hold the keys. Nobody scans your messages. Nobody builds a profile on your communication patterns.

For businesses handling privileged communications (legal, medical, financial), this control is not a luxury. It is a professional obligation. Client-attorney communications should not be scanned by an advertising company.

The Hard Parts

Email is not like other self-hosted applications. The hard part is not the server software, which is well-established and reliable. The hard part is deliverability.

• IP reputation. Email providers (Gmail, Outlook, Yahoo) assign a trust score to every sending IP address. A new IP has no reputation. It takes weeks or months of clean sending to build one. During that time, your emails may land in spam folders or be silently rejected.
• DNS configuration. You need properly configured SPF, DKIM, and DMARC records. One mistake and your emails bounce or get flagged as spoofed.
• Blacklists. If your server's IP range was previously used by spammers, it may be on blacklists before you even send your first email. Getting delisted is tedious.
• Maintenance. Mail servers need security patches, spam filter updates, and log monitoring. They are a high-value target because a compromised mail server can send thousands of spam messages before anyone notices.

A Practical Compromise

Many VPS1 clients take a hybrid approach to email:

• Use a transactional email service (like a paid SMTP relay) for outbound delivery. Your server generates the email, but the relay service handles the hard part of getting it into inboxes. This sidesteps the IP reputation problem entirely.
• Self-host the inbound side. Your server receives and stores email. You control the data at rest. Combined with full-disk encryption, this gives you data sovereignty over stored messages.
• Use a simple Docker-based mail server like Mailcow or Docker Mailserver. These package everything (Postfix, Dovecot, Rspamd, webmail) into a single deployment that is manageable.

When to Do It

Self-host email if: you have a legitimate need for email privacy (legal, medical, government contracting), you are willing to invest in proper setup and ongoing maintenance, and you are comfortable using a relay service for outbound delivery during the reputation-building period.

Do not self-host email if: your primary motivation is saving money on Google Workspace (the savings are modest), you cannot tolerate any deliverability issues during the ramp-up period, or you do not have expert help managing the server.

VPS1 deploys and maintains mail servers for clients who need them. We handle the DNS configuration, reputation building, spam filtering, and ongoing security. Talk to us if email self-hosting is on your roadmap.