Recent submissions

Comment · 1 month ago
Sievepad is built on Monaco (the editor component behind Visual Studio Code) and executes scripts with sieve-rs, the interpreter inside Stalwart, compiled to WebAssembly.
Comment · 1 year ago
Stalwarts supports the latest EmailPush draft too, although it is not announcing it in the JMAP capabilities.
Comment · 1 year ago
There is a new section in the documentation discussing upgrades:

https://stalw.art/docs/install/upgrade/

The goal is to stabilize the database layout/configuration format very soon so v1.0.0 can be released (hopefully before Q1/Q2 2026).

Comment · 1 year ago
This will get better soon. The next step on the roadmap is to refactor the configuration format and migrate most APIs to JMAP.
Comment · 1 year ago
Soon Thundermail by Mozilla!
Comment · 1 year ago
Thanks! :-)
Comment · 1 year ago
I want to clarify that Stalwart can absolutely be compiled without any proprietary code. All you need to do is omit the Enterprise feature flag during compilation [0], and what you get is a 100% AGPL-3.0 build. The Arch package removal wasn’t because the software suddenly became non-free, but rather due to a packaging requirement: Arch needs a clean separation of the Enterprise code from the source tree, and that’s something we haven’t done yet (it will be implemented as a script). The delay isn’t due to any unwillingness to comply, it’s simply been a matter of prioritization. Over the past few months, the focus was on delivering major features like WebDAV support. That said, I'm still fully committed to resolving the packaging issue because we want Stalwart back in Arch as much as you do.

It’s also worth noting that only about 5% of the codebase is Enterprise, and that small slice helps fund ongoing development and expansion of the team [1]. As much as I'd love to be completely sponsor-funded, the reality is that open source projects still need to cover real-world costs. For what it's worth, Stalwart has received two NLNet grants [2] [3] to support open protocol work, which hopefully reinforces our commitment to open source.

So while the optics of this situation may look rough from the outside, I promise it’s not some “open source in name only” kind of thing. It’s just one of those painful balance acts between building features, maintaining packages, and paying the bills.

And hey, if you're heading back to Maddy, no hard feelings. But the door’s always open if you want to give Stalwart another shot down the road.

[0]: https://stalw.art/docs/development/compile [1]: https://stalw.art/compare/#faq [2]: https://nlnet.nl/project/Stalwart/ [3]: https://nlnet.nl/project/Stalwart-Collaboration/

Comment · 1 year ago
Thanks for follow-up. You're absolutely right that there's a distinction between privacy and anonymity. However I just want to clarify that my decision to keep a low personal profile online stems from a deep belief in privacy, not secrecy.

To give you more context about the project: Stalwart Labs was indeed started and is currently led by a single developer: myself. I have over 30 years of experience working with email technologies and have previously founded three email-related companies.

That said, I’m not working entirely alone. While I’m the core developer and founder, there are others involved in Stalwart Labs today handling support, sales, and maintaining smaller parts of the codebase (mostly changes required by clients). My plan is to continue leading development myself until the project reaches version 1.0, which I hope will happen later this year. After that milestone, the goal is to gradually expand the development team, particularly to support work on a Rust-based webmail and calendar interface that will complement the mail server.

Stalwart’s development has been largely self-funded, aside from two NLNet grants. I’ve been growing the team organically and intentionally. While I have been approached by two VC firms, I’ve chosen to decline their offers. Not just to avoid external pressure (and stress), but also because some proposed directions conflicted with promises I’ve made to the community. For example, there have been suggestions to move some open-source features behind a paywall, which I’m against and promised the community never to do.

As for enterprise support, yes, Stalwart Labs offers an enterprise license that includes premium support services. And regarding adoption, I'm happy to say that there are currently a few hundred enterprise clients using Stalwart in production. While I would need the clients' permissions to share their names, I can say that Mozilla Thunderbird is one of them. They’ve publicly announced their upcoming launch of thundermail.com, which is powered by Stalwart.

I hope that gives you more clarity and confidence in the project. Thanks.

Comment · 1 year ago
Comment · 2 years ago
Comment · 3 years ago
Hello HN,

Excited to announce that Encryption at Rest has just been added to the open source Stalwart Mail Server. With this addition, the mail server will now automatically encrypt all incoming plaintext emails, utilizing either OpenPGP or S/MIME, before they are written to disk. Importantly, the keys are owned and controlled by the end user, ensuring that not even system administrators can decrypt these messages.

I'd love to hear your thoughts and feedback. Thanks!

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton