Skip to content
Sign inGet startedDashboard

BlogSelf-hosted email

Self-hosted email vs managed hosting: the work you take on

By Julien CoulaudPublished July 27, 2026Updated October 15, 20265 min read

You can run your own mail server in 2026. Mailcow and similar projects install in an afternoon, and a small server costs less than most hosted plans. The work starts after the first test message goes out. Here is that work, with a source for each claim, so you can decide with real numbers.

Julien Coulaud

Founder of Shipmail. Building business email hosting for solo founders and small teams.

  • Self-hosted email
  • Email hosting
  • Deliverability
  • Custom domain email

Short answer

Self-host email if you know Linux and DNS, want full control of your data, and can live with occasional delivery problems. Pay a managed host if missed mail costs you money and nobody wants a mail server as a second job. The software is free. Your hours go into port 25, sender reputation, updates and backups.

Self-hosted email vs managed hosting

ApproachCost shapeWho runs the mail systemBest fit
DIY mail server[1]A server with 6 to 8 GiB of RAM, plus your timeYou, including updates, backups and delivery problemsPeople who know Linux and DNS and want full control
Managed email hostA monthly subscriptionThe provider runs the servers; you manage users and DNSBusinesses where a lost message has a real cost
ShipmailSources[12]Shipmail pricing[13]Shipmail security$4 a month for 2 mailboxesShipmail runs the servers; you keep your domain and DNSCustom-domain email without a mail-server job

What you gain by self-hosting

Self-hosting gives you things no provider sells. You hold every message on disk you control. You choose the spam rules, the retention and the logs. Extra mailboxes and domains cost nothing. For a technical person who enjoys it, that is a fair trade.

The cost is time, and it arrives in bursts. Most weeks the server just runs. Then a blocklist entry, a full disk or an expired certificate takes an evening, often when you are busy with something else.

What running a mail server involves

Running a mail server means getting port 25 and a clean IP, publishing SPF, DKIM, DMARC and PTR records, filtering spam, and handling monitoring, updates and backups. Routine checks take minutes, but failures take hours.Sources[2]AWS: Amazon EC2 restriction on email sent using port 25[3]Hetzner Cloud FAQ: blocked mail ports[4]DigitalOcean: why is SMTP blocked?[5]Spamhaus Policy Blocklist (PBL)[7]Gmail email sender guidelines[8]Yahoo Sender Hub best practices[9]Microsoft: Outlook's requirements for high-volume senders[1]mailcow: system requirements

  1. Step 1

    Port 25 and IP reputation

    Many hosts block outbound port 25 by default. Spamhaus lists home and broadband IP ranges in its Policy Blocklist, so a server at home rarely delivers. Pick a host that lets you send, and check its IP first.

  2. Step 2

    SPF, DKIM, DMARC, PTR and TLS

    Gmail requires every sender to have SPF or DKIM, matching forward and reverse DNS (PTR), and TLS. Bulk senders to Gmail, Yahoo and Outlook.com also need DMARC; Gmail and Outlook.com set the line at 5,000 messages a day.

  3. Step 3

    Spam and abuse filtering

    Tune inbound filters so wanted mail gets through. Watch outbound abuse too: one hacked password can get your IP blocklisted. Gmail asks senders to keep their spam rate below 0.3%.

  4. Step 4

    Monitoring and incident response

    Watch the mail queue, disk space, certificate expiry and bounce messages. Decide who fixes it when it breaks while you travel.

  5. Step 5

    Updates and security

    Patch the operating system and the mail stack, renew certificates and rotate passwords. Mailcow alone needs 6 GiB of RAM plus swap, more for 5 or more users.

  6. Step 6

    Backups and recovery

    Back up messages, DKIM keys and configuration. Restore from a backup once before you need to, so you know it works.

  7. Step 7

    Migration and continuity

    Keep a written list of mailboxes, aliases and DNS records. If the server dies, that list decides how fast you can move to another one.

  8. Step 8

    Administrator time

    Routine checks take minutes. Failures take hours and need someone who understands SMTP, DNS and Linux.

Sources[2]AWS: Amazon EC2 restriction on email sent using port 25[3]Hetzner Cloud FAQ: blocked mail ports[4]DigitalOcean: why is SMTP blocked?[5]Spamhaus Policy Blocklist (PBL)[7]Gmail email sender guidelines[8]Yahoo Sender Hub best practices[9]Microsoft: Outlook's requirements for high-volume senders[1]mailcow: system requirements

Port 25 is blocked on most clouds

AWS EC2, Hetzner Cloud and DigitalOcean all block outbound mail ports on new servers by default. AWS and Hetzner let you ask for the block to be removed.Sources[2]AWS: Amazon EC2 restriction on email sent using port 25[3]Hetzner Cloud FAQ: blocked mail ports[4]DigitalOcean: why is SMTP blocked?

  • AWS EC2 blocks outbound port 25 to public addresses by default. You can request removal.
  • Hetzner Cloud blocks ports 25 and 465 on every new server. You can ask to unblock them after one month and a paid invoice.
  • DigitalOcean blocks SMTP ports 25, 465 and 587 on Droplets.
