-
v27.1-rc.9
Pre-Releaseci / fork-checks (push) Skippedci / build (push) Skippedgithub/ci (branch) GitHub Actionspublish / version (push) Skippedpublish / publish-amd64 (push) Skippedpublish / publish-arm64 (push) Skippedpublish / publish-relay (push) Skippedpublish / release (push) Skippedpublish / binaries (push) Skippedannounce / announce (release) Successful in 24sci / github (push) Canceled after 37m39sgithub/ci (tag) GitHub Actionspublish / github (push) Successful in 54m30spublish / relay-sign (push) Successful in 17spublish / announce (push) Successful in 30sreleased this
2026-11-06 07:09:57 +00:00 | 18 commits to main since this releaseThe ninth release candidate of the 27.1 series: 27.1-rc.8 with certificate and DNS fixes, paging fixes for two query methods, and fuller milter traces.
Certificates and DNS
- CAA records are off by default. A domain with automatic certificates and automatic DNS used to publish a CAA record at its apex, tied to this server's ACME account. CAA covers every name under the domain, so another ACME client there, like certbot on a web server, would be refused at its next renewal. New domains now leave CAA off; the field explains when to turn it on. DNS-PERSIST-01 providers publish their
_validation-persistrecord whether or not CAA is on. (#294) - Changing a domain's names orders a certificate right away. Editing Additional Hostnames, the ACME provider or the domain name on a domain already on ACME used to wait for the next renewal, about 60 days out. Saving now orders a certificate when the names it covers change, and a domain keeps a single queued renewal. (#295)
Fixes
x:MaskedEmail/queryandx:ArchivedItem/querypage correctly. A request with apositionpast the first page returned the first page again and ignoredlimit. Both now honorposition,anchorandlimit. The masked email fix and its test are Stefan's, thanks Stefan. (#296)- Milter replies show in delivery traces. When a milter rejects with its own reply, the trace now records the SMTP code and text the client was sent, not just "Reply code". SMTP replies don't change. Stefan's patch again. (#293)
Before you upgrade
Existing domains keep the records they publish today, CAA included. If another ACME client issues certificates for names under a domain that inbuxa publishes CAA for, untick CAA in that domain's DNS settings, then delete the record at your DNS provider: unticking it doesn't remove a record that's already published. Check with
dig CAA example.com.Run this with inbuxa-admin 27.1-rc.5, whose DNS guide leaves CAA off and lists each DNS provider's description, and inbuxa-webmail 27.1-rc.3.
Everything in 27.1-rc.8 is here too, the directory fix, journal report format, inbuxa Relay and migrations included. inbuxa Relay ships from this tag as
registry.coffeylabs.org/inbuxa/inbuxa-relay:27.1-rc.9and 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.9, also tagged:27.1-rc.:lateststays on 2026.x until 27.1 ships.Downloads
- CAA records are off by default. A domain with automatic certificates and automatic DNS used to publish a CAA record at its apex, tied to this server's ACME account. CAA covers every name under the domain, so another ACME client there, like certbot on a web server, would be refused at its next renewal. New domains now leave CAA off; the field explains when to turn it on. DNS-PERSIST-01 providers publish their