jcoffey-dev 9976d52e29
ci / github (pull_request) Skipped
ci / fork-checks (pull_request) Successful in 1m8s
ci / build (pull_request) Successful in 4m30s
github/ci (branch) GitHub Actions
Shared mailboxes: a second kind of account lock
A shared mailbox (support@, legal@) belongs to no one person: nobody
signs in to it, and the people assigned open it beside their own mail
at an access level an administrator chose. An account lock already is
most of that: it keeps receiving mail, refuses every sign-in, and its
delegates reach it through real grants on every container (so IMAP,
DAV and JMAP honor them), never including Share. So a shared mailbox is
a lock of a second kind (multi-account spec, MA-S; John, 2026-10-05).

Lock gains kind: "lock" (the default, so stored locks read as before)
or "sharedMailbox", set on create and fixed after. A shared mailbox:

- needs no reason to make, change or end;
- holds up to 100 people, where a lock holds 10;
- runs its own Sieve replies and redirects, so an automatic
  acknowledgement goes out (a lock answers no one);
- records only what is sent as it (audit_send_as, which now covers it),
  not AL-9's access and per-change records, which would bury the log
  for a busy desk;
- sends only as itself (MA-S3): From and Reply-To must be its own
  addresses, so answers come back to the mailbox and not to whoever
  replied; anything else is forbiddenFrom.

The session marks it delegation: {locked: true, kind: "sharedMailbox"},
so a front end that knows no kind still treats it as a lock. The
console's layout gains Management › Directory › Shared Mailboxes
(CustomComponent/SharedMailboxes).

Tests: the account lock suite now goes on to a shared mailbox: made
without a reason with twelve people, sign-in refused, the session's
kind, its vacation reply delivered, an answer sent as it and recorded
as the agent with no per-change records, and a Reply-To naming the
agent refused; a lock unit test reads a stored lock without a kind.
account_lock_tests, jmap_tests, audit_log_tests and imap_tests pass
(RocksDB).
2026-10-05 15:27:52 -07:00
2026-09-18 10:21:56 -07:00

inbuxa

A complete mail and collaboration server, every feature included, under the AGPL


Note

Development happens on git.coffeylabs.org/inbuxa/inbuxa-server; the copy on GitHub is a read-only mirror. Report issues at git.coffeylabs.org/inbuxa/inbuxa-server/issues, and join discussions at community.coffeylabs.org.

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 aren't read: the server stops at startup and names each one to rename. 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
A complete mail and collaboration server in one Rust binary: JMAP, IMAP, POP3, SMTP, CalDAV, CardDAV and WebDAV, every feature included, under the AGPL.
Readme LicenseRef-SEL AGPL-3.0-only
19 MiB
0 Stars 1 Watchers 0 Forks
2026-10-06 15:29:51 +00:00
Languages
Rust 97%
Python 2.2%
HTML 0.7%