Sources[2]AWS: Amazon EC2 restriction on email sent using port 25[3]Hetzner Cloud FAQ: blocked mail ports[4]DigitalOcean: why is SMTP blocked?

A common middle path is to self-host the mailboxes and send outgoing mail through a paid relay. The mail stays on your server, and the relay's IP reputation gets your mail delivered. You pay a second bill and secure a second account.

Passing every DNS check does not guarantee the inbox

SPF, DKIM, DMARC and PTR prove the message is yours. Gmail and Outlook still decide where it lands, using your IP's history, your spam rate and signals they do not publish. A new server on a fresh IP has no history.Sources[7]Gmail email sender guidelines[9]Microsoft: Outlook's requirements for high-volume senders

These are two people, not a failure rate. Plenty of people run their own mail for years without trouble. A managed host does not guarantee the inbox either. It shares the reputation work across many customers.

When self-hosting is the right call

Self-hosting is the right call when you already run Linux servers, need the data on hardware you control, and a lost message would be an annoyance rather than a lost client.

  • You already run Linux servers and know DNS, TLS and backups.
  • You need the data on hardware you control, for a legal or personal reason.
  • Your mail is personal or low-stakes, and a lost message is an annoyance, not a lost client.
  • You are happy to pay a relay for outgoing mail.
  • You enjoy it. That counts.

When managed hosting is safer

Managed hosting is safer when a missed invoice, password reset or client reply costs you money, or when nobody on the team wants to be on call for a mail server.

  • A missed invoice, password reset or client reply costs you money.
  • Nobody on the team wants to be on call for a mail server.
  • Several people share addresses like support@ and need to see who answered.
  • You want backups to be someone else's job.

You still own your domain, your DNS, your passwords and what you send. You stop owning the servers.

Where Shipmail fits

Shipmail is managed email on your own domain, from $4 a month for 2 mailboxes. Shipmail runs the servers, outgoing delivery, spam filtering, updates and backups. The servers are in Germany. Messages and backups are stored encrypted.Sources[12]Shipmail pricing[13]Shipmail security

You keep the domain and the DNS account. IMAP keeps the mail portable, so you can leave the way you arrived. Shipmail gives you the SPF, DKIM and DMARC records and checks them, but does not promise that every message will reach the inbox. That still depends on what you send.Sources[14]Shipmail custom-domain setup guide[13]Shipmail security

Shipmail is not end-to-end encrypted. Its servers can read stored mail to filter and search it. If you self-host because nobody else may hold the keys, Shipmail is the wrong fit.[13]

Moving from your own server without changing your address

To move from your own server without changing your address, keep the old server running while you switch the DNS records to Shipmail, create the same mailboxes and aliases, and import the old mail over IMAP or from an MBOX export.Sources[15]Shipmail provider-switch guide[16]Shipmail mailbox import documentation

  1. Step 1

    List what you run

    Write down every mailbox, alias, forward and Sieve rule on the old server.

  2. Step 2

    Publish the new DNS records

    Keep the old server running. Add the domain to Shipmail, replace the MX record and the SPF, DKIM and DMARC records, and wait for verification.

  3. Step 3

    Create the addresses and copy mail

    Once the domain verifies, create the same mailboxes and aliases. Import the old mail over IMAP, or upload an MBOX export.

  4. Step 4

    Test both directions

    Send to and from Gmail and Outlook addresses. Check the From line, replies and every alias.

  5. Step 5

    Retire the old server

    Run a final import, keep one backup, then shut the server down and revoke its credentials.

