Mailcow vs Mailu: When the Full Suite Makes Self-Hosted Email Worse
Greg Foster
September 18, 2026
Mailcow looks like the grown-up Docker mail server. SOGo for calendars, a busy admin, ClamAV, Rspamd, Oletools, a Redis, a pile of containers that feel like a product. Mailu looks like a subset: Postfix, Dovecot, webmail if you want it, fewer logos on the status page. People move from Mailu to Mailcow because they want “complete.” Completeness is how a homelab mail stack becomes worse at the only job that mattered: a small number of humans sending mail that arrives, and a stack you can restore on a Saturday.
I have run self-hosted email in production. I have also watched Mailcow installations that were technically impressive and operationally sad: 8 GB of RAM for three mailboxes, ClamAV chewing a NUC during a family backup window, SOGo fighting the Nextcloud that already held the contacts. The suite did not clear Gmail. It cleared the weekend.
What Mailcow is selling
Mailcow is an opinionated compose stack with a real admin UI. You get mailboxes, aliases, DKIM, quarantine, fail2ban-ish behavior, SOGo, optional webmail, antivirus, a monitoring feel. It is closer to a small-business appliance than Mailu. If you are leaving cPanel and you want one pane, Mailcow is the pane.
That pane has a cost. More containers mean more volumes, more upgrade notes, more ways a compose pull leaves you with a SOGo that will not talk to Dovecot until you read a GitHub issue. The admin UI hides some of that. It does not hide RAM. ClamAV alone is a hobby. If you turn it off, you still have the rest of the suite, and you still have people who installed Mailcow because the screenshot included ClamAV.
SOGo is the other gravity. CalDAV and CardDAV in the same product as IMAP is convenient until you already have Nextcloud or iCloud for that, and now you have two contact databases and a phone that syncs the wrong one. The full suite created a second source of truth. That is worse than a slimmer mail stack that refused to be your PIM.

What Mailu is selling
Mailu is still a lot of moving parts — it is mail — but it is easier to treat as “SMTP and IMAP in Docker” next to the rest of the homelab. You can skip webmail. You can keep calendars elsewhere. You will set more DNS by hand. You will not get SOGo for free. That lack is a feature if SOGo is not the job.
Mailu will not save you from a dirty IP. Neither will Mailcow. I will not repeat the deliverability sermon except to say: more containers do not warm a PTR. If you are choosing Mailcow to look more legitimate to Gmail, stop. Choose a relay or a clean IP. Choose the suite for operations, not for reputation.
When the full suite makes email worse
- RAM and CPU on a box that also does photos. Mailcow plus Immich plus Arr is how a mini PC becomes a heater and a 502 factory. Mailu is not tiny. It is smaller. On 8 GB shared, smaller is the difference between mail and a salvage night.
- Upgrade surface. Mailcow releases are frequent and documented. You will still read them. Mailu upgrades are also a project. The difference is how many services can disagree after the pull. I have seen SOGo-only breakage that made people think “mail is down” when IMAP was fine. The suite taught the household that the web UI is mail. When the UI is sick, they stop sending.
- Backup story. More volumes, more consistency requirements. A naive folder copy during a receive leaves you with a half-written maildir and a confident SOGo database. Mailu has the same class of problem with fewer pieces. Fewer pieces is a restore you can hold in your head.
- Security surface. Extra admin UIs and extra webapps are extra things on 443. Mailcow’s admin is powerful. Powerful and on the internet is a pair I dislike. Put it on Tailscale. People put it on the internet because the suite feels like a product that “should” be exposed. Mailu’s quieter admin gets the same treatment, but there is less to expose.
- Antivirus theatre. ClamAV on inbound personal mail from three relatives is a CPU bill for a threat model that is really “do not click.” If you need AV, you may not want to self-host mail at all. If you do not need AV, Mailcow still tempts you to leave it on because it was in the demo.

When Mailcow is the right heavier tool
Pick Mailcow if you are mail for a tiny org — a club, a five-person shop — and you want one admin to create mailboxes without SSH. Pick it if SOGo is actually the calendar you will use, and you do not already have Nextcloud. Pick it if you will give it a dedicated VM with 8–16 GB and a backup job that knows about all the volumes. Pick it if you like the UI enough to live in it weekly, not once at install.
I have been happy with Mailcow in those conditions. I have been unhappy when it was “the complete Mailu” on a shared NUC. Completeness is not a homelab virtue. Isolation is.
When Mailu is enough
Pick Mailu if you already have a PIM, you want compose next to the other stacks, and you can stand DNS by hand. Pick it if you have two to ten mailboxes and no desire to run SOGo. Pick it if the alternative is Mailcow and you cannot dedicate the RAM. Pick it if you will relay outbound anyway, because then the extra suite is not buying deliverability.
If you need an appliance checklist more than either Docker suite, that is a different product family. This comparison is the two compose religions. Do not add a third logo in the same weekend you migrate DKIM. Migrations are how you lose selectors and start over with Gmail.
Users, not containers, are the real load
Three mailboxes that send twenty messages a day do not need Oletools. Thirty mailboxes with a shared calendar and a boss who wants a web UI do. Mailcow’s suite maps to the second number. Homelab blog comments map to the first and then install the second anyway. I ask for the mailbox count and the PIM before I ask for the compose repo. If the answers are “four” and “Apple already syncs contacts,” Mailcow is vanity.
Logs are the other user. Mailcow will generate more of them. That is useful when you are hunting a reject. It is noise when you are hunting disk. I have filled a volume with mail logs and antivirus traces on a box that had 40 GB for everything. Mailu can do that too if you debug-log. Mailcow does it with the defaults looking helpful.
A migration I recommend against
Do not move Mailu to Mailcow because a Reddit thread said Mailcow is more “production.” Production is a PTR, a backup you have restored, and a number of services you can name while tired. Mailcow can be production. So can Mailu. The move itself is a deliverability event: new hosts, new keys if you slip, new web UI for users who had a bookmark. If Mailu sends and receives and you can restore it, stay. Add Nextcloud if you wanted calendars. Do not add a second mail stack to get calendars.
If Mailu is a mess — volumes you do not understand, a proxy that broke SMTP — Mailcow will not teach you mail. It will give you a nicer mess. Fix the DNS and the proxy, or leave self-hosted mail, before you collect suites.
Mailcow and Mailu are not the only self-hosted mail servers worth considering. Stalwart replaces most of the Docker suite with a single Rust program that runs in a few hundred megabytes of memory; how it compares with Mailcow on resources, webmail, spam filtering and upgrades is covered in Stalwart vs Mailcow.
How I choose
Dedicated VM, several users, one admin who is not me every day: Mailcow, ClamAV off unless I have a reason, admin not on the public internet, backup tested. Shared homelab, my family, Nextcloud already there: Mailu or a paid host. I still tell most households to pay Fastmail. I tell the ones who will not pay to pick the slimmer compose file unless they can point at the extra Mailcow service they will actually use.
I still tell operators to write the restore steps on a card: which volumes, which order, which DNS records if the hostname changes. Mailcow’s card is longer. If you will not write the card, you will not want the longer product. That is not an insult. It is a sizing tool.
The full suite makes self-hosted email worse when you cannot name why each container exists. Mailcow invites that. Mailu invites a different sin — too many knobs, not enough checklist — but it does not pretend to be your office suite. I would rather a mail stack that is only mail. The calendar can live. The antivirus can live. The admin can be small. Gmail will not be impressed either way. Your Saturday, and the person who has to restore it without you, will.