What's the deal with maintaining mailing lists on Fedora these days?
For years I've used mailman (first mailman2, now mailman3) on Fedora to
administer mailing lists. In mailman3, you also need postorius to
provide a web interface to users and hyperkitty to provide mail archive
support.
On Fedora 35, mailman2 isn't available anymore, so that's when I
switched to mailman3. The original Fedora 35 did not have postorius,
but that became available later. Hyperkitty on the other hand is not
available on fedora 35. I use an rpm that I built myself.
On Fedora 36, mailman3 can be installed, but both postorius and
hyperkitty (there it is in the repository) cannot. They both depend on
a too old version of django.
On Fedora 37 (I know, not released yet, so any complaints should go to
the testing list) none of the packages can be installed since they all
depend on python 3.10 and F37 will come with 3.11. The packages are
actually the unmodified F36 packages.
Do people use mailman3 on Fedora? If so, how?
Should I invest time in getting it to work in a python virtual
environment? And how would that work with SELinux?
This very mailing list (users@xxxxxxxxxxxxxxxxxxxxxxx) is managed with
mailman3, but does the system on which it runs run Fedora?
--
Sjoerd Mullender
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
