Coming in January 2027
What’s coming in 27.1
27.1 is the first inbuxa series: one version number for the server, inbuxa Admin, inbuxa Webmail, the installer, the CLI and inbuxa-migrate. After it, a new series comes every January and July.
Updated 13 November 2026
Everything below is in the 27.1 release candidates today, and our own mail runs on
them. Candidates are opt-in and never latest. Their notes are on the
releases page.
A mail server with no open mail port
- inbuxa Relay. Put a small relay on a public machine. It takes mail in on port 25 and sends your mail out, and your server never opens a mail port to the internet. The server dials out to the relay and manages it.
- While the link is up, your server’s spam filter, directory and rules answer each sender during their session. While it’s down, the relay holds your mail, encrypted to the server’s key, until the link is back.
- Outgoing mail through a relay keeps DKIM, DANE, MTA-STS, REQUIRETLS and TLS-RPT. The server publishes the relays in MX and SPF where it manages DNS.
- A relay gets its own certificate, or uses one of the server’s, a wildcard say. Upgrades are signed and pushed from inbuxa Admin.
Moving in, and moving out
- Move a whole domain in from inbuxa Admin. From IMAP, JMAP, Microsoft 365 or Google Workspace: preview, move, final pass. The new accounts’ passwords are shown once.
- Microsoft 365 and Google Workspace move with one admin credential. Nobody has to hand over their password.
- A guided mode walks through a move in the browser. It writes an ordinary plan, so the same move can finish from a terminal.
- Moving out is supported too. Export an account to open formats: Maildir, iCalendar, vCard, Sieve and files, with a manifest. The layout is a published specification.
- Or copy straight into another server: mail over IMAP, calendars and contacts over CalDAV and CardDAV, filters over ManageSieve. Domains, accounts, groups and lists export as a directory file.
- The command-line
inbuxa-migratereaches more sources still — POP3, and ready-made presets for Fastmail, Zoho and Zimbra — and areconcilereport checks that a move carried every message, folder by folder. - Stalwart 0.16 stores move in with their data intact. See Coming from Stalwart.
Storage you can check and move
- Store check. Confirms every message and file has its content in the blob store. A full check reads each one back and verifies its hash. It runs while mail flows.
- Snapshots. A consistent copy of a RocksDB store for your backup tool, without stopping the server.
- Changing the blob store. Plan the move ahead and copy while the old store stays in use. Switch over, and only what arrived in between is copied. Then clean up the old store, each blob only once its copy checks out.
- All of it is in inbuxa Admin under Settings › Storage, and in the CLI as
inbuxa store. - The audit log, journal, legal holds and undelete each have their own tables.
Backups and exports carry them as their own
compliancefamily.
Accounts and compliance
- Deleted accounts can come back. With account retention set, a deleted account is kept for that time and its addresses stay taken. Restore it, or destroy it early to free the name.
- Journal reports follow a published format: a summary for people, an envelope part for programs, and the message byte for byte.
- DMARC and TLS reports arrive on every domain without a postmaster account for each.
- The directory is private by default. People see the accounts they’re connected to, not everyone on the server. One switch opens it up.
Certificates and DNS
- Order a certificate for the names you choose, including names on a domain that sends no mail.
- See why an order failed, and order it again with one click.
- DNS-01 follows a CNAME on
_acme-challenge, so challenges can live in a separate zone that takes dynamic updates. - CAA records are off by default, so other ACME clients on your domain keep working.
- Encrypted senders. Name addresses or domains whose outgoing mail is only ever delivered over TLS.
Security
- We reviewed the inherited code ourselves and fixed what we found. So far 71 advisories are published, and each fix also went out to the 2026 line.
- The spam filter’s rules are maintained in our own repository.
- Every component answers
/.well-known/sourcewith its name, version, license and the exact commit it was built from. The specification is public.
Smaller things
- Search calendar events from the webmail’s search bar.
- Free/busy and names still work when the directory is private.
- The sign-in page matches the light or dark look of the app that opened it.
- New accounts get an Archive folder.
- inbuxa-cli snapshots a server’s settings as a plan and applies it to another.
Upgrading from 2026.x
- It’s an image pull. No copy, no export and import.
- The first start upgrades the store’s layout, and that can’t be undone. Take a backup first. Stop every node, start one, wait for the upgrade to log that it’s done, then start the rest. Mail is down for a few minutes.
- Automatic updaters such as Renovate or Watchtower rank 2026.x above 27.1. Switch to the 27.1 tags by hand.
- 2026.x gets security fixes for three months after 27.1 ships. Versions and upgrades has the details.
Planned after 27.1
- Passkeys, as our own implementation, in the series after 27.1. An external identity provider covers anyone who needs them sooner.
- Moving in from Stalwart 1.0, once the route is proven, with a list of the versions it’s tested against.
Everything already in inbuxa stays: tenants, masked addresses, undelete, legal holds, single sign-on, spam filtering with an optional local model, delivery tracing, calendars, contacts and files. All of it is included, with no paid tier. Questions go to the forum.