Pins server 2026.9.30.2, console 2026.9.30 and webmail
inbuxa-webmail:2026.10.5-g17a8093, the repository's new name. Those
releases need three changes here:
- The JMAP client asks for urn:inbuxa:jmap:registry, the registry
capability's name since the server renamed it.
- Configured servers refuse HTTP Basic on /jmap (contract C-23), and in
bootstrap mode nothing but x:Bootstrap answers. So after bootstrap the
server comes up once with INBUXA_HTTP_BASIC_AUTH=all, from a one-step
override file, long enough for the administrator to give itself an API
key; it is then recreated without the override. The key, as a Bearer
token, does the rest of the setup, is destroyed at the end and expires
within the hour regardless.
- --local signs in to the webmail through the server's page as well, as
the first-party OAuth client: a password sign-in would have nothing to
pass the password on with. The server is told its loopback address as
INBUXA_PUBLIC_URL, so its sign-in page and OAuth metadata point where a
browser can reach them.
install-local now signs in end to end the way a browser does, and checks
that the Basic override did not outlive the setup.