mailcow vs Mail-in-a-Box: two self-hosted mail setups

mailcow and Mail-in-a-Box compared on licence, install needs, DNS handling and extras, with each claim sourced to the vendor's own docs or licence file.

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: mailcow and Mail-in-a-Box. They take different routes. mailcow is a Docker stack, with each mail component in its own container. Mail-in-a-Box is an installer. It turns a fresh Ubuntu server into a mail server, and it takes over the domain’s DNS.

We run Stalwart in Jabali Panel. We do not run mailcow or Mail-in-a-Box, so read this as a comparison by an interested party. Product facts cite each vendor’s own homepage, documentation, README, licence or changelog, checked on 2026-11-21. Jabali facts come from the Jabali Panel repository. Judgements are labelled as ours.

The short answer

Choose mailcow if you already run Docker Compose, you want each mail component visible as its own container, and you want a web interface over the stack [3][4].

Choose Mail-in-a-Box if you want one dedicated Ubuntu server, you want the box to run its own DNS, and you accept that the box should not be changed after installation [5][6].

Licence

mailcow’s README says that the mailcow code is released under the “GNU General Public License, Version 3” [1]. Its LICENSE file is the GPL version 3 [2]. The README also says that mailcow uses other open-source software, so check the licence of each part you rely on [1].

Mail-in-a-Box is “made available per the CC0 public domain dedication” [5]. Its LICENSE file is CC0 1.0 Universal [8]. Running the installer uses scripts that get Let’s Encrypt certificates, so you must accept the Let’s Encrypt terms [5].

Judgement (ours): both licences are free to use. For most readers, the licence will not decide between the two.

What each one is

mailcow’s documentation calls it an open-source groupware and e-mail suite built on Docker [3]. It says that “Each container represents a single application” [3]. The components include Postfix for Internet mail, Dovecot for IMAP and POP, SOGo for webmail, calendars and contacts, Rspamd for spam, and ClamAV as an optional antivirus scanner [3].

Mail-in-a-Box says that “Technically, Mail-in-a-Box turns a fresh cloud computer into a working mail server” [5]. Its README lists Postfix, Dovecot, Nextcloud for CardDAV and CalDAV, Roundcube webmail, SpamAssassin, Postgrey and nsd4 DNS. It says the box sets SPF, DKIM, DMARC, DNSSEC, DANE TLSA and MTA-STS records automatically [7]. Its goals say it will not “make something customizable by power users” [7].

The main difference is the design. mailcow lets you see and change its parts. The docs describe customising Dovecot and the Dockerfiles [3]. Mail-in-a-Box gives you one set of choices, made for you [5][7].

Judgement (ours): a team that wants to tune or swap one component will find mailcow easier to work with. A single owner who wants fewer decisions will find Mail-in-a-Box closer to that.

Installation and requirements

mailcow needs Docker 24.0.0 or later and Docker Compose 2.0 or later [4]. Its system packages include git, openssl, curl and jq [4]. The install page we read gives no minimum memory figure [4].

Mail-in-a-Box needs the “Ubuntu 22.04 x64 (server edition)” operating system [6]. The guide asks for at least 512 MB of RAM and recommends 1 GB [6]. The machine “must be installed on a fresh machine that will be dedicated to Mail-in-a-Box” [6]. Containers and modified images are not supported [5].

The guide asks you to set reverse DNS at your cloud provider to the box’s hostname [6]. You add glue records and point the domain’s nameservers at the box [6]. The guide recommends letting the box take over DNS, and it covers external DNS as an advanced option [6]. Some registries need two glue records with different IP addresses, which a single-IP box cannot provide [6].

What you get out of the box

Both products accept, deliver, store and serve mail. The extras differ.

mailcow adds SOGo for webmail, calendars and contacts, Rspamd for spam, and an ACME container for Let’s Encrypt certificates [3]. A Watchdog container checks the status of the other containers [3].

Mail-in-a-Box adds Roundcube webmail and Nextcloud Contacts for contact and calendar sync [5]. It filters spam and uses greylisting [5]. Its control panel shows DNS and system status checks, and it supports TOTP two-factor login [5]. Its backups are encrypted. You must copy the encryption password file somewhere safe, because the backups cannot be decrypted without it [6].

Where Stalwart and Jabali Panel fit

