Some reflections on installing mailman3 from Debian packages - Why? - I often want a mailing list - Owning the domain for email is required, and should be required for everyone (but that's a rant for another time) - Resource requirements are low - Reflections - Go right for Debian 11 - There are no complete guides - https://www.linuxcloudvps.com/blog/how-to-install-mailman3-on-debian-11/ - https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.html - Other people even aggregate their own: https://jeffknerr.github.io/mailman3/debian/2022/07/19/mailman3-on-debian-11.html - I guess we just hack on it until it works then we don't want to document further. Which I feel like is more due to the system feeling super fractured; if they're not going to put much into it, we shouldn't. - Packages don't configure but also don't tell you what they don't configure - Deleting `example.com` causes the web application to implode - https://lists.mailman3.org/archives/list/[email protected]/thread/SWUCPOOX3STF7HU7WCUBDUXYUXQNSKRW/?sort=date - https://github.com/maxking/docker-mailman/issues/12 - Probable workaround 1. Create a new domain 2. Get the ID of your new domain (`select * from domain;` on `sqlite3 /var/lib/mailman3/data/mailman.db`) 3. Update `/usr/share/mailman3-web/settings_local.py` to include `SITE_ID=${domainId}` 4. Restart all 5. Delete `example.com` from the web app - I used a DigitalOcean droplet which meant (unsurprisingly) the IP address was on [[Spamhaus]]'s blocklist. I went to `https://check.spamhaus.org/listed/?searchterm=${ipAddress}` and submitted a request. Do this as early as possible. Include the _exact_ time the IP address was assigned to you for faster service - Templates seem to be missing for me, old mailman used to have templates preset