HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
stalwartlabs
stalwart
Rust2023–2026
stalwartlabs / stalwart

stalwart

All-in-one Mail & Collaboration server. Secure, scalable and fluent in every protocol (IMAP, JMAP, SMTP, CalDAV, CardDAV, WebDAV).

17Distinct people
21Mentions
0Explicit recommenders
15.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

All-in-one Mail & Collaboration server. Secure, scalable and fluent in every protocol (IMAP, JMAP, SMTP, CalDAV, CardDAV, WebDAV).

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

Microsoft Outlook/365 still down after 12 hours direct repository linkDebated

The discussion centers on a massive, multi-day Microsoft Outlook/365 outage that has paralyzed global business operations and triggered widespread criticism of the company's infrastructure reliability. Participants are divided between attributing the failure to Microsoft's strategic shift toward AI at the expense of core engineering talent and structural complexity, versus arguing that such centralization is an inevitable trade-off for modern enterprise efficiency.

129 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by year21 dated mentions

Observed mentions: 2023-05-30 18:56:54 UTC to 2026-10-26 18:38:51 UTC.

02468102023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC523
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC10010
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC211

What Hacker News says

21 sources
Not OP, but I self host a few domains. I was worried about not being able to send emails, but is seems that as long as you setup properly SPF/DKIM/DMARC you're fine. You may have problems if using a domestic address though. For the configuration, the best bet is probably to use a product that makes it easy to configure the above three, there are a few alternatives around, like Stalwart [1] or docker-mailserver (which is little more that your postfix/dovecot/rspam combo packaged in a container) [2] [1] https://github.com/stalwartlabs/stalwart [2] https://github.com/docker-mailserver
In Lies we tell ourselves about email addresses
> There are no issues with POP and multiple clients whatsoever. POP3 in standard only have "Leave a copy on the server" but lack synchronisation mechanism. > I suggest you to educate yourself on DKIM, DMARC, SPF and SMTP before making those statements. You cannot use SMTP in real world without these protocols. Your messages would automatically land in spam folders of big providers. For example, if you want to send email to Gmail, you need SPF and DKIM [1]. Any half decent implementation of SMTP need to support all these protocols [2]. [1] https://support.google.com/a/answer/81126?hl=en [2] https://github.com/stalwartlabs/stalwart > It DOES have delivery tracking. Spam filtering is not a protocol feature and it shouldn't be. I suggest you again to educate yourself. SMTP have extension for DSNs (Delivery Status Notifications) but crucially
Read the rest
it does not provide information if/why email was classified as spam. This is a reason why many website registration form have “check spam folder”. SMTP deliverability is a hard problem both on protocol level and infrastructure on spam filtering[3]. [3] https://blog.paranoidpenguin.net/2020/02/self-hosting-email-... > If you don't know how to build something doesn't mean it's left out to "hardcore graybeards". You got to admit you just don't know how and either learn or surrender to companies who know, offering the same for a buck. It's pretty simple. I spend a significant amount of time investigating feasibility of building an email product and build some libraries for email protocols. It is not just my opinion but other HNs users including OP. Search HN for "self hosting email" for others people experience.
In Why email startups fail
As I understand, the AGPLv3 requires the corresponding source code to be provided under the same license, so the Arch guys wanting an AGPLv3 source package isn't just a niche Arch-specific concern or a "packaging issue," but a licensing requirement that can't be ignored or delayed. > All you need to do is omit the Enterprise feature flag during compilation, and what you get is a 100% AGPL-3.0 build. Maybe I'm misunderstanding, but my interpretation of this issue[1] is that Stalwart contains AGPLv3 licensed functions that call into the SEL licensed `has_tenant_access` function, among others, and that the affected functions are not conditionally compiled out of the AGPLv3 binaries. @afontenot says on that issue that they don't believe it's "possible to use Stalwart under the AGPL at present." Are they wrong and can that issue be closed? I a
Read the rest
m also concerned about the webadmin. A free software program that downloads proprietary code on first start isn't free software in practice, and since there aren't two separate SEL and AGPLv3 licensed builds of the webadmin on GitHub, that must be the case. > 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. I get it, but it's disappointing that AGPLv3 compliance is so low in the list of priorities that this licensing issue has been known about but not solved in 8 months, all while receiving grants intended for free software projects. That balancing act must have included the consideration that the free software community is regularly burnt by rug-pulls (Redis) and trust isn't easily won back once its lost. > 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. I might. Sorry if I've been harsh, but it's only because Stalwart is a very cool project. A FOSS all-in-one mail server written in a safe language is exactly what email needs, and since learning about it, I've been worried that it's too good to be true. Please don't let it be. I don't think it will gain the momentum to replace Postfix if it can't be packaged in Linux distros due to licensing issues. [1]: https://github.com/stalwartlabs/stalwart/issues/783
In Calendars, Contacts and Files in Stalwart
I checked my repo to see which Stalwart version I was running and if I could update, and I was surprised to find that the Arch package has been deleted due to FOSS licensing concerns[1], the most severe of which seems to be that Stalwart can no longer build without proprietary code[2]. Other smaller issues include the fact that the web admin interface isn't included in the source distribution, but is downloaded from GitHub on first run, and _also_ seems to contain proprietary code[3]. These issues, which would be showstoppers for a real free software project, and pretty easy to fix if you were the rightsholder of the code, were promised to be fixed "in a few weeks" in September last year, and "in a few months" in January this year, however they're still not fixed, which means I can't upgrade - not that I probably want to anymore. I truly
Read the rest
believe in free software, so I find the idea of using "open source" as an empty marketing bullet-point for at least eight months to be fairly distasteful. Might be time to switch to Maddy. [1]: https://gitlab.archlinux.org/archlinux/packaging/packages/st... [2]: https://github.com/stalwartlabs/stalwart/issues/783 [3]: https://gitlab.archlinux.org/archlinux/packaging/packages/st...
In Calendars, Contacts and Files in Stalwart

Showing the 15 most recent of 21 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.