Self-hosted email is the home cooking of the internet — virtuous, technically pure, and almost universally harder than people expect. The "VPS" part of self-hosted email is the easy part. The "email" part is where most people give up. This guide is honest about both: what VPS specs actually matter, why hardware is the smallest part of the puzzle, and how to evaluate whether self-hosting email is right for you.
Real talk before you start. Most people who try self-hosted email give up within 6 months. The technology works; the operational burden of staying off blocklists and maintaining deliverability is real and ongoing. If your time is worth more than $5/month, paid email hosting (Migadu, Fastmail, MXroute) is probably the right answer. Self-host because you want to learn or have specific privacy requirements — not to save money.
What's in this guide
The hard truth about self-hosting email
The hardware and software for self-hosted email are excellent and free. Postfix, Dovecot, Mailcow, Mailu, mailinabox — all mature, all good. You can install them in an evening. The hard part comes after.
Email's actual deliverability depends on:
- IP reputation. Major email providers (Gmail, Outlook, Yahoo, iCloud) maintain reputation scores for every sending IP. New IPs start with neutral or negative reputation; you have to "warm them up" by sending small volumes that don't get marked as spam.
- Reverse DNS. Your IP must have a PTR record matching your sending domain. Most VPS hosts let you set this; some don't.
- SPF, DKIM, DMARC. Three DNS records that authenticate your mail. Get any of them wrong and your mail goes to spam.
- Blocklist hygiene. Public blocklists like Spamhaus list IP ranges with bad reputation. If your VPS's IP range was previously used by spammers, you may inherit that bad reputation.
- Volume patterns. Big email providers flag IPs that send unusual volumes. A new IP suddenly sending 1000 emails/day looks like compromised. Ramp up slowly.
- User behavior. When recipients mark your mail as spam, your reputation drops. One careless newsletter to a stale list can trash your reputation for months.
None of this is the VPS host's fault, and we can't really fix it for you. We can give you a VPS with clean IP reputation, set rDNS for you, and stay out of your way. The rest is on the operator. Postfix + Dovecot setup guide →
What email VPS actually needs
Hardware-wise, email is one of the lightest workloads imaginable.
- RAM: Postfix and Dovecot together use 100-300MB. Add antispam (Rspamd, SpamAssassin) and you're at 500MB-1GB. A 1-2GB VPS handles dozens of mailboxes.
- CPU: Idle most of the time. Brief spikes during antispam scans. 1 vCPU is plenty for typical loads.
- Storage: Depends entirely on how much email users keep. Plan for ~5GB per active mailbox at modest use. NVMe is overkill; SATA SSD is fine.
- Network: Email is small. A few hundred KB to a few MB per message. Bandwidth is rarely a constraint.
- Reverse DNS support: The VPS host must let you set custom rDNS for your IP. Non-negotiable for deliverability. Every OliveVPS plan supports custom rDNS.
- Stable IP without abuse history: Newer hosts have cleaner IP ranges. Ask before signing up.
IP reputation: the thing that matters most
Repeat: this is the make-or-break factor.
Before you spend an evening setting up Postfix, do this: ask your prospective host for a sample IP from the range you'd be assigned. Then check it on:
- MXToolbox Blacklist Check (60+ blocklists).
- SenderScore if available.
- Spamhaus IP Check.
If the IP is on any major blocklist, ask for a different one. If the entire IP range has issues, find a different host.
Most major hosts (DigitalOcean, AWS, Linode, Vultr) actually have worse mail reputation than smaller specialty hosts because spammers love the easy signups and free credits — Gmail and Outlook know this and aggressively filter mail from their IP ranges.
Specialty mail hosts win here. Companies whose entire business depends on email deliverability — like Mailgun, SendGrid, Postmark — invest heavily in IP reputation. Their delivery rates beat self-hosted setups, often by a lot. For transactional email, sending through a specialist is dramatically more reliable than self-hosting.
Sizing for users / mailboxes
| Setup | RAM | vCPU | Disk | Plan |
|---|---|---|---|---|
| Personal email, 1-3 mailboxes | 1GB | 1 vCPU | 25GB | Starter ($3.99/mo) |
| Small family or team, 5-15 mailboxes | 2GB | 1-2 vCPU | 60GB | Pro ($7.99/mo) |
| Small organization, 20-50 mailboxes | 4GB | 2 vCPU | 100GB | Premium ($15.99/mo) |
| Larger org, 100+ mailboxes | 8GB+ | 2-4 vCPU | 200GB+ | Higher tier |
Storage scales with retention policy. If users keep 10 years of mail with attachments, plan for 10-30GB per mailbox. If you enforce reasonable cleanup, 2-5GB per mailbox is typical.
Region selection
For self-hosted email, region affects two things:
- Latency to recipients' mail servers. Less critical than for web — email is asynchronous, an extra 100ms doesn't matter.
- Legal jurisdiction over your mail. EU hosting brings GDPR protections. US hosting is subject to US legal processes. Choose based on your privacy priorities.
For US users without specific jurisdiction needs: New York or Dallas. For privacy-focused users: Frankfurt (German privacy law is generally protective). For Indian users: Mumbai.
Common email stacks
Postfix + Dovecot (manual)
The classic Unix mail stack. Postfix handles SMTP (sending and receiving), Dovecot handles IMAP/POP3 (mail clients reading mail). Add Rspamd for antispam, OpenDKIM for signing. Maximum flexibility, maximum config burden. Setup guide →
Mailcow (Docker)
Mailcow bundles Postfix, Dovecot, Rspamd, SOGo (webmail), ClamAV, and a management web UI into a Docker Compose stack. docker compose up -d and you have a full mail server. Recommended starting point for self-hosters who don't want to assemble pieces. Wants 6GB+ RAM ideally, runs on 4GB with some pruning.
Mailu (Docker)
Similar to Mailcow but lighter. Postfix, Dovecot, Rspamd, Roundcube webmail. Smaller resource footprint than Mailcow. Slightly less feature-rich.
Mail-in-a-Box
Single-script installer that sets up everything on a fresh Ubuntu box. Simplest possible setup. Trades some flexibility for ease.
Stalwart
Modern Rust-based all-in-one mail server (SMTP + IMAP + JMAP). Newer, less battle-tested, but architecturally cleaner than the Postfix-era stacks. Worth watching.
Email-friendly VPS hosting
Custom rDNS supported on every plan, clean IP ranges, fast support if your IP needs replacing. Starting at $3.99/mo. We won't pretend deliverability is easy — we'll just give you the right starting point.
See VPS Plans →Paid alternatives worth considering
If reading the deliverability section made you reconsider self-hosting, these are honestly worth a look. We're not selling them — just noting they exist.
- Migadu: $19/year for unlimited domains and ~30 mailboxes. Excellent for small teams. Supports custom domains, IMAP/SMTP, no per-mailbox pricing.
- Fastmail: $5/mo per user. Polished UI, great mobile apps, custom domains supported.
- MXroute: $40/year (lifetime tier deals available). Massive email storage, generous limits, no-frills service.
- Proton Mail: $4-10/mo. Privacy-focused, end-to-end encrypted between Proton users, Swiss jurisdiction.
- Tuta (Tutanota): Similar to Proton but German.
For ~$20-100/year you get email that just works, deliverability is someone else's problem, and you keep your custom domain. Self-host if the learning is the point or if you have specific control needs — not to save the price of a coffee per month.
FAQ
How long does it take to "warm up" a new email IP?
2-6 weeks of careful, gradual sending to build reputation. Start with 10-50 messages per day, ramp slowly. Send to engaged recipients first (people who'll open and reply). Avoid sending to old/stale lists during warmup. Major providers (Gmail, Outlook) take longest to grant good reputation.
What if my IP gets blocklisted?
Most blocklists have removal request forms. Submit, wait 24-72 hours. If the cause was your fault (spam, compromised account), fix it first. If the listing was unfair, the appeal usually succeeds. Repeated listings on the same IP suggest your sending hygiene needs work.
Will OliveVPS replace my IP if it gets blocklisted?
Once, yes — file a ticket and we can typically swap to a clean IP from our pool. Repeat offenders, no — at that point the cause is your sending behavior, and a new IP would just become blocklisted again.
Can I run a mail server on a 1GB VPS?
For 1-3 personal mailboxes with light antispam, yes. For more users or aggressive antispam (ClamAV virus scanning, heavy Rspamd), bump to 2GB. Mailcow specifically is happier with 4-6GB.
Should I run my mail server alongside other services on the same VPS?
Light services (a personal blog, Pi-hole) — fine. Heavy services that compete for resources during mail processing — not great. Spam scanning is CPU-spiky; you don't want it competing with your busy web app at the same moment. For serious self-hosters, mail gets its own VPS.