How to Choose the Right VPS for Running an Email Server

Choosing a VPS for a self-hosted email server is different from choosing one for a web application. The requirements are specific and unforgiving: mail servers are long-running, IO-intensive, and deeply affected by the reputation of the IP address they're assigned. A VPS that's excellent for a web application can be a poor fit for email.

This guide covers what actually matters when selecting a VPS for email, what to watch out for, and what most guides don't tell you about IP reputation on cloud infrastructure.

The IP Reputation Problem With Cloud Providers

Before anything else, understand this: many IP addresses on consumer VPS providers arrive pre-burned for email. Providers like DigitalOcean, Linode, Vultr, and AWS have had their IP ranges so heavily abused by spammers over the years that large blocks of their address space appear on blocklists before you've ever sent a single message.

This doesn't mean you can't run a mail server on these providers — but it means your first task before configuring anything else is to verify that your assigned IP is clean. Check it against Spamhaus, MXToolbox, and major blocklist databases before deploying your mail stack.

If the IP is listed, request a new one from your provider. Most will reassign IPs at no charge. Keep checking until you get a clean address.

What Specs Actually Matter for Email

RAM

Modern mail servers like Postfix are surprisingly lean on memory. A basic setup handling a few hundred accounts runs comfortably on 1–2GB. But if you're adding spam filtering (SpamAssassin or Rspamd), virus scanning (ClamAV), and webmail (Roundcube or Rainloop), memory requirements climb quickly. ClamAV alone can use 500MB–1GB depending on configuration.

Practical minimum: 2GB RAM for a basic setup with spam filtering. 4GB if you're adding virus scanning or running more than a few hundred active mailboxes.

Storage and IO

Email storage is append-heavy and retention-oriented — messages accumulate and mailboxes need fast random-access for IMAP. SSD storage makes a meaningful difference in mail server responsiveness compared to spinning disk, particularly for IMAP access patterns where clients are constantly reading individual message files.

For storage sizing: estimate (average mailbox size) × (number of mailboxes) × 1.5 for overhead. A conservative per-mailbox allocation for business use is 10–20GB. Fifty users means 500GB–1TB of storage, ideally SSD or NVMe.

CPU

Mail servers are not CPU-intensive under normal conditions. A shared-CPU VPS with 1–2 vCPUs handles most small deployments without strain. CPU becomes a constraint only if you're doing heavy content filtering or virus scanning on every message. For a few hundred users, CPU is rarely the bottleneck.

Network

Email traffic volumes are low compared to web traffic — even a busy mail server doesn't need more than 100Mbps of bandwidth. What matters more than raw throughput is network reliability and good peering relationships with major mail providers' networks. Providers with strong peering deliver better SMTP performance and lower latency to Gmail, Outlook, and Yahoo mail servers.

Reverse DNS: A Hard Requirement

Your VPS must have a PTR (reverse DNS) record that resolves the server's IP address to a hostname matching your mail server's fully qualified domain name. This is non-optional — many receiving mail servers check PTR records and reject mail from IPs that lack one or where the PTR doesn't match the SMTP banner the server presents.

Most VPS providers let you set custom PTR records through their control panel. Set this before sending your first email. The hostname you configure should match exactly what you've set as your mail server's hostname in Postfix or whichever MTA you're using. For the full explanation, see our guide on PTR records and reverse DNS.

Port 25: Verify Before You Deploy

Port 25 is used for server-to-server SMTP delivery — without it, your mail server cannot send email directly to other mail servers. Many VPS providers block outbound port 25 by default to prevent spam abuse from their infrastructure.

If port 25 is blocked, your outbound mail simply won't work, and this isn't obvious until you've already built out your server. Check your provider's policy explicitly before deploying:

• AWS and Google Cloud block port 25 permanently on standard accounts and require routing through their own mail services
• DigitalOcean and Vultr block port 25 by default but will unblock it on request after account verification
• Hetzner, OVHcloud, and Contabo generally allow port 25 on verified accounts

Confirm outbound port 25 availability before committing to a provider for a self-hosted mail server.

Providers Worth Considering for Email

Based on community experience with self-hosted mail deployments:

• Hetzner: Good reputation for IP cleanliness, port 25 available on verified accounts, competitive pricing, European data centers — a popular choice in the self-hosting community
• OVHcloud: Good network peering, port 25 allowed, multiple datacenter locations across Europe and North America
• Contabo: Affordable entry point, generally allows port 25, though IP reputation varies by range and should be verified before use
• DigitalOcean / Vultr / Linode: Port 25 blocked by default but unblockable on request; IP reputation varies heavily — requires checking per assigned IP

Avoid AWS and Google Cloud for self-hosted mail unless you have a specific architectural reason — both permanently restrict port 25 on standard accounts.

Snapshots and Backups

Your VPS provider must support regular snapshots and offsite backup capabilities. Email data is business-critical, and losing it to hardware failure or misconfiguration is unacceptable. Set up automated daily snapshots from day one, and test the restore process before you go live — not after your first serious incident.

For a broader look at self-hosted email backup strategy, see our guide on self-hosted email disaster recovery.

Is Self-Hosting on a VPS the Right Choice?

Running your own mail server gives you control and can reduce costs at scale — but it comes with ongoing maintenance that most organizations underestimate. Updates, security patches, monitoring, blocklist management, and authentication configuration all fall to you. Before committing, be honest about whether your team has the capacity to maintain it reliably over time.

If you want professional email infrastructure without the maintenance overhead, MailDog's mail service handles the underlying complexity. For outbound sending specifically, the SMTP relay provides reliable delivery without running your own MTA. See pricing for details, or contact the team with questions about your specific requirements.

Get the Foundation Right First

VPS selection for email is mostly about avoiding the obvious traps: blocked port 25, dirty IP reputation, insufficient storage, and missing reverse DNS. Get those four things right and the actual mail server software — Postfix, Dovecot, and your choice of spam filter — will handle the rest reliably. The hardware is rarely what limits a self-hosted mail server; the IP reputation and initial configuration almost always are.