Most WordPress sites start by sending email through the hosting server. Some eventually hit deliverability problems serious enough to migrate. Here is the honest comparison.

How most hosting handles email

Shared hosting providers typically run a shared mail server. Yourdomain.com email routes through the same IP address as hundreds of other domains. When one of those domains sends spam, the shared IP reputation suffers — and so does yours.

Symptoms of shared mail server problems:

  • Emails going to spam
  • Messages rejected by Google, Microsoft, or Apple
  • “550 SPF check failed” errors
  • IP blocklist entries on Spamhaus, UCEPROTECT, or Barracuda

This is not hypothetical. It happens to almost every shared hosting customer eventually.

Managed email services

A managed email service runs its own mail infrastructure with dedicated IP addresses, strict sending policies, and proper authentication (SPF, DKIM, DMARC).

Transactional email services

These send machine-generated emails: order confirmations, password resets, contact form notifications.

Postmark — the quality leader for transactional email. Charges per email (not per thousand), strict sending policies, excellent deliverability. Their server IPs have a clean reputation because they actively manage it. Starting at $25/month for 25,000 emails.

Amazon SES — the cheapest professional option. $0.10 per 1,000 emails. The catch: you need to warm up your sending, manage your own configuration, and handle bounces/complaints yourself. Excellent for high volume if you have the technical capacity to configure it properly.

Mailgun — good balance of price and ease of use. Free tier of 5,000 emails/month. Better deliverability than shared hosting out of the box.

SendGrid — the enterprise option. Free tier is marketing-focused (not transactional), but the paid plans are comprehensive. Email API plus marketing dashboard.

Professional email hosting (human-readable inbox)

For domain email (hello@yourdomain.com), a proper email host rather than the web host:

Google Workspace — £5–12/user/month. Gmail interface, excellent spam filtering, 30 GB of storage on the basic plan. Industry standard for professional email.

Microsoft 365 — similar price point to Google. Outlook/Exchange interface. Better if your team lives in the Microsoft ecosystem.

Proton Mail — end-to-end encrypted, EU-based. £4–9/month. Good privacy story. Less integration with third-party tools.

FastMail — independent, no advertising, no tracking. €5/month. Good technical reputation, owned by an individual rather than a large corporation.

Self-hosted email

Self-hosting your mail server means running Postfix, Exim, or a custom mail server on your VPS. This is technically possible but operationally difficult.

What self-hosting gives you:

  • Complete control over the mail server configuration
  • No per-email costs at scale
  • Full data residency (no third-party touching your email)

What self-hosting costs you:

  • IP reputation management — you need to warm up new IPs, monitor blocklists, and act quickly when problems arise
  • Daily operational attention — spam complaints, bounces, and authentication failures need monitoring
  • Deliverability expertise — getting mail reliably into Gmail/Outlook inboxes requires specialist knowledge
  • SSL certificate management for mail.subdomain

The technical complexity of self-hosted email has led most professionals to conclude it is not worth doing for most organisations. Even large companies with dedicated IT teams often use Google Workspace or Microsoft 365 rather than self-hosted.

When self-hosted email makes sense

Self-hosted email is worth considering when:

  • Your data cannot leave your jurisdiction (some government or regulated industry requirements)
  • You have an email engineer on staff or on retainer
  • You need complete infrastructure control for compliance reasons
  • You run a mail service (not just using email for your own domain)

For almost everyone else, the operational cost of self-hosted email exceeds the cost of a managed service.

The migration decision tree

Does your email need to land in inboxes reliably?
  NO → Use whatever your host provides
  YES →
    Is your email transactional (automated, machine-generated)?
      YES → Use Postmark, Amazon SES, or Mailgun
      NO → Is your team small (< 20 people)?
        YES → Google Workspace or FastMail
        NO → Microsoft 365

Migrating away from hosting-provider email

If you decide to move to a managed email service:

  1. Set up the new email service first (verify DNS records, send a test email)
  2. Update DNS (MX, SPF, DKIM) to point to the new service
  3. Do not cancel the old hosting email yet — keep it running for 2 weeks to catch anything that was addressed to old addresses
  4. Use an email migration tool (Google Workspace provides one, or use IMAPSYNC for smaller migrations)
  5. After confirming mail flows correctly, decommission the old hosting email

The DNS changes are the most critical and irreversible step. Do them carefully and verify mail flow before declaring the migration complete.