Instructions described for the deployment of the set of mailman3, postorius and hyperkitty do not provided a functional system. Host package documentation tends to be rather opaque as well. Partly this may because there are no useful indications of how the system should be used or perhaps these instructions work for someone that already knows what they are doing

Propose:

• write a minimal deployment that actually works
• include details of how to use the system
• perhaps elaborate on tweaking a deployment

--Blacktav (talk) 10:01, 5 September 2025 (UTC)

There are the following components available

• mailman3 The GNU mailing list managerhttps://docs.list.org/en/latest/index.html
• mailman-web The web interface for Mailman 3
• mailman3-hyperkitty Mailman plugin to archive emails with Hyperkitty
• hyperkitty A web interface to access GNU Mailman v3 archives
• postorius wiki-page The New Mailman Web UI
• python-django-mailman3 Libraries and templates to Django-based interfaces interacting with Mailman
• python-mailmanclient Official Python bindings for the GNU Mailman 3 REST API
• python-flask-mailman Porting Django's email implementation to your Flask applications

It is not clear how all these packages should function together

• mailman3 this is the core package, everything else is subservient to it
• mailman-web this is a convenience package for deploying Hyperkitty and Postorius and is generally required for a functional mailman3 deployment
• mailman-hyperkitty this is a plugin for mailman3-core allowing core to interact with a Hyperkitty webserver

Thats it, you don't really need anything else (other than dependencies, some of which will be installed by these packages). The Mailman Suite documents how it is all supposed to work together (though it says there are 5 key packages and then proceeds to list 7)

The additional ArchLinux packages are if you wanted to deploy individual instances, for example on discrete containers. --Blacktav (talk) 12:14, 5 September 2025 (UTC)