INBUXA 2026.10.6

Container image: registry.coffeylabs.org/inbuxa/inbuxa-server:2026.10.6 (linux/amd64, linux/arm64); also :latest.

Binaries for a host install are attached: inbuxa-linux-amd64.tar.gz and inbuxa-linux-arm64.tar.gz, with SHA256SUMS. Each is the binary out of this release's image for that architecture, so it is the same build. The image grants it cap_net_bind_service; a host install has to grant that itself (setcap, or AmbientCapabilities in the unit) to bind port 25.

Mirrored from the Gitea release; report issues on Gitea.

INBUXA 2026.10.5.1

Container image: registry.coffeylabs.org/inbuxa/inbuxa-server:2026.10.5.1 (linux/amd64, linux/arm64); also :latest.

Binaries for a host install are attached: inbuxa-linux-amd64.tar.gz and inbuxa-linux-arm64.tar.gz, with SHA256SUMS. Each is the binary out of this release's image for that architecture, so it is the same build. The image grants it cap_net_bind_service; a host install has to grant that itself (setcap, or AmbientCapabilities in the unit) to bind port 25.

Mirrored from the Gitea release; report issues on Gitea.

INBUXA 2026.10.5

Container image: registry.coffeylabs.org/inbuxa/inbuxa-server:2026.10.5 (linux/amd64, linux/arm64); also :latest.

Binaries for a host install are attached: inbuxa-linux-amd64.tar.gz and inbuxa-linux-arm64.tar.gz, with SHA256SUMS. Each is the binary out of this release's image for that architecture, so it is the same build. The image grants it cap_net_bind_service; a host install has to grant that itself (setcap, or AmbientCapabilities in the unit) to bind port 25.

Mirrored from the Gitea release; report issues on Gitea.

INBUXA 2026.9.30.2

Container image: registry.coffeylabs.org/inbuxa/inbuxa-server:2026.9.30.2 (linux/amd64, linux/arm64); also :latest.

Binaries for a host install are attached: inbuxa-linux-amd64.tar.gz and inbuxa-linux-arm64.tar.gz, with SHA256SUMS. Each is the binary out of this release's image for that architecture, so it is the same build. The image grants it cap_net_bind_service; a host install has to grant that itself (setcap, or AmbientCapabilities in the unit) to bind port 25.

Mirrored from the Gitea release; report issues on Gitea.

INBUXA 2026.9.30.1

Container image: registry.coffeylabs.org/inbuxa/inbuxa-server:2026.9.30.1 (linux/amd64, linux/arm64); also :latest.

Binaries for a host install are attached: inbuxa-linux-amd64.tar.gz and inbuxa-linux-arm64.tar.gz, with SHA256SUMS. Each is the binary out of this release's image for that architecture, so it is the same build. The image grants it cap_net_bind_service; a host install has to grant that itself (setcap, or AmbientCapabilities in the unit) to bind port 25.

Mirrored from git.coffeylabs.org/inbuxa/inbuxa-server/releases/tag/v2026.9.30.1; report issues on Gitea.

INBUXA 2026.9.29.2

Container image: registry.coffeylabs.org/inbuxa/inbuxa-server:2026.9.29.2 (linux/amd64, linux/arm64); also :latest. amd64 is published first; arm64 is added to the same tag when its build finishes, and :latest moves then.

Binaries for a host install are attached: inbuxa-linux-amd64.tar.gz and inbuxa-linux-arm64.tar.gz, with SHA256SUMS. Each is the binary out of this release's image for that architecture, so it is the same build. The image grants it cap_net_bind_service; a host install has to grant that itself (setcap, or AmbientCapabilities in the unit) to bind port 25.

Mirrored from git.coffeylabs.org/inbuxa/inbuxa-server/releases/tag/v2026.9.29.2; report issues on Gitea.

INBUXA 2026.9.20

The first tagged release of INBUXA, cut from the tree this project's own mail service moved onto on 20 September 2026.

Built on Stalwart 0.16.22. The version reports both:

$ inbuxa --version
2026.9.20 (Stalwart 0.16.22)

The base is in the string deliberately. Stalwart's data upgrades are one-way, so anyone upgrading needs to know which store format their data will be converted to.

Every feature, one edition

All nine features that upstream keeps for its Enterprise Edition are rebuilt clean-room and present in this build. There is no licence key, no seat count and no edition check, because there is nothing to check.

• Multi-tenancy — tenants with their own domains, administrators, quotas and queue visibility
• Masked email — per-sender disposable addresses that deliver to the account
• Undelete — deleted mail held for a set period and restorable
• Branding and templates — operator logo, and the text of calendar alarm and invitation mail
• AI spam classification — an optional local model as one spam signal, and a Sieve function. Off in a new install
• Monitoring — stored metrics and traces, a live trace view, and threshold alerts
• SCIM 2.0 provisioning — accounts and groups from an identity provider, to RFC 7643 and RFC 7644
• Scale-out storage — SQL read replicas, sharded blob and in-memory stores
• Per-domain directories — a domain signs in against its own LDAP, SQL or OIDC directory

Each was specified before it was written, from public documentation, the published standards and observed behaviour. The specifications are in docs/spec/features/, and the strip report for every upstream import is in docs/fork/strip-reports/.

Installing

Download the binary below, or build from source:

cargo build --release -p inbuxa

A server started with no configuration comes up in bootstrap mode. INBUXA Admin's setup wizard completes first boot over JMAP — the administrator, your domain, its DKIM keys, ACME certificates and a first mailbox. No web interface runs on the mail host, and none is fetched at first boot.

Full instructions: https://docs.inbuxa.org/install/fresh/

Not in this release

Two tools are specified and still to be built:

• The one-command installer (inbuxa deploy). Until it lands, install as above.
• The migration tool (inbuxa migrate). Migrating from Stalwart is a written procedure you run yourself — it is how this project's own cutover was done, in a 78-second window. See https://docs.inbuxa.org/install/migrating/

Licence

AGPL-3.0-only. 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. Stalwart is a trademark of Stalwart Labs LLC; INBUXA is not affiliated with or endorsed by them.