Stalwart vs Mailu: two self-hosted mail servers compared

Stalwart and Mailu compared on licence, install requirements, upgrade path and features, each claim sourced to the vendor docs and licence files.

By Shuki Vaknin 7 min read

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


If you want to run your own mail server, two free options come up often: Stalwart and Mailu. They take different routes. Stalwart is one Rust server that speaks the mail protocols itself [1][5]. Mailu is “a set of Docker images” [10].

We use Stalwart in Jabali Panel, so read this as a comparison by an interested party. Jabali Panel does not run Mailu [19]. We checked each product claim below against the vendor’s README, licence files, documentation, website and release notes on 2026-11-21. Where we make a judgement, we say so. For mailcow, see Stalwart vs mailcow. For four options side by side, see the best self-hosted email server.

The short answer

Choose Stalwart if you want one server for mail, calendars, contacts and shared files [4], and you can plan for its 1.0 upgrade path [3].

Choose Mailu if you want a set of Docker images with a web administration interface, and components that are MIT-compatible [10][11].

Licence

Stalwart is dual-licensed. Its README says “This project is dual-licensed under the” AGPL-3.0 and the Stalwart Enterprise License v2 (SELv2) [1][2]. The README also says “About 85% of Stalwart’s features are free and open source under the AGPL-3.0”, and that the rest make up the Enterprise edition [1]. The README describes the SELv2 as “a proprietary license designed for commercial use” [1]. Check the feature list before you rely on a feature you need.

Mailu’s README says it is free software, and that its components are “compatible with the MIT license” [10]. The LICENSE file in the Mailu repository is the MIT License [11].

What each one is

Stalwart’s README describes it as a mail and collaboration server, with JMAP, IMAP4, POP3, SMTP, CalDAV, CardDAV and WebDAV support [1]. The homepage says “One server instead of five.” [4] That is the vendor’s own description of the design.

Mailu’s README opens with “Mailu is a simple yet full-featured mail server as a set of Docker images.” [10] Its feature list covers IMAP, SMTP and submission, webmail, an administration interface, aliases, auto-reply, forwarding, managesieve, greylisting, DMARC and SPF checks, and an anti-virus scanner [10]. The README does not list calendar or contact features [10]. Mailu’s FAQ describes a WebDAV service, Radicale, for calendars and address books [15], and its configuration reference lists a WebDAV address [16]. Mailu’s FAQ names Postfix, Dovecot, Nginx and Rspamd as the services whose configuration files you can override [15].

Our judgement: a single server has fewer parts to watch, but one fault affects more of the stack. A set of containers lets you inspect and replace each part, but you need Docker, and you need to understand how the parts connect.

Installation and requirements

Stalwart’s install page lists several routes: an installation script on Linux, macOS and FreeBSD, a Docker or other OCI container image, and a Windows binary run as a service [5]. Its release binaries cover Linux (x86_64, aarch64, ARMv7 and ARMv6), macOS, FreeBSD (x86_64) and Windows (x86_64) [6]. The requirements page says “A mail server depends more on its network than on its hardware.” It then covers the network, memory, CPU, disk and outbound connections [6]. Read its memory section before you size a host. We did not copy its figures into this post.

Mailu’s Docker Compose requirements page says “The minimal required memory and swap are:” 3GB of memory and 1GB of swap when it runs ClamAV, and 1GB of memory and 1GB of swap without it [12]. The host must not listen on ports such as 25, 80, 443 and 587, because Mailu’s services use them [12]. Mailu’s Docker Compose setup generates a docker-compose.yml and a mailu.env with its setup utility, and you then start it with docker compose up -d [13]. Mailu’s docs also have a separate Kubernetes setup page [17].

On upgrades, the Stalwart changelog says the 1.0.0 release (2026-10-26) includes breaking changes, and “existing v0.16.x deployments cannot be upgraded in place” [3]. The latest Stalwart release in our check is v1.1.1, published 2026-11-16 [3][9]. Mailu’s master docs say its 2024.06 branch “features the most recent stable version” [17]. The latest GitHub release we found is tag 2024.06.71, published 2026-11-19 [18].

What you get out of the box

Both products handle the core mail jobs: accepting mail, delivering it, storing mailboxes and serving clients.

Stalwart’s README lists DMARC, DKIM, SPF and ARC checks in its SMTP server, MTA-STS and DANE support, and automatic TLS certificates through ACME [1]. Its spam filter is built in, with DNS blocklist checks, greylisting and a Pyzor digest option [1]. Calendars, contacts and shared files come with the server [1][4].

Mailu’s README lists aliases, auto-reply, forwarding, fetched accounts, outgoing DKIM, DMARC and SPF checks, greylisting, an anti-virus scanner and Let’s Encrypt support [10]. Its webmail can be Roundcube or SnappyMail, and calendar and contact sync runs through the WebDAV service described above [15][16].

