Stalwart vs Postfix and Dovecot: one server or a stack

Stalwart against the classic Postfix and Dovecot mail stack: licence, moving parts, built-in features and the migration path in Stalwart's docs.

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 run your own mail, you choose between two designs. One is a single server that does SMTP, IMAP, JMAP and the calendar and contact protocols itself. The other is the classic stack: Postfix to move mail, Dovecot to serve mailboxes to clients, and the parts you add yourself, such as DKIM signing, spam filtering and webmail. This post compares those two designs. It does not pit one product against the other.

We use Stalwart in Jabali Panel, so read this as a comparison by an interested party. Jabali Panel ships Stalwart 1.0.2 [11]. We checked each product claim below against the vendor’s README, licence files, documentation, website and changelog, all checked on 2026-11-21. Postfix and Dovecot are separate projects with their own sites, so each is cited to its own source. Where we make a judgement, we say so.

The short answer

Choose Stalwart if you want one service for mail, calendars, contacts and shared files [3], and you can plan for the 1.0 upgrade if you run 0.16 [2].

Choose Postfix and Dovecot if you want each part as its own project, you already run them well, and you want to pick the signing, filtering and webmail parts yourself. This is our judgement.

Licence

Stalwart is dual-licensed. Its README says “This project is dual-licensed under the” AGPL-3.0 and the Stalwart Enterprise License v2 [1]. It also says “About 85% of Stalwart’s features are free and open source under the AGPL-3.0” [1]. Check the feature list before you rely on a feature you need [1]. For what each licence asks, see Stalwart Community vs Enterprise.

Postfix is also dual-licensed. Its LICENSE file says recipients can take the software under the Eclipse Public License 2.0 or the IBM Public License 1.0, whichever they choose [7].

Dovecot is under more than one licence. Its COPYING file says the code under src/lib, src/auth and src/lib-sql is MIT licensed, and “Everything else is LGPLv2.1” [10].

Our judgement: all three are free software licences. Read each licence text before you ship a product that bundles one of them.

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]. Its homepage says “One server instead of five.” [3] That is the vendor’s own description of the design.

Postfix’s home page says it is “Wietse Venema’s mail server” and that “Postfix attempts to be fast, easy to administer, and secure.” [6] It handles the SMTP side of mail. Our term for that role is mail transfer agent (MTA). The page does not use that term.

Dovecot’s home page describes Dovecot Community Edition as an email server [8]. Its documentation index lists pages for IMAP, POP3 and ManageSieve [9]. The index has no JMAP page [9].

Our judgement: in the classic stack, Postfix moves mail and Dovecot serves mailboxes. You then add the rest, and each part has its own config, logs and update cycle.

Installation and moving parts

Stalwart is one service. Mail, IMAP, POP3, JMAP and mailbox storage run in one process [1][11]. Jabali Panel runs it as the jabali-stalwart.service unit [13].

The classic stack has at least two services. Dovecot’s documentation index has a page titled “Postfix and Dovecot SASL” [9]. You set up and watch both services, and you keep their configs in step.

Our judgement: one service means fewer files to edit and fewer logs to read. The trade-off is that one fault can touch more of the mail path.

What you get out of the box

Stalwart’s README lists DMARC, DKIM and SPF checks in its SMTP server, plus ARC, POP3, IMAP and the calendar and contact protocols [1]. Its homepage says calendars, contacts and shared files sit “in the same server as the mail” [3].

The Postfix and Dovecot home pages we checked do not mention calendars, contacts, webmail, DKIM or spam filtering [6][8]. In a classic stack you add those parts as separate projects. That is our description of a common setup, not a vendor claim.

Where Stalwart sits in Jabali Panel

Jabali Panel runs Stalwart 1.0.2 [11]. The panel manages mailboxes, forwarders and each domain’s DKIM key and Stalwart domain entry [12].

