Linus Rath
483821706d
Stalwart 1.0 counts every EmailSubmission record of an account against `maxSubmissions` (500 by default), whatever its status or age, and its own purge of old records never runs. Bulwark never destroyed a submission, so after about 500 JMAP sends an account could not send at all: every send, read receipt and reschedule failed with a raw "There are too many email submissions" error, and each failed attempt left one more copy of the message in Drafts. Bulwark now removes the records that can no longer be cancelled. Destroying a record never stops its delivery, but a pending one could no longer be cancelled, so pending records are never touched: - an immediate send (no hold, no undo window) destroys its own record right after the send, riding along with the old-draft cleanup; only where `urn:stalwart:jmap` is advertised, and never decided by the created `undoStatus`, which 0.16.10-0.16.16 report as final for held sends - a throttled background prune destroys canceled records and final records whose `sendAt` has passed, going by `EmailSubmission/get`, in every submission account; it runs at startup, after sends, after undo and on EmailSubmission state changes - a confirmed cancel (undo, cancel, reschedule) destroys the canceled record in a request of its own - an `overQuota` on a submission create prunes at once, on Stalwart walks the change log for records older than the query's three-day window, retries once, and otherwise throws `SubmissionQuotaError`, shown as a translated explanation in the composer, quick reply, read receipts and the scheduled-send actions Failed sends now clean up after themselves and say so: - a failed send removes the Drafts copy it created and keeps the user's draft; the raw send paths remove their import the same way - a read receipt that did not go out is taken back out of Sent, a method-level error counts as a failure, `$MDNSent` is only set after a sent receipt, and the automatic receipt no longer retries on every refresh of the open message - quick-reply failures, "Send now", "Reschedule" and a failed undo are shown instead of only logged - the scheduled list reads every page of `EmailSubmission/query`; it stopped after the first because `total` needs `calculateTotal`
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.
Contents
- Screenshots
- Features
- Quick start
- Other ways to install
- Configuration
- Documentation
- Development
- Community and support
- License
Screenshots
Calendar week view · Contact details with recent mail and upcoming events
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:
- Getting started: Introduction, Installation, Editions, Bulwark Lite, Demo mode
- Deployment: Docker, Manual install, Static hosting, Install on Stalwart, Updating
- Guides: Admin dashboard, Account security, Impersonation, Plugins, Marketplace, Troubleshooting
- Extensions: Introduction, manifest.json, Publishing
- Development: Architecture, Contributing
- Legal: Privacy
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
- Questions: check Troubleshooting, then ask on Discord.
- Bugs and feature requests: open a GitHub issue.
- Security vulnerabilities: report them privately to dev@bulwarkmail.org or through a security advisory, never in a public issue.
- Release notes: CHANGELOG.md and the GitHub releases.
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.