v1.18.0 - Stalwart 1.0 #1376
rathlinus
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
1.18.0 (2026-10-26)
1.18.0 works with Stalwart 1.0, released today, as well as with 0.16. Sign-in, calendars, contacts, files and sending were adapted to what changed in 1.0, and a Stalwart that was moved from 0.16 to 1.0 with Stalwart's migration tool keeps working with the same open tabs. It also fixes the findings of a security review of the whole webmail, more places where an action in a view that mixes accounts could hit another account's message with the same id, and a series of calendar bugs around repeating events. Plugins can show their own search results and a count on their buttons, quick reply can be turned off, and a new device offers to restore your saved account list.
Thank you for your donations:
One-time
Monthly
Upgrading to Stalwart 1.0
stalwart-migrate) copies the data into a new store. Ids and sync state are kept, so Bulwark carries on without reloading anything, but OAuth tokens are not migrated: everyone who signed in with single sign-on, or with a password and a two-factor code, signs in again. Keep the server's public URL the sameSecurity
/api/plugin-approval-statusrefuses plugin packages while user plugins, plugin uploads or their review are turned off. Any signed-in user could fill the admin's review queue and the data directory with packages (GHSA-qc44-275p-gqw9, thanks @oguzyilmaznet)COOKIE_SECURE=true, the unprefixed sidebar-app cookie is no longer trusted behind a TLS proxy that sends noX-Forwarded-Proto, so a sibling subdomain can't add origins to the page'sframe-src(GHSA-cjm9-m826-mh78, thanks @oguzyilmaznet)cid:image no longer hides the rest of the messageconfig.json, the admin password hash and the setup token are written readable only by the app's user, a synced settings file can no longer pass as an admin session, and the setup wizard refuses a session secret under 32 charactersFeatures
email.get,email.getRawandemail.getAttachmenttake an optional account id, and summaries carry itNODE_USE_ENV_PROXY=1is set. Bulwark still checks the address itself and asks the proxy for exactly that address ([Bug]: iCal subscription bypasses HTTPS_PROXY despite NODE_USE_ENV_PROXY=1 #1367, thanks @Jan0oo)Fixes
setup.shasks again for a pasted session secret under 32 charactersThis discussion was created from the release v1.18.0 - Stalwart 1.0.
All reactions