A server still on Stalwart 0.16, with the default mail layout, moves to 1.0 when jabali update runs. The update copies the mail data with Stalwart’s migration tool into a new store while 0.16 keeps serving. Then Stalwart stops for the final copy and starts again on 1.0. If 1.0 does not start, the update switches back to 0.16 [12].

The 1.0.0 changelog entry says “existing v0.16.x deployments cannot be upgraded in place” [2]. That is why Jabali’s update uses a copy.

Moving from Postfix and Dovecot to Stalwart

Stalwart documents a path from a Dovecot and Postfix server. Its migration index lists “Dovecot and Postfix, including Mail-in-a-Box and mailcow” as a source for its proxy and Vandelay tools [4].

Its guide for that source covers configuring the new server, configuring the proxy, configuring the source server, starting the proxy, migrating accounts and finishing the move [5]. Vandelay is Stalwart’s import tool. The guide says “Vandelay reads each mailbox over IMAP” and uses a Dovecot master user to sign in to each account [5].

Our judgement: a move is a project of its own. Test it on a copy of your data and a second server first. Check delivery and retrieval from each client before you change the MX record. Stalwart’s guide covers the server side. It does not cover your DNS plan.

Which one fits which job

Our judgement, not the vendors’:

  • One server for mail, calendars and contacts on one host: Stalwart. If you run 0.16, plan the 1.0 upgrade first [2].
  • A team that wants to replace each part, or already runs Postfix and Dovecot well: keep the classic stack.
  • A hosting panel that manages mailboxes and the DNS records mail needs: Jabali Panel with Stalwart [12].
  • Commercial support: check each vendor’s support and licence terms on its own site.

Common questions

Do I need Dovecot if I use Stalwart?

No. Stalwart’s README lists IMAP and POP3 servers in the same program [1]. Run one mail server per host. Two servers on the same ports will conflict. That part is our judgement.

Is Stalwart free?

Most of its features are free and 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. Stalwart Community vs Enterprise covers the split in more detail.

Can I move accounts one at a time?

Stalwart’s migration index has a page titled “Migrating account by account” [4]. Its guide covers starting a proxy before the move [5]. Whether that fits your setup depends on your DNS and client settings. For a move into Jabali Panel, its own IMAP migration copies each mailbox over IMAP into Stalwart, one mailbox at a time, and needs an app password for the source account [14].

Which one is better?

This comparison does not rank them. It lists what each vendor says and where each part runs.

Sources and check dates

All sources were checked on 2026-11-21 unless stated.

  1. Stalwart README, licence split, protocols and features: https://raw.githubusercontent.com/stalwartlabs/stalwart/main/README.md
  2. Stalwart changelog, 1.0.0 entry: https://raw.githubusercontent.com/stalwartlabs/stalwart/main/CHANGELOG.md
  3. Stalwart homepage: https://stalw.art/
  4. Stalwart migration index: https://stalw.art/docs/migration/
  5. Stalwart guide for Dovecot and Postfix sources: https://stalw.art/docs/migration/guide/configure-source/dovecot-postfix/
  6. Postfix home page: https://www.postfix.org/
  7. Postfix LICENSE file, from the Postfix source tree: https://raw.githubusercontent.com/vdukhovni/postfix/master/postfix/LICENSE
  8. Dovecot home page: https://www.dovecot.org/
  9. Dovecot documentation index: https://doc.dovecot.org/
  10. Dovecot COPYING file: https://raw.githubusercontent.com/dovecot/core/main/COPYING
  11. Jabali Panel components table, Stalwart 1.0.2: https://jabali-panel.com/docs/platform/components/
  12. Jabali Panel email docs, including “Moving to Stalwart 1.0”: https://jabali-panel.com/docs/email/
  13. Jabali Panel services table, jabali-stalwart.service: https://jabali-panel.com/docs/admin/services/
  14. Jabali Panel migrations, IMAP mailbox migration into Stalwart: https://jabali-panel.com/docs/migrations/