Linus Rath 5a553a315b fix: report refused read changes and re-register push at its limit
Follow-ups to the review of the push, keyword and identity work:

- A send that names no sender, like the List-Unsubscribe mailto: of the
  unified view, fell back to the first identity in server order, which
  on Stalwart 1.0 is a group's. It now takes the login's own identity,
  with addresses compared regardless of case.
- Re-register creates the replacement subscription before it destroys
  the old one, so at Stalwart's limit (15 per account by default) it
  failed with `overQuota`. It now frees the old record's place and
  tries once more.
- On 1.0 the push settings note goes by the emailpush capability alone
  and ignores refusals remembered under 0.16. On 0.16 a group the user
  belongs to is recognised by its identity, so a member without
  calendars, contacts or files keeps the group's junk filter and is no
  longer told the group sends no notifications.
- Plugin imports can no longer set Stalwart 1.0's attachment keywords,
  and `keywords.discover` leaves them out.
- Batch mark-as-read showed messages the server refused as read. It now
  updates only what was written and reports the rest, and thread
  expansion and category-tab moves keep what a partly refused batch
  did write.
- Refused read and star changes from shortcuts, the list, the viewer
  and Pro tabs show "Failed to update email" instead of an unhandled
  rejection. The automatic mark-as-read on opening stays quiet.
- A tag whose id predates the 128-byte limit can have its colour
  changed again.
- The state-regression guard notes that a multi-node 1.0 cluster can
  trip it harmlessly, at the cost of one extra full fetch.
2026-09-25 21:57:11 +02:00
2026-09-23 21:18:21 +02:00
2026-09-23 21:18:21 +02:00
2026-09-23 21:18:21 +02:00
2026-09-23 21:18:21 +02:00

Bulwark: webmail for Stalwart Mail Server. Mail, calendar, contacts and files in one browser client.

latest release  docker: ghcr.io/bulwarkmail/webmail  license: AGPL v3  Discord members online

Website · Documentation · Live demo · Releases · Discord

Bulwark Webmail is a self-hosted webmail client for Stalwart Mail Server. It talks to Stalwart over JMAP and puts mail, calendar, contacts and files behind one login, with one set of settings and one admin dashboard.

Bulwark inbox on a laptop, with the same message open on a phone

Contents

Screenshots

Calendar week view with events from several calendars Contact details with recent mail and upcoming events
Calendar week view  ·  Contact details with recent mail and upcoming events

Rich-text composer next to the message list The inbox split diagonally between the light and dark theme
Composer with identities and formatting  ·  Light and dark themes

Features

  • Mail: threading, unified inbox, cross-account views, full-text search, Sieve filters, S/MIME, templates, scheduled send
  • Calendar: month, week, day and agenda views, recurring events, iMIP invitations, CalDAV subscriptions
  • Contacts: several address books, groups, vCard import and export
  • Files: Stalwart's JMAP file storage, with previews, sharing and folder upload

All four share single sign-on and 2FA, multiple accounts, 27 languages, PWA install and web push, themes, plugins and keyboard shortcuts. The full list is on the All features page.

There are two editions. The full edition runs as a Node.js server and adds the admin dashboard, OAuth, plugins and settings sync. Bulwark Lite is the same client as static files, served by any web host or by Stalwart itself.

Quick start

docker run -d -p 3000:3000 ghcr.io/bulwarkmail/webmail:latest

Then open http://localhost:3000. A setup wizard asks for your Stalwart server and an admin password. The installation guide has the details, and Stalwart setup covers the mail server side.

Other ways to install

Method Guide
Docker Compose Compose
Behind a reverse proxy or on a sub-path Reverse proxy
From source, without Docker Manual install
Lite on any static host Static hosting
Lite as a container Container image
Lite served by Stalwart Install on Stalwart

Updating explains how to move to a new version.

Configuration

Most installs are set up in the wizard on first launch and changed later in the admin dashboard. You can also use environment variables, which fit read-only or immutable deployments better. When both set the same key, the value saved in the admin config wins, so an environment variable only fills in what the admin config leaves unset.

JMAP_SERVER_URL=https://mail.example.com
APP_NAME=My Webmail
Topic Guide
Overview, config files and precedence Configuration
Every variable Environment reference
OAuth2 / OIDC and single sign-on Authentication, Embedded SSO
Several JMAP servers, custom endpoints Multi-server deployments, Custom endpoints
Branding, logos, per-domain branding Customization
Anonymous telemetry (off by default) Anonymous usage stats

Documentation

All documentation is at bulwarkmail.org/docs:

The pages are Markdown files in the website repository. Send corrections there.

Development

git clone https://github.com/bulwarkmail/webmail.git
cd webmail
npm install
cp .env.dev.example .env.local   # built-in mock JMAP server, no mail server needed
npm run dev
npm run typecheck
npm run lint
npx vitest run             # unit tests
npm run test:integration   # Stalwart in Docker + Playwright

The contributing guide covers tests, translations, code style and pull requests. Architecture explains how the code is organized.

The stack: Next.js 16 and React 19, TypeScript, Tailwind CSS v4, Zustand, Tiptap, next-intl, Tabler Icons, and our own JMAP client (RFC 8620). Tests run on Vitest and Playwright.

Community and support

License

GNU AGPL v3. This repository preserves the original MIT attribution for the fork lineage in NOTICE.

Acknowledgments

Thanks to root-fr/jmap-webmail and @ma2t for the groundwork this project builds upon.

S
Description
Self-hosted JMAP webmail for Stalwart Mail Server. Mail, calendar, contacts, and files in one client.
Readme Multiple Licenses
85 MiB
Languages
TypeScript 98.4%
JavaScript 0.9%
CSS 0.3%
Shell 0.3%