Forked on 11 November 2026Both AGPL-3.0

What changed compared to MailFlow

Plimail is a fork of MailFlow, the self-hosted unified webmail by Matt. It keeps MailFlow's mail engine and adds what we were missing, then removes what we did not need, so the whole thing is one image to run.

Why a fork

MailFlow lacked features and responsiveness we needed: no calendar, no encryption, and a crowded interface with many small buttons. Plimail was started to add those, on a stack small enough for one person to run and keep up to date.

The rule for Plimail is keep what is necessary, and keep the stack simple: one application image, a 60-line compose file, a 27-line .env.example, and no HTTPS machinery of its own beyond a self-signed fallback. A trusted certificate comes from the reverse proxy or tunnel you already run.

Plimail still takes fixes from MailFlow. The first release ported upstream's 12/24-hour clock, menus kept on screen, the collapsible attachment list, the undo-send switch, per-account notification mute and three IMAP sync fixes.

Side by side

MailFlow as of 4.3.1, the version Plimail forked from, against Plimail 1.1.0.

AreaMailFlowPlimail
Running it
ImagesTwo: a frontend image (Caddy or nginx) and a backend imageOne: the backend serves the built interface itself
ContainersFrontend, backend, PostgreSQL, RedisPlimail, PostgreSQL, Redis
HTTPSBuilt in: self-signed, or Let's Encrypt through the bundled CaddyHTTP on 3000 for your proxy, self-signed HTTPS on 3443
Setup files137-line compose file, 211-line .env.example, 771-line README60-line compose file, 27-line .env.example, short README
RepositoryAbout 1,660 filesAbout 1,100 files
LicenceAGPL-3.0, plus a paid commercial licence and a requested business licenceAGPL-3.0 only
Mail
Unified inbox, threads, search, rules, OAuthYesYes, same engine
Account setupNo autodiscovery: enter the server settingsFound from the address (autoconfig, Thunderbird ISPDB, SRV, MX)
Server-side filtersNoSieve over ManageSieve, plus out-of-office
Read receiptsNoRequest and answer (MDN, RFC 8098)
Import and exportSingle message as .emlFolders and selections as .mbox or .eml, import keeping dates and flags
Signature imagesNo uploadUpload, resize, sent inline
Spam filteringBuilt-in antispam filterLeft to your mail server
Privacy
OpenPGPNoAutomatic keys, PGP/MIME, Autocrypt, encrypted drafts and Send later, backup
Password-protected messagesNoYes, for recipients without PGP
Calendar and contacts
CalendarsNoCalDAV, invitations, answers, search
ContactsAddress book served over CardDAV, sync from external CardDAVAddress book served over CardDAV, contact groups; no external sync
Apps and interface
DesktopElectron appInstallable web app with mailto: handling and offline reading
MobileCapacitor Android appThe responsive web app
Themes242, dark and light, following the system if you like
ButtonsMany small onesFewer, bigger; the rest in a More menu
Languages1111
Extending and sign-in
PluginsPlugin platform, GTD pluginRemoved
IntegrationsTodoist, CardDAV contact syncRemoved
AIAssistant with OpenRouter and other providersSame, plus Claude, translate, scam check, proofreading, tones, writing style
Sign-inPassword, TOTP, OIDC, API tokensSame, plus passkeys and changing your own password
Counts come from the two repositories: MailFlow at the fork point and Plimail's main branch.

What was removed, and why

Each removal is a part we did not use and did not want to maintain. If you rely on one of them, MailFlow is the better choice.

Plugins and the GTD plugin

A platform to maintain for features we did not use. Plimail's additions went into the core instead.

Todoist and CardDAV contact sync

Integrations with outside services. The CardDAV server for your own contacts stays.

Built-in antispam and mailbox cleanup

Spam is filtered by the mail server. Sieve rules now run there too.

Electron and Android apps

On a computer, the installable web app does the job of the Electron one with no separate release.

Bundled Caddy and nginx

One image instead of two. Let's Encrypt is left to your own proxy or tunnel.

22 extra themes

One design in dark and light, matching the selfhostr family.

Thanks to MailFlow

Plimail would not exist without MailFlow and the work Matt and its contributors put into it: the IMAP engine, the sync model, the sanitizer and most of the interface come from there. Copyright in that code stays with its authors.

MailFlow is licensed under the GNU AGPL-3.0, and so is Plimail. The original notices are kept, and every change is listed in the NOTICE file. Internal names that installs depend on, such as MAILFLOW_* variables, the mailflow database and the volume names, are unchanged. MailFlow's commercial licence offer does not apply to Plimail.