You bought a domain. You want you@yourdomain to work. The default assumption used to be: install Postfix + Dovecot on a VPS and configure DNS. In 2026 that path leads to your messages going to spam folders 30% of the time and you spending two evenings a month fixing reputation issues. There are better options.

This article is about practical email-on-your-domain in 2026: the four real choices, what each one costs, and what trade-off each one carries.

Why self-hosting email got harder

Three things happened over the last 15 years.

First, anti-spam at major providers (Gmail, Outlook, Yahoo, iCloud) became aggressive. They penalise mail from new IPs, low-volume IPs, IPs without enough reputation. A fresh VPS has zero reputation. You build it slowly by sending consistent, low-volume, well-authenticated mail. Mistakes set you back to zero.

Second, DNS authentication (SPF, DKIM, DMARC) became required, not optional. In 2024 Gmail and Yahoo started bouncing mail without DMARC. If you set the records wrong, your mail does not arrive. Self-hosters get the records right eventually, after some pain.

Third, hosting providers started blocking SMTP outbound by default. DigitalOcean, Hetzner, Vultr, AWS all require explicit unlock requests for port 25. Some refuse. The reason is they got tired of customers running spam.

The combination means a self-hosted mail server in 2026 needs: working SPF, DKIM, DMARC, MTA-STS, BIMI optional, reverse DNS, IP reputation building, anti-spam software, IMAP/SMTP encryption, daily monitoring of bounces and reputation. Possible. Not worth it for most.

Option 1: a managed mailbox provider

The default answer for almost everyone. You pay 1-6 euro per mailbox per month and somebody else handles all of the above.

The market splits in two:

Microsoft 365 and Google Workspace are the big two. Both cost around 5-6 euro per user per month. Both come with a calendar, contacts, file storage, video calls. Both are reliable, deliverability is excellent, you can be set up in 30 minutes by changing 4 DNS records.

Mailbox-only providers are cheaper and lighter. Fastmail (3-5 euro/mo, based in Australia, no Big Tech), Mailbox.org (3 euro/mo, Germany, GDPR-strict), ProtonMail (4-10 euro/mo, Switzerland, end-to-end encryption focus), Migadu (20 euro/year unlimited mailboxes per domain, Switzerland), Tuta (3 euro/mo, Germany).

For a freelancer or small team that just needs you@yourdomain to work and read mail in Apple Mail, Thunderbird, or a phone, the cheapest option that fits your jurisdiction is the right answer. Migadu is excellent value for an agency with multiple domains.

To make it work, you change MX records on the domain to point at the provider, add their SPF/DKIM/DMARC records, done.

Option 2: forwarding only, no mailbox

If you only need to receive mail at you@yourdomain and you read it on your existing personal Gmail, you do not need a mailbox at all. You set up a forwarder: anything to you@yourdomain gets relayed to [email protected].

Many domain registrars include this for free. Cloudflare Email Routing is the cleanest free option: zero cost, works for any domain you have on Cloudflare, supports up to 200 forwarders per domain. You can set up hello@, info@, support@ as separate forwarders that all land in the same Gmail.

The catch: forwarding only handles incoming mail. To send mail showing your domain as the From address, you need either a managed mailbox (option 1) or a transactional sender (option 3). Sending from Gmail with a you@yourdomain From address is technically possible (Gmail "Send mail as") but breaks DMARC unless you also configure DKIM signing for the relayed mail, which most people skip and then complain about deliverability.

For a portfolio site, a side project, or a personal domain where you only get the occasional email, forwarding is the right answer. Free, 5 minutes of setup, no monthly cost.

Option 3: transactional email for app-generated mail

If your need is "the website sends password reset emails to users", you do not need a mailbox at all. You need a transactional email service: an SMTP relay that authenticates as your domain and delivers outgoing mail with high deliverability.

The leaders are Postmark (excellent reputation, 15 USD per 10k emails), SendGrid (cheaper at scale, more setup), Mailgun, Amazon SES (cheapest, more technical), Resend (modern, developer-friendly).

The integration is: your application talks SMTP to the provider with API key auth, the provider signs the mail with DKIM and sends it. You configure a couple of DNS records and you are done. Deliverability is professional-grade because the provider runs warmed-up IP pools and monitors reputation continuously.

For a typical WordPress site, the workflow is: install a small plugin (WP Mail SMTP, FluentSMTP), point it at Postmark or SES, the site's outgoing mail (password resets, order confirmations, comment notifications) goes through the relay instead of trying to send from the local server. Solves the deliverability problem in 10 minutes.

You can combine this with option 2: forwarding for inbound, transactional for outbound, no mailbox provider needed.

Option 4: self-host (only if you really know why)

If after reading the above you still want to run your own mail server, the modern stack is:

  • Mailcow or Mail-in-a-Box as the all-in-one stack (Postfix + Dovecot + Rspamd + SOGo + Roundcube, automated, sane defaults).
  • A VPS with reverse DNS you control and SMTP outbound enabled. Hetzner with a manually-requested unlock works. Some find OVH friendlier.
  • A clean IP. New IPs from the cheap-VPS pool often have residual spammer reputation. Buy from providers that let you check the IP on Spamhaus and similar before ordering.
  • Time. Plan to spend 1-2 hours a month on monitoring, plus the initial setup of 4-8 hours.

The valid reasons to self-host: legal/compliance requirements that need data on infrastructure you control, training/learning, philosophical preference for data sovereignty, very high volume (10k+ messages/day) where the per-message cost of a managed provider becomes significant.

The invalid reasons: "it should be free", "I don't trust Google", "how hard can it be". For all those there are option 2 and 3 covering 95% of the actual need at zero or near-zero cost.

A decision tree

If you are choosing now:

  • Personal domain, low volume, you read mail in Gmail anyway: Cloudflare Email Routing, free.
  • Freelancer or 1-3 person team: Fastmail, Migadu, or Mailbox.org. 3-5 euro per mailbox per month.
  • Small business with calendar and file collaboration: Google Workspace or Microsoft 365. 6 euro per user per month.
  • Web app sending transactional emails: Postmark or SES, plus option 1 or 2 for human mail.
  • Special compliance requirement, very high volume, or you want to learn: Mailcow on a clean VPS with proper monitoring.

The mistake is jumping straight to option 4 without considering the others. Self-hosting email is a 2026 hobby, not a 2026 default. Pick a managed solution that fits the case, save the time, write actual content for your site instead.