Jabali Panel does not ship mailcow or Mail-in-a-Box. It ships Stalwart, and Stalwart 1.0.2 is the mail server listed in Jabali’s component docs [13]. The mail stack is Stalwart with Bulwark as the webmail client, served on mail. [14]. The mail module is optional and needs the DNS module active first [14]. The admin area shows DKIM, SPF, DMARC and MTA-STS state for each domain [15]. Mailboxes and forwarders are managed from the panel [16].

Stalwart describes itself as “One server for your email, calendars, contacts and shared files” [11]. Its README says that “About 85% of Stalwart’s features are free and open source under the AGPL-3.0”, and the rest are in the Enterprise edition [10]. The changelog’s 1.0.0 entry says existing v0.16.x deployments cannot be upgraded in place [12]. On Jabali Panel’s default mail layout, jabali update does that copy for you [13]. It now lists releases up to 1.1.1, dated 2026-11-16 [12].

For more on Stalwart against mailcow, read Stalwart vs mailcow.

Moving between the two

We found no vendor page that covers moving mail between these products. Two related facts exist. mailcow’s docs describe imapsync, which migrates or retrieves mail from remote mailboxes [3]. Mail-in-a-Box backups need the encryption key to restore [6]. Test any move on a copy of your data before you change DNS. Any such move is your own project, not a vendor-supported path.

Which one fits which job

The judgements below are ours. Neither vendor makes them.

  • A team that runs Docker Compose and wants each part visible: mailcow [3][4].
  • One dedicated Ubuntu server, one owner, and few settings to manage: Mail-in-a-Box [5][6][7].
  • A server that also hosts websites: the Mail-in-a-Box guide rules this out, because the machine must be dedicated [6]. We did not check mailcow for this case.
  • A panel that manages DNS, SSL and mail for your domains: Stalwart in Jabali Panel [13][14][15].

Common questions

Can I run Mail-in-a-Box on a server that also hosts websites?

The guide says the machine must be dedicated to Mail-in-a-Box [6]. The homepage says the box supports simple static hosting [5].

Does mailcow need Docker?

Yes. The install page lists Docker 24.0.0 or later and Docker Compose 2.0 or later [4].

Is Mail-in-a-Box still maintained?

Its changelog lists version 78, dated October 22, 2026 [9]. The homepage we fetched still shows version 76, dated May 24, 2026 [5]. The homepage says the maintainers work on it in their limited free time [5]. We cannot tell from these pages which is current, so check the releases on GitHub [7] before you plan an install.

Which one is better?

That depends on your team, your server and the jobs you need done. This comparison lists what each vendor says and what each one needs. It does not rank them.

Sources and check dates

All sources were checked on 2026-11-21.

  1. mailcow: dockerized README: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/master/README.md (checked 2026-11-21)
  2. mailcow: dockerized LICENSE: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/master/LICENSE (checked 2026-11-21)
  3. mailcow documentation: https://docs.mailcow.email/ (checked 2026-11-21)
  4. mailcow installation page: https://docs.mailcow.email/getstarted/install/ (checked 2026-11-21)
  5. Mail-in-a-Box homepage: https://mailinabox.email/ (checked 2026-11-21)
  6. Mail-in-a-Box setup guide: https://mailinabox.email/guide.html (checked 2026-11-21)
  7. Mail-in-a-Box README: https://raw.githubusercontent.com/mail-in-a-box/mailinabox/master/README.md (checked 2026-11-21)
  8. Mail-in-a-Box LICENSE: https://raw.githubusercontent.com/mail-in-a-box/mailinabox/master/LICENSE (checked 2026-11-21)
  9. Mail-in-a-Box CHANGELOG: https://raw.githubusercontent.com/mail-in-a-box/mailinabox/master/CHANGELOG.md (checked 2026-11-21)
  10. Stalwart README: https://raw.githubusercontent.com/stalwartlabs/stalwart/main/README.md (checked 2026-11-21)
  11. Stalwart homepage: https://stalw.art/ (checked 2026-11-21)
  12. Stalwart CHANGELOG: https://raw.githubusercontent.com/stalwartlabs/stalwart/main/CHANGELOG.md (checked 2026-11-21)
  13. Jabali Panel components: https://jabali-panel.com/docs/platform/components/
  14. Jabali Panel email docs: https://jabali-panel.com/docs/email/
  15. Jabali Panel admin docs: https://jabali-panel.com/docs/admin/
  16. Jabali Panel forwarders and mailboxes docs: https://jabali-panel.com/docs/user/forwarders/ and https://jabali-panel.com/docs/user/mailboxes/