Why Reeva runs on Stalwart Mail Server
By Reeva Team · May 18, 2026
The mail engine you use shapes everything: how fast your inbox is, what protocols you can speak, what you can be sure is not happening to your messages. Reeva is built on the open-source Stalwart Mail Server. Here is why.
One engine, every modern protocol
Stalwart speaks SMTP, IMAP, JMAP and Sieve out of the box, with DKIM signing, DMARC and SPF checks, ARC, MTA-STS and TLS-RPT. We don’t have to bolt on a JMAP gateway or a separate calendar server — it’s one engine you can audit.
Written in Rust
Mail servers historically come with a long list of memory-safety CVEs. Stalwart is written in Rust, which removes a whole class of memory-corruption bugs by construction. Less fire-fighting means more time on features and privacy.
Auditable
The source is on GitHub under a permissive license. Anyone can read it, file bugs and verify that the server isn’t quietly reading your content. We follow upstream closely and contribute back where we can.
Modern features for free
Stalwart handles DKIM key rotation, sieve filtering, JMAP push and full-text search natively. We get to focus on the things that matter to Reeva’s customers — privacy, custom domains, calendar, file cloud — instead of reinventing mail-server plumbing.
What does it mean for you?
- Your mail sits inside a fast, modern, audited engine.
- All standard protocols are first-class — no bridge apps required.
- The components are open, so the service can be reproduced by anyone if Reeva ever disappeared.
If you want to dig in, Stalwart is at stalw.art. If you’d rather skip the infrastructure entirely and just have a private inbox, that’s what we’re here for.