How to Self-Host a Mail Server Without Landing in Spam

"You can't self-host email any more" is half-true. You can — plenty of people do — but only if you treat deliverability as the actual project, not an afterthought.

The four things that decide whether you land in the inbox

1. A clean IP with reverse DNS. Your IP must not be on blocklists, and its PTR record must resolve to a hostname that matches your mail server's banner. VPSoto sets rDNS on request — ask before you start configuring.
2. SPF — a TXT record on your domain listing which servers may send for it. Example: v=spf1 mx -all.
3. DKIM — your server cryptographically signs every outgoing message; receivers verify the signature against a public key you publish in DNS. Non-negotiable in 2026.
4. DMARC — a policy record that tells receivers what to do when SPF/DKIM fail, and gives you reports. Start at p=none to observe, then tighten to quarantine/reject.

Use a modern stack, not raw Postfix tutorials from 2009

Spin up one of these and let it do the hard parts:

• Mailcow — Docker-based, full-featured, great admin UI
• Mailu — also Docker, lighter
• Mail-in-a-Box — opinionated, one-script install

They configure Postfix, Dovecot, DKIM signing, spam filtering, and webmail for you.

Sizing

A small mail server is happy on 2 GB RAM to start; 4 GB is comfortable once you add full-text search and aggressive spam scanning. Put it on SSD or NVMe — mail is lots of small files.

Reality check

Warm the IP gently (don't blast 10,000 messages on day one), keep your DNS tidy, monitor the DMARC reports, and handle bounces. Do that and your mail lands. Skip it and you'll spend a weekend wondering why Gmail hates you.

Want a clean IP and port 25 open? That's standard on VPSoto VPS plans — browse them here, or read the mail-server use case.