Should I host my own email on a VPS?

What this is#

Not the how, the whether. Email is the one workload where the honest advice for most people is "don't", and the same honest advice makes self-hosting great for the right person. This page is the decision; the how-tos are linked at the end.

What self-hosting actually involves#

Running a mail server isn't the hard part, Mailcow installs in an afternoon. The commitment is everything after:

• Deliverability is a discipline, not a setting. rDNS, SPF, DKIM, and DMARC get you to the starting line; large receivers then judge your IP and domain reputation continuously. A fresh server earns trust over weeks of consistent, low-volume, legitimate sending, and one compromised WordPress form on the same box can spend that trust overnight.
• You become the blocklist watcher. Listings happen even to clean senders; noticing and delisting is on you (the tools), and our policy puts blacklist cleanup on the customer, with a charge per listing, precisely because it's real work.
• Uptime carries a different weight. A down website loses visitors; a down mail server eventually loses mail, senders retry for a few days, then bounce. Vacations count.
• Inbound is its own job: spam filtering, storage growth, and mailbox backups, mail is often the least replaceable data a person has.

None of this is exotic, but it's forever: a mail server is a pet, not a cattle.

When hosted mail is the right answer#

For most people and almost every business: mailboxes at a dedicated mail provider (or your registrar's mail service), your domain's MX pointing there, and your VPS doing everything except mailboxes. You get teams of people whose whole job is deliverability and uptime, for a few dollars a mailbox, and your VPS migration/reinstall/experiments never endanger mail. If email failing for a day would genuinely hurt you, this is your answer, and there's no shame in it.

When self-hosting is worth it#

• You want ownership: your mail on your hardware, no third party reading, mining, or locking you out. For many self-hosters this is the entire point, and it's a good one.
• You'll actually enjoy the craft: deliverability is a skill, and running clean mail infrastructure teaches more about the internet than almost any other service.
• The stakes fit: personal domains, project mail, a tinkerer's setup, places where a rough week hurts pride, not payroll.

If that's you: Mailcow on a 6 GB plan or larger, rDNS set first, the outbound and inbound checklists as your setup guides, and the email policy as the boundary (personal and transactional volume, never bulk).

The hybrid most setups should land on#

These aren't all-or-nothing:

• Mailboxes hosted, VPS sends transactional: human mail lives at a provider; your apps send their password resets either through the VPS directly (fine at low volume with the records set right) or through a relay like Amazon SES/Mailgun, which also keeps app mail off your personal reputation.
• Self-host inbound-light: some self-hosters run Mailcow for mailboxes but route all outbound through a relay, keeping the hardest problem (sending reputation) outsourced while owning their data.

The one-paragraph verdict#

Host your own email if you want to run a mail server, as a project, a principle, or a craft. If you just want email that works, host the mailboxes elsewhere, point MX there, and let your VPS be great at everything else.

Still need help?#

You can open a support ticket. So we can help on the first reply, it's worth mentioning:

• what you're weighing (self-hosting, hosted mailboxes, or the hybrid),
• roughly the volume and kind of mail involved.

Related questions#

• "Is it worth hosting my own email on a VPS?"
• "What's the ongoing work of running a mail server?"
• "Should my business self-host email?"
• "Can I keep mailboxes at a provider and still send from my VPS?"
• "What does the hybrid email setup look like?"