Where Stalwart sits in Jabali Panel

Jabali Panel runs Stalwart with Bulwark webmail [19]. Jabali Panel ships Stalwart 1.0.2 [20]. A server still on 0.16, with the default mail layout, moves to 1.0 when jabali update runs, which copies the mail into a new store [20]. The panel creates DKIM keys for each domain and publishes them into the hosted DNS zone [19]. Its Mail Deliverability page shows DKIM, SPF, DMARC and MTA-STS state for each domain [19].

Jabali Panel does not run mailcow, Mailu or Mail-in-a-Box [19]. If you want Mailu, run it on its own server and point that domain’s mail records there.

Migration between the two

Neither vendor’s pages that we checked describe a direct path between Stalwart and Mailu.

Stalwart’s migration docs describe Vandelay, which imports an account from a source reached over IMAP or other protocols, or from a Maildir tree. It then writes the account to a JMAP server such as Stalwart [8]. Mailu’s command line has a user-import command, and its docs say that “password is being imported as a hash” [14].

These are separate tools, not a tested route between the two products. If you plan a move, test it on a separate server first, with a copy of your data.

Which one fits which job

Our judgement, not the vendors’:

  • One server for mail, calendars and contacts, on a single host: Stalwart. If you run 0.16, plan the 1.0 upgrade first.
  • A team that wants Docker images, a web admin interface and MIT-compatible components: Mailu.
  • A hosting panel that also manages DNS and SSL for your domains: Jabali Panel with Stalwart.
  • A need for commercial support: check each vendor’s support and licence terms on its own site before you decide.

Common questions

Is Stalwart free?

About 85% of its features are open source under AGPL-3.0. The rest are in the Enterprise edition, under the SELv2 [1]. Check the feature list for the features you need.

Is Mailu free?

Mailu calls itself free software, and its components are compatible with the MIT license [10]. Its LICENSE file is the MIT License [11].

Does Mailu need Docker?

Mailu is “a set of Docker images” [10]. Its docs cover Docker Compose and Kubernetes setups [13][17].

Which one is better?

This comparison does not rank them. It lists what each vendor says about its product and where its parts run.

Sources and check dates

All sources were checked on 2026-11-21.

  1. Stalwart README, licence split and feature list: https://raw.githubusercontent.com/stalwartlabs/stalwart/main/README.md
  2. Stalwart licence texts, AGPL-3.0 and SELv2: https://raw.githubusercontent.com/stalwartlabs/stalwart/main/LICENSES/AGPL-3.0-only.txt and https://raw.githubusercontent.com/stalwartlabs/stalwart/main/LICENSES/LicenseRef-SEL.txt
  3. Stalwart changelog, 1.0.0 and later entries: https://raw.githubusercontent.com/stalwartlabs/stalwart/main/CHANGELOG.md
  4. Stalwart homepage: https://stalw.art/
  5. Stalwart install documentation: https://stalw.art/docs/install/
  6. Stalwart system requirements and supported platforms: https://stalw.art/docs/install/requirements/
  7. Stalwart 0.16 to 1.0 upgrade guide: https://stalw.art/docs/migration/upgrade-0-16/
  8. Stalwart migration index, including Vandelay: https://stalw.art/docs/migration/
  9. Stalwart latest release, v1.1.1 (2026-11-16): https://github.com/stalwartlabs/stalwart/releases/tag/v1.1.1
  10. Mailu README: https://raw.githubusercontent.com/Mailu/Mailu/master/README.md
  11. Mailu licence, MIT: https://raw.githubusercontent.com/Mailu/Mailu/master/LICENSE.md
  12. Mailu Docker Compose requirements, 2024.06 branch: https://mailu.io/2024.06/compose/requirements.html
  13. Mailu Docker Compose setup, 2024.06 branch: https://mailu.io/2024.06/compose/setup.html
  14. Mailu command line reference, 2024.06 branch: https://mailu.io/2024.06/cli.html
  15. Mailu FAQ, 2024.06 branch: https://mailu.io/2024.06/faq.html
  16. Mailu configuration reference, 2024.06 branch: https://mailu.io/2024.06/configuration.html
  17. Mailu setup page, master branch: https://mailu.io/master/setup.html
  18. Mailu latest release, tag 2024.06.71 (2026-11-19): https://github.com/Mailu/Mailu/releases/tag/2024.06.71
  19. Jabali Panel blog, origin-checked posts: https://jabali-panel.com/blog/stalwart-mail-hosting-panel/, https://jabali-panel.com/blog/self-hosted-mail-server/, https://jabali-panel.com/blog/debian-hosting-control-panel/, https://jabali-panel.com/blog/best-self-hosted-email-server/
  20. Jabali Panel components table: https://jabali-panel.com/docs/platform/components/