jcoffey-dev 64cddc9246 The switch reports every change as an event (LP-8)
Turning legacy mail protocols off or back on raises
security.legacy-protocols-changed (id 643, info level, also in the packaged
schema), with the scope (policy = server), the new value, who made the
change (accountId), whether listeners closed or reopened (details), which
ones (listenerId), and -- only when a listener could not be put back --
which and why (reason).

It is raised in Server::set_protocol_policy rather than by the JMAP
method, so whatever turns the switch is reported. A /set that changes
nothing -- the switch already where it was asked to be, nothing to close
or reopen -- is not a change and raises nothing.

The event is never an error, but jmap's exhaustive map from security
events to HTTP errors has to name it; it joins the other two that can't
occur there. rustfmt now also wraps LP-6's two over-long lines in
enums_impl.rs, which it flagged along with this change's.

tests/e2e/legacy_protocols.py now gives the server a stdout tracer and
reads events from the container's log: turning the switch off is exactly
one event naming the scope, value, author and listeners closed; setting it
off again raises none; turning it on is one event naming the listeners
reopened. It also proves LP-6's side: seven refused submission sign-ins
are seven auth.legacy-protocol-refused events, and there is no auth.failed
or auth.too-many-attempts among them. All checks pass.
2026-09-21 10:53:01 -07:00
2026-09-18 10:21:56 -07:00
2026-09-20 20:17:24 -07:00
2026-09-18 10:21:56 -07:00

inbuxa

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, and docs/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.

S
Description
Imported from github.com during the 2026-09-20 standup (local dir: inbuxa-server)
Readme
12 MiB
Languages
Rust 96.8%
Python 1.8%
HTML 1.2%