[Script request]: Bulwark Mail

[King3R]

Application Name

Bulwark Mail

Official Website

https://bulwarkmail.org/

Source Repository

https://github.com/bulwarkmail/webmail

Repository Stars

1100

Minimum Adoption Requirement

• The official source repository has at least 1,000 stars.

Description

Bulwark is a self-hosted webmail suite that speaks JMAP (RFC 8620) natively and pairs with Stalwart Mail Server. Mail, calendar, contacts, and files share one login, one settings store, and one admin dashboard.

Apps

• Mail: threading, a unified inbox, full-text search, Sieve filters, S/MIME, and templates
• Calendar: month, week, day, and agenda views. Drag an event to reschedule it; iMIP invitations go out on create and update.
• Contacts: several address books, groups, vCard import/export, and autocomplete in the composer
• Files: Stalwart's native JMAP FileNode storage, browsable as a real folder tree

Features

• Setup wizard: runs on first launch and walks through JMAP, OAuth, branding, and the admin password. No .env.local editing.
• Admin dashboard: policy, users, plugins, themes, and the audit log, all from the browser
• SSO: OAuth2 / OIDC with PKCE and discovery, plus TOTP two-factor
• Multi-account: several accounts at once. HTTP/2 lifts the five-account cap that browser connection pooling imposes on HTTP/1.1.
• Plugins & themes: bundled extensions, plus a marketplace at extensions.bulwarkmail.org
• 24 languages: including right-to-left for Arabic, Hebrew, and Persian
• PWA: installs on desktop and mobile. Email colors are remapped by luminance, so mail hard-coded to dark-on-white stays readable on a dark theme.
• Real-time: JMAP EventSource pushes new mail as it arrives

Why should this be added?

Most self-hosted webmail is an IMAP client with a browser bolted onto it. That inheritance shows up as a poll loop, one connection per folder, and threads the browser has to reassemble on every render. JMAP does that work on the server, which lets Bulwark stay thin and still stay in sync.

A generic JMAP client would stop there. Bulwark also calls Stalwart's own JMAP methods, so Sieve filters, the vacation responder, account security, FileNode storage and runtime branding are all reachable from the same session, instead of being things you leave the webmail to configure.

Bulwark is a great addition to the Stalwart Mail Server with a growing range of extensions and some side projects.
https://github.com/bulwarkmail/legacy-proxy
https://github.com/bulwarkmail/relay
https://github.com/bulwarkmail/native

Installation Notes

• A running Stalwart Mail Server with JMAP enabled, or the built-in demo backend if you're only poking at the UI. No Stalwart yet? Follow the official installation guide, then Stalwart setup for the Bulwark-specific parts.
• Node.js 20 or later, for a manual install only. The Docker image ships its own Node 24 runtime, so ignore this if you're using the container.

https://bulwarkmail.org/docs/getting-started/installation

Due Diligence

• I have searched existing scripts and found no duplicate.
• I have searched existing discussions and found no duplicate request.
• The application has an official public source repository.
• The application is self-hosted and suitable for Proxmox VE Helper-Scripts.
• The application appears to be actively maintained and provides official releases, tags, or release tarballs.
• I understand that requests outside the project scope may be closed without an extensive explanation.