Linus Rath
d9ffe8a76e
Fixes from the review of the Files work (1cf9944b..a9a25b94).
- A file shared on its own, or one below a folder its owner took back,
could not be reached. Once Stalwart 1.0's placeholder folders were
left out it became a root of "Shared with me", which listed folders
only, and search opened it on the drive root. 0.16 lists such files
as roots too. Each owner's files shared on their own are now listed
on one page under "Shared with me" ("Files from <name>"), where they
open, preview and download like any other file and nothing can be
added; two of the same name get a number. Search opens a shared hit
where it is listed, and links into a shared drive name the node by id
(`/files?shared=<owner>:<id>`), so a shared folder or page also
survives a reload. A Files page that is already open takes the link
from search directly, since Next keeps it mounted when only the query
changes.
- A copy that fails part-way destroys only the nodes it made, the
deepest first and without `onDestroyRemoveChildren`, one call per
level because 0.16 refuses a folder destroyed in the same call as
its children. It used to destroy the new folder with everything
below it, so whatever someone put there during a long copy was
deleted for good. A folder holding such nodes now stays, and the
error says part of the copy was left in place.
- The document editor opens read-only on 0.16 for a sharee without the
rename right. 0.16.6 to 0.16.23 refuse any change a sharee makes
without Modify, so every save of such a document failed with a 500.
1.0, told apart by its `maxFileNodeDepth`, still asks for
`mayModifyContent` alone.
- Ctrl+C with only symlinks selected empties the clipboard instead of
keeping an earlier cut for the next paste.
- A paste reads each account's file tree once, not once per pasted
item for the listing and 1.0's depth check.
- The Stalwart bundle's README says that on older 0.16 releases and
the 1.0 pre-releases a failed update also drops the cached copy, and
the next restart or reload of the Applications downloads it again,
not only a later `UpdateApps`. The static README says a restart
applies the CORS setting on the current 1.0 pre-releases, where
`ReloadSettings` fails with the stock spam-filter rules.
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.