Mailu vs mailcow: two Docker mail servers compared

Mailu and mailcow compared on licence, install needs, built-in features and migration, with each claim sourced to each project's own docs or README.

By Shuki Vaknin 6 min read

Started as a Novell NetWare network administrator 35 years ago; system administrator and web developer for more than 25 years.


Mailu and mailcow are two free mail servers that both run as Docker containers. People often compare them with each other, and with Stalwart. They differ in how each project is licensed, what each one documents, and how each one is split into parts.

We run Stalwart in Jabali Panel, not Mailu or mailcow. Read this as a comparison by an interested party. We checked each product claim against that project’s own README, licence, website or documentation on 2026-11-21. Where we make a judgement, we label it as ours. For a wider list that also covers Stalwart and Mail-in-a-Box, see the best self-hosted email server.

The short answer

Choose mailcow if you want an e-mail suite with a web interface, you already run Docker Compose, and you want each mail function in its own container. mailcow describes itself as a groupware and e-mail suite based on Docker [1].

Choose Mailu if you want a set of Docker images with a web administration interface, and you plan to install it with Docker Compose or Kubernetes [6, 7, 9].

These two lines are our judgement, based on what each project says about itself. They are not a ranking.

Licence

Mailu is MIT-licensed. Its licence file begins “MIT License” [12]. Its README says that all components are “compatible with the MIT license”, and it describes its features as “all FOSS components” [11].

mailcow is licensed under the GNU General Public License version 3 [4]. Its README says that “Any part of mailcow itself is released under” GPL version 3 [3]. The same README says that “mailcow makes use of various open-source software” and asks you to check those licences before you use mailcow [3].

Our reading, not a vendor claim: the MIT licence places fewer conditions on reuse than GPL version 3. If licence terms matter for your use, have them checked before you deploy either one.

What each one is

Mailu describes itself as a “simple yet full-featured mail server” that runs “as a set of Docker images” [6]. Its README lists standard IMAP, SMTP and submission, aliases, domain aliases, custom routing, auto-reply, auto-forward, fetched accounts, managesieve, and DANE, MTA-STS, DKIM for outgoing mail, greylisting, DMARC and SPF checks [11]. It also lists webmail and an administration interface [11]. The feature list we read does not name a calendar or contacts component.

mailcow’s documentation says that “Each container represents a single application” [1]. Its component list includes Postfix for Internet mail, Dovecot for IMAP and POP, SOGo as an “Integrated webmailer and Cal-/Carddav interface”, Rspamd as the spam filter, and ClamAV as an “Antivirus scanner (optional)” [1]. The page also names the mailcow UI as the main web interface [1].

Our reading: mailcow shows more of its parts by name, and each part runs in a container you can inspect or restart. We did not find a Mailu page that lists its containers one by one, so this post does not compare container counts.

Installation and requirements

Mailu runs on Docker Compose or Kubernetes [7, 9]. Its Compose requirements page gives a minimum of 1 GB of memory and 1 GB of swap without ClamAV, and 3 GB of memory and 1 GB of swap with ClamAV [7]. The Compose setup needs Docker Compose v2 if you use the Compose flavour [7].

Mailu’s setup page says that “you should not run any critical mail server until” you have tested every feature [8]. Read that warning before you choose a server for real mail.

mailcow needs Docker 24.0.0 or later and Docker Compose 2.0 or later [2]. Its install page lists system packages, Docker and Docker Compose, and a quick installation section [2]. The install page does not give a memory figure, so this post does not compare memory needs for mailcow.

The Mailu pages we read are the master branch. They name 2024.06 as the stable branch [10]. We did not confirm the current Mailu release, so check the project’s release notes before you install.

What you get out of the box

Both products handle the core mail jobs: they accept mail, filter it, store it and serve it to clients.

Mailu’s README lists OpenPGP key publication through WKD, passkey sign-in to its webmail, and OAuth 2.0 for compatible mail clients [11]. Antivirus scanning and spam checks are built in [11].

mailcow’s SOGo component provides webmail with calendar and contacts access, and Rspamd and ClamAV run as separate services [1]. ClamAV is optional [1]. You can tune, replace or monitor each of these parts on its own.

Where Stalwart and Jabali Panel fit

Jabali Panel does not run mailcow or Mailu. It manages Stalwart 1.0.2 as its mail server [13]. If you want mailcow or Mailu, run it on its own server and point that domain’s mail records at it [13].

For the Stalwart comparisons, read Stalwart vs mailcow and Stalwart vs Mailu.

Migration between the two

Neither vendor documents a path that moves mail from one of these products to the other. The pages we read cover import into each product, not between them.

  • mailcow sync jobs copy or move existing e-mail “from an external IMAP server”, using imapsync [5].
  • Mailu documents importing an external mailbox from a filesystem Maildir. The steps are: create the domain and mailbox in the admin first, do not log in to the new mailbox before the import, stop Dovecot, and copy the external Maildir contents into the account’s legacy address directory. The page advises that you keep a backup of the source until the import is verified [10].

We do not give a migration recipe between the two. If you plan one, test it on a separate server first, with a copy of your mail.

Which one fits which job

These judgements are ours. They are based on the vendor pages above.

  • A team that already runs Docker Compose and wants each mail function visible in its own container: mailcow.
  • A team that wants a Docker-based server with a built-in admin and webmail, run with Compose or Kubernetes: Mailu.
  • A small virtual machine: check the Mailu memory figures before you choose. The 2 GB difference for ClamAV is significant on small hosts [7]. Decide early whether you need an antivirus scanner.
  • A hosting panel that manages DNS and SSL for your domains: Jabali Panel with Stalwart, which Jabali manages for you [13].

Common questions

Is Mailu free?

Yes. Mailu is MIT-licensed [12], and its README says all components are free software [11].

Does mailcow need Docker?

Yes. mailcow needs Docker 24.0.0 or later and Docker Compose 2.0 or later [2].

Can I run Mailu on Kubernetes?

Mailu’s docs include a Kubernetes setup page [9]. We did not test that setup.

Which one is better?

That depends on your team and your server. This page lists what each project says about itself. It does not rank them.

Sources and check dates

All sources were fetched on 2026-11-21.

  1. mailcow documentation, home page and component list: https://docs.mailcow.email/
  2. mailcow installation page, prerequisites: https://docs.mailcow.email/getstarted/install/
  3. mailcow README: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/master/README.md
  4. mailcow licence, GPL-3.0: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/master/LICENSE
  5. mailcow sync jobs: https://docs.mailcow.email/post_installation/firststeps-sync_jobs_migration/
  6. Mailu homepage: https://mailu.io/
  7. Mailu Docker Compose requirements: https://mailu.io/master/compose/requirements.html
  8. Mailu setup overview: https://mailu.io/master/setup.html
  9. Mailu Kubernetes setup: https://mailu.io/master/kubernetes/mailu/index.html
  10. Mailu maintenance, including importing an external mailbox: https://mailu.io/master/maintain.html
  11. Mailu README: https://raw.githubusercontent.com/Mailu/Mailu/master/README.md
  12. Mailu licence, MIT: https://raw.githubusercontent.com/Mailu/Mailu/master/LICENSE.md
  13. Jabali Panel blog: https://jabali-panel.com/blog/self-hosted-mail-server/ and https://jabali-panel.com/blog/best-self-hosted-email-server/ (checked 2026-11-21)