jcoffey-dev
b73aa13fa3
tests/e2e/legacy_protocols.py boots the debug binary in a container, turns the switch off and on, and checks the ports themselves. Everything below it was unit-tested and none of it could have told us this worked. What it establishes: IMAP and POP3 stop answering while inbound SMTP, submission and JMAP keep going (LP-1, LP-2, LP-3); the listeners are saved whole (LP-1); a restart does not reopen them, which is the point of taking the objects away rather than only the sockets; both come back on their own without a restart (LP-5); savedListeners empties; and asking to close submission is overruled to false and reported, with 465 still answering (LP-21, acceptance test 18). wouldClose named imaps, pop3s and sieve, and those were exactly the three that closed (LP-16). One caveat about the method, because it nearly produced a false pass in reverse. A published Docker port accepts connections whether or not anything is listening in the container, so connecting proves nothing. The first run of this script reported IMAP still open after the switch, and that was the script being wrong, not the server. Each port now has to speak: a TLS handshake on 993, 995 and 465, a greeting on 25. It lives under tests/ because target/ is ignored and this is worth keeping. It derives its own root, needs Docker and a debug build, and clears its state directory first -- a half-bootstrapped one from an earlier run is no longer in bootstrap mode and the recovery admin stops working.
A complete mail and collaboration server, every feature included, under the AGPL
INBUXA is a mail and collaboration server: JMAP, IMAP, POP3, SMTP, CalDAV, CardDAV and WebDAV, in one Rust binary, with ihasmail as its web front end. It is a fork of Stalwart. Project site: inbuxa.org. Documentation: docs.inbuxa.org.
Stalwart ships some features only in a paid Enterprise Edition: multi-tenancy, masked email, undelete and others. INBUXA ships everything to everybody under the AGPL-3.0, rebuilding those features independently and without using any of Stalwart's Enterprise code.
What's different from Stalwart
- Every feature, one edition. No license key, no edition checks, no
upsell. See
docs/spec/SPEC.md§4 for the features being rebuilt, anddocs/spec/features/for each one's specification. - Webmail and administration by ihasmail, as a separate service that can run beside the server or elsewhere. Stalwart's own web interface is removed, so there's no web front end on the mail host.
- Clean-room rebuilds. Enterprise-only code is stripped from every
upstream release before it's imported. The rebuilt features are written
from specifications that use only public sources (
docs/spec/SPEC.md§3).
How the fork is kept
Upstream releases arrive as stripped snapshots, never with upstream's git
history, which contains Enterprise code. tools/fork/strip.py builds each
snapshot on top of upstream's own ossify.py, then verifies it independently.
The report for every import is in docs/fork/strip-reports/. See
docs/spec/SPEC.md §2.
Building
cargo build --release -p inbuxa # the binary is target/release/inbuxa
docker build -t inbuxa . # or the container image
Settings are read from INBUXA_* environment variables. An existing Stalwart
install's STALWART_* variables still work, with a warning to rename them.
New installs keep their data in /var/lib/inbuxa and logs in
/var/log/inbuxa. Existing installs keep the paths their configuration
already names, so none of their data moves.
License and credits
INBUXA is free software under the GNU Affero General Public License, version 3.
It is a fork of Stalwart, copyright © Stalwart Labs LLC, modified by Coffey Labs in 2026. Upstream's copyright notices are kept on every file they cover, and every upstream file this fork changed says so in its header, under the notice it came with. Stalwart's files are dual-licensed AGPL-3.0-only or Stalwart's Enterprise License, and INBUXA takes them under the AGPL-3.0 only. A few of those files also carry code from other projects under MIT or BSD licenses, which stays under those licenses; THIRD-PARTY.md lists it with its notices. "Stalwart" is Stalwart Labs' name. INBUXA isn't affiliated with or endorsed by Stalwart Labs.
The INBUXA mark reuses ihasmail's cat-and-envelope artwork.