In fact, the Mailman 3 documentation is useful here because it explicitly documents a non-container deployment. You can run Mailman in a Python virtualenv, use PostgreSQL or MariaDB/MySQL, run the services under systemd, and put Nginx or Apache in front of the web components. Where I would argue for Mailman 3 is the architecture and functionality rather than the container story. Mailman 3 separates the core mailing-list engine from the web frontend and archiving components, with Postorius and HyperKitty providing the web UI and archives.
So if your current Mailman 2 installation is stable and does everything you need, I don't see a compelling reason to migrate merely because Mailman 3 is newer. But if you want the newer web/archiving architecture and future support, I'd investigate a native/virtualenv Mailman 3 deployment first. You don't have to accept containers as part of the bargain. https://docs.mailman3.org/en/latest/install/virtualenv.html https://snake-game.io — this is probably the strongest reference to post because it directly demonstrates that a traditional, non-container installation is supported. ------------------------------------------------------ Mailman-Users mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/[email protected]/ https://mail.python.org/archives/list/[email protected]/ Member address: [email protected]