Sources[15]Shipmail provider-switch guide[16]Shipmail mailbox import documentation
Sources16 sourcesVerified 2026-10-15
  1. [1]
    mailcow: system requirements

    mailcow's minimum is 6 GiB of RAM plus 1 GiB of swap with the default configuration, a 1 GHz CPU and 20 GiB of disk excluding email. 8 GiB of RAM is recommended for about 5 to 10 users. Incoming TCP 25 must be open, and the MTA connects out on TCP 25 and 465.

    docs.mailcow.email · 2026-10-15

  2. [2]
    AWS: Amazon EC2 restriction on email sent using port 25

    By default, Amazon EC2 allows outbound traffic over port 25 only to private IPv4 addresses; traffic over port 25 to public IPv4 and IPv6 addresses is blocked. Customers can request that the restriction be removed.

    docs.aws.amazon.com · 2026-10-11

  3. [3]
    Hetzner Cloud FAQ: blocked mail ports

    Hetzner blocks ports 25 and 465 by default on all cloud servers. After a customer has been with Hetzner for a month and paid the first invoice, they can submit a limit request explaining the use case; port 587 is not blocked.

    docs.hetzner.com · 2026-10-15

  4. [4]
    DigitalOcean: why is SMTP blocked?

    SMTP ports 25, 465 and 587 are blocked on Droplets to prevent spam and abuse, including traffic through a Reserved IP. DigitalOcean recommends a third-party email service provider for sending.

    docs.digitalocean.com · 2026-10-15

  5. [5]
    Spamhaus Policy Blocklist (PBL)

    The PBL lists end-user IP address ranges from which email should never be sent directly to the final destination, often ranges ISPs assign to broadband or dial-up customers, dynamic or static.

    spamhaus.org · 2026-10-15

  6. [6]
    Xfinity: why is port 25 for email submission not supported?

    Comcast does not support port 25 for the transmission of email by its residential internet customers, and recommends port 587 with TLS/SSL enabled.

    xfinity.com · 2026-10-11

  7. [7]
    Gmail email sender guidelines

    Since February 1, 2024, all senders to Gmail need SPF or DKIM, valid forward and reverse DNS, TLS, RFC 5322 formatting, and a Postmaster Tools spam rate below 0.3% (best practice below 0.1%). Senders of more than 5,000 messages a day also need SPF, DKIM and DMARC (policy may be none), a From domain aligned with SPF or DKIM, and one-click unsubscribe for marketing and subscribed mail. Messages of the same category should have the same From address, display names should be a consistent and accurate statement of the sender's identity, and subject lines should not start with Re: or Fwd: unless the message is a real reply or forward. The page does not mention no-reply addresses.

    support.google.com · 2026-10-11

  8. [8]
    Yahoo Sender Hub best practices

    Yahoo asks bulk senders to implement SPF and DKIM, publish a DMARC policy of at least p=none that passes, support one-click unsubscribe for marketing and subscribed mail, honor unsubscribes within 2 days, and keep the spam rate below 0.3%.

    senders.yahooinc.com · 2026-10-11

  9. [9]
    Microsoft: Outlook's requirements for high-volume senders

    Microsoft's April 2025 announcement that Outlook.com requires SPF, DKIM and DMARC (at least p=none, aligned with SPF or DKIM) from domains sending more than 5,000 emails a day, starting May 2025.

    techcommunity.microsoft.com · 2026-10-11

  10. [10]
    Hacker News comment on administrator time and vanished mail

    A former self-hoster said, "Being a full-time email administrator is a job I will never do again unless I'm getting paid for it," and described outgoing mail that would "just ... vanish" with delivery that felt "like 50/50."

    news.ycombinator.com · 2026-07-27

  11. [11]
    Hacker News comment on authenticated mail going to spam

    A self-hoster reported that mail went "straight to spam" after configuring SPF, DMARC, DKIM, reverse DNS, and checking the IP against reputation lists.

    news.ycombinator.com · 2026-07-27

  12. [12]
    Shipmail pricing

    Shipmail plan prices, mailbox limits, team access, and send limits.

    shipmail.to · 2026-10-15

  13. [13]
    Shipmail security

    Shipmail security page: core infrastructure hosted in the EU, in Germany; TLS in transit; messages and attachments stored encrypted at rest. Shipmail is not end-to-end encrypted: its servers can decrypt stored mail.

    shipmail.to · 2026-10-15

  14. [14]
    Shipmail custom-domain setup guide

    Shipmail guide to DNS verification, mailbox creation, and domain cutover.

    shipmail.to · 2026-10-05

  15. [15]
    Shipmail provider-switch guide

    Shipmail guide to inventorying addresses, migrating mail, updating MX and authentication records, testing, and keeping a rollback path.

    shipmail.to · 2026-07-27

  16. [16]
    Shipmail mailbox import documentation

    Shipmail documentation for connected and file imports, selection options, storage checks, progress, skipped items, and repeat imports.

    shipmail.to · 2026-10-15

Questions worth answering

Common questions about self hosted email alternative.

Is self-hosting email worth it?
For personal mail and people who enjoy running servers, often yes. For business mail where a lost message costs money, usually no. The software is free, but your time goes into delivery problems, updates and backups.
Why are my self-hosted emails going to spam?
Common causes are a missing PTR record, an IP on a blocklist such as the Spamhaus PBL, or a new IP with no sending history. Check SPF, DKIM, DMARC and reverse DNS first, then the IP's reputation.Sources[7]Gmail email sender guidelines[5]Spamhaus Policy Blocklist (PBL)
Can I run a mail server at home?
You can receive mail, but sending usually fails. Spamhaus lists ISP broadband ranges in its Policy Blocklist, and ISPs such as Xfinity do not support port 25 for home customers. Most home setups send through a relay.Sources[5]Spamhaus Policy Blocklist (PBL)[6]Xfinity: why is port 25 for email submission not supported?
How much RAM does a self-hosted mail server need?
Mailcow lists 6 GiB of RAM plus 1 GiB of swap as its minimum, and recommends 8 GiB for about 5 to 10 users. Lighter stacks need less, but spam filtering uses most of the memory.[1]
Can I move from my own server to Shipmail without changing my address?
Yes. The address belongs to your domain. Publish Shipmail's DNS records, wait for verification, create the same mailboxes, then import the old mail over IMAP or from an MBOX file.Sources[15]Shipmail provider-switch guide[16]Shipmail mailbox import documentation

Related guides

More on Shipmail pricing, comparisons, and team workflows.

Email, newsletters and booking pages on your own domain, in one plan.

Get started for free