you@lists:~$ ./why-mailman.sh
Mailing lists, the way the internet intended.
Managed GNU Mailman 3 with Postorius, HyperKitty archives, real Reply-To-List, and DMARC handled properly. Migrated off Google Groups in an afternoon, and nobody can shut it down but you.
Terminal transcript: you@lists:~$ mailman members announce@yourproject.org — 9 members. you@lists:~$ post announce@yourproject.org < release-2.4.txt — fanning out to 9 subscribers. OK 9 delivered, 0 bounced, 0 spam-foldered. OK archived at /hyperkitty/list/announce@yourproject.org/2026/07/.
you@lists:~$ cat 02-why-lists-still-win.txt
## why-lists-still-win
A mailing list is not a feature bolted inside somebody else's product. It is the oldest working format for group communication on the internet — one address, every subscriber, no feed deciding who sees the message, no platform that can rebrand your community into an add-on next quarter.
- Every message reaches every subscriber — no feed, no algorithmic throttling.
- The archive is yours: exportable mbox, not a Google-owned export file with a deadline.
- Reply-To-List keeps conversations on the list, not scattered across private replies.
- DMARC, SPF and DKIM are configured per list, so messages don't get silently dropped by strict bulk-sender rules.
- Nobody can deprecate this. Mailman has been the reference mailing-list manager since 1998 — the protocol underneath is SMTP, not a roadmap.
1 message → 9 mailboxes → 1 permanent archive
you@lists:~$ ./list-health-check.sh
## list-health-check
you@lists:~$ cat 04-what-we-run.txt
## what-we-run
- mailman version
- Mailman 3.x — Postorius admin UI, HyperKitty archives
- list management
- Postorius web UI — create, moderate, subscribe/unsubscribe, ban, no shell access needed
- public archive
- HyperKitty — searchable, threaded, a permanent URL per message
- reply-to-list
- munged correctly out of the box — no reply-all chaos
- deliverability
- SPF + per-list DKIM signing + DMARC alignment, handled for you
- data residency
- EU-hosted
- backups
- daily — list config, archive and subscriber database included
- export
- mbox / CSV export any time — your data, your exit
you@lists:~$ cat 05-migration.log
## migration
you@old:~$ google-groups-export announce@yourproject.org → writing members.csv (247 rows) → writing archive.mbox (1,842 messages) OK export complete: members.csv, archive.mbox you@lists:~$ mailman create announce@yourproject.org OK list created: announce@yourproject.org you@lists:~$ mailman addmembers members.csv announce@yourproject.org → importing 247 addresses OK 247 members added, 0 rejected you@lists:~$ hyperkitty-import archive.mbox --list announce@yourproject.org → indexing 1,842 messages OK archive imported: /hyperkitty/list/announce@yourproject.org/ you@lists:~$ mailman subscribe announce@yourproject.org newcomer@example.org OK subscribed: newcomer@example.org you@lists:~$ echo "Same list, same address, nobody's permission required."
you@lists:~$ cat 06-cost-comparison.txt
## costs
Some organisations run mailing lists through Google Workspace Groups for Business, where every subscriber needs a paid Workspace seat. Managed Mailman does not require a seat per subscriber — the price stays flat no matter how the list grows.
| List size | Workspace, per seat/mo | Managed Mailman, flat/mo | Monthly saving |
|---|
How we calculate this
you@lists:~$ cat 07-faq.txt
## faq
? Can you really migrate us off Google Groups without losing history?
Yes. We export your members and archive, recreate the list in Mailman 3, re-import subscribers, and load the old threads into HyperKitty so the archive stays searchable and public. A list under 10,000 messages typically moves in an afternoon, and we test-fire before we cut over.
? What is the difference between Mailman and a Google Group or Workspace Group?
Mailman is the mailing-list software the internet has run on since 1998: Reply-To-List, a real SMTP-based subscription model, and a public archive you own. Groups is a product Google can reshape, restrict or sunset on its own schedule; your list rides on someone else's roadmap.
? Do you handle SPF, DKIM and DMARC for us?
Yes. Every list gets per-list DKIM signing, and we configure SPF and DMARC alignment for the sending domain so messages do not land in spam or get rejected by strict recipient servers.
? Can members reply to the whole list, not just to me?
Reply-To-List is configured correctly out of the box. Hit reply, it goes to the list. No more reply-all confusion or accidentally private replies to a list address.
? Is there a public archive people can search without subscribing?
HyperKitty gives every list a permanent, threaded, searchable web archive at a stable URL per message, which helps new members onboard and helps search engines index your community's history.
? What if we outgrow it or want to leave?
Full mbox and CSV export, any time, no lock-in. It is the same open format Mailman has always used, so you can move your list to any other Mailman host, or run it yourself.