HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mailcow
mailcow-dockerized
PHP2017–2026
mailcow / mailcow-dockerized

mailcow-dockerized

mailcow: dockerized - 🐮 + 🐋 = 💕

18Distinct people
19Mentions
0Explicit recommenders
13.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

mailcow: dockerized - 🐮 + 🐋 = 💕

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 year19 dated mentions

Observed mentions: 2017-10-22 11:51:38 UTC to 2026-08-13 19:41:04 UTC.

0123452017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 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
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC505
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC303
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC505
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC110
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

19 sources
Many applications hammer the disk even if the developers don't believe this is an issue, not only journald, unfortunately. It's my third attempt to make my regular Linux desktop less disk-chatty. This is a huge issue for btrfs and for COW FS in general, because they have massive write amplification for small and frequent writes (38,7 TB written to my idle desktop SSD in 2 years). If you're interested, here are my findings this time so far: - workrave: 60 second stat sync https://github.com/rcaelers/workrave/pull/717 - kde klipper: saves to disk on every copy, even if permanent storage is disabled https://bugs.kde.org/show_bug.cgi?id=501030 - kde plasmashell: saves qt shader cache each time notification popup disappears https://bugs.kde.org/show_bug.cgi?id=523805 - bitwarden firefox extension: tries to connect to desktop ap
Read the rest
plication every 10 seconds, writes about every failure to browser's WebStorage 14+ KB https://github.com/bitwarden/clients/issues/22192 - firefox datareporting/glean: very chatty .mozilla/firefox/xxx/datareporting/glean/db/data.safe - ipfs: writes every received DHT announce to disk, 20 GB in 3 hours https://discuss.ipfs.tech/t/constant-writes-to-datastore-log/20316 - mailcow: redis saves data every 5 minutes https://github.com/mailcow/mailcow-dockerized/pull/7405
In Single log line is 49KB+ (ext4) / 110KB+ (btrfs) of systemd-journald disk writes
My list[0] being discussed on HN as well[1]: - maddy (https://github.com/foxcpp/maddy) (this is my personal favorite, I'm running at least 6 instances right now) - chasquid (https://blitiri.com.ar/p/chasquid/) - mailu (https://github.com/Mailu/Mailu) - mailinabox (https://github.com/mail-in-a-box/mailinabox) - mailcow (https://github.com/mailcow/mailcow-dockerized) - docker-mailserver (https://github.com/docker-mailserver/docker-mailserver) - Postal (https://docs.postalserver.io/) (more for API driven email apps) - Haraka (https://haraka.github.io/) (SMTP only) - Combine with [WildDuck](https://wildduck.email/)? [0]: https://vadosware.io/post/its-never-been-easier-or-harder-to... [1]: https://news.ycombinator.com/item?id=32720234
In Email Done My Way, Part 0 – The Journey
I have been selfhosting my email stack on a cheap VPS (~ $10) for many years now, probably since 2009 or so. I used to set up everything manually, but that was quite painful and there were some rough edges. Nowadays, I just use mailcow (https://github.com/mailcow/mailcow-dockerized) for the setup part and have a much more polished experience. Email deliverability is not a problem. Generally, you just have to make sure to correctly setup DKIM/SPF (and DMARC) and check if your IP is on some blacklist. You can get it removed easily. (Edit: Also required is forward-confirmed reverse DNS, see below). There was one provider that denied incoming mails from me, even though I got the IP removed from every blacklist I could find. I wrote a short mail to the admin contact and got told I had to host a web page with contact information on the same IP.
Read the rest
Since being whitelisted there, everything works like a charm, couldn't be happier.
In Ask HN: The middle ground for email self-hosting?
Just give me a dockercompose.yml. That’s all I need. A positive example for this is mailcow [1]: all you need to do is pulling the repo, editing the mailcow.conf and running “docker compose up”. Logging is preconfigured, and the watchdog just works. It’s dead simple and provides secure defaults. It’s ready for production in very little time. That’s what I would love to see from more projects. I hope supabase will follow this at some point. I really like the idea of a self hosted firebase. But right now there is too much to take care of for a single person to actually take a self hosted supabase into prod (be it for side projects or whatever). [1] https://github.com/mailcow/mailcow-dockerized
In The case for open infrastructure

Showing the 15 most recent of 19 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.