-
v27.1-rc.8
Pre-Releasepublish / version (push) Skippedpublish / publish-amd64 (push) Skippedpublish / publish-arm64 (push) Skippedpublish / publish-relay (push) Skippedpublish / release (push) Skippedpublish / binaries (push) Skippedci / fork-checks (push) Skippedci / build (push) Skippedannounce / announce (release) Successful in 25sgithub/ci (branch) GitHub Actionsci / github (push) Successful in 40m9sgithub/ci (tag) GitHub Actionspublish / github (push) Successful in 47m51spublish / relay-sign (push) Successful in 18spublish / announce (push) Successful in 32sreleased this
2026-11-04 04:44:50 +00:00 | 30 commits to main since this releaseThe eighth release candidate of the 27.1 series: 27.1-rc.6 with one security fix and a new journal report format. 27.1-rc.7 was tagged with the security fix, but its build failed and it was never published, so this is the first release you can install with that fix.
Security
- Allow Directory Queries now does what it says. With the setting off, which is the default, regular users could still list and look up the other accounts on their server. Now listing and searching are refused over JMAP and WebDAV. A regular user can only look up the accounts they already have a connection to: their own, their groups, people who shared with them, and people on their own shares. Sharing follows the same rule on JMAP, WebDAV and IMAP. (#282, #283)
Journal reports
Journal reports now follow a public specification, the journal report format. A report is a
multipart/reportwith a summary for people, an envelope part for programs with one line per recipient, and the message byte for byte.Before you upgrade
Allow Directory Queries
If you're on the default, regular users lose these when you upgrade:
- directory suggestions in compose (addresses they type still send)
- picking anyone they have no connection to in the share dialog
- free/busy for people who haven't shared with them
- starting a share with someone new, in any client
People already on a share keep it, and it can still be changed or removed.
To keep all of that, turn on Settings › Sharing › Allow Directory Queries. With it on, nothing changes. Accounts allowed to list accounts aren't affected either way.
An IMAP connection keeps the settings it started with, so a change to this setting reaches it when it reconnects.
Journal reports
This matters if you send journals to an outside archive, or read reports with a script.
- Scripts should read the new envelope part, not the summary. The summary's wording isn't fixed.
- The
Bccline is nowNot in To or Cc, andaddressed=not-in-headersin the envelope part. It never proved a blind copy: a list's post arriving for a subscriber looks the same. - Reports to an archive now declare
BODY=8BITMIMEorBODY=BINARYMIME. A server that can't take the message unchanged doesn't get that report, which most often means a message with lines past 998 bytes and a server withoutBINARYMIME. The report stays in the built-in journal and shows as an archive failure on the journal.
Reports already stored keep the layout they were written in.
Run this with inbuxa-webmail 27.1-rc.3, which shows names on shares and explains missing free/busy when the setting is off.
Everything in 27.1-rc.6 is here too, inbuxa Relay and migrations included. inbuxa Relay ships from this tag as
registry.coffeylabs.org/inbuxa/inbuxa-relay:27.1-rc.8and as static binaries with.sigfiles; run it with the server release of the same version.Container image:
registry.coffeylabs.org/inbuxa/inbuxa-server:27.1-rc.8, also tagged:27.1-rc.:lateststays on 2026.x until 27.1 ships.Downloads