I have of course activated password login as it was not possible to get the
provider based logins to work (might be but not worth the time for me right
now). Is there any way for an user to request a new password when it is
I presume that the Persona login is removed now. I cannot hide it in my
version or at least I do not know how.
How do I set a template for one specific list? I want one list to have
a special footer template.
I have tried updating the database (template table) without effect so
apparently the database is not used for templates or some kind of
fallback is used to set it to the generic footer. Of course I also
tried to restart mailman after that operation to try to rule out any
I want to use a file://-path as that is the least painful way of doing
it. I also would like a solution to place a file in a special
location. My current templates are in a
structure with names like list:member:generic:footer.txt
Is there any way to enable footer for some lists at the same time
disable for lists. I maintain an mailman3 instance and some of the lists
in it need the footer message well some not.
When creating a new list in Mailman 3, the Digest Size Threshold is set to 30KB, which is not much in my opnion.
1) How do I set another default for Digest Size Threshold for new lists.
2) How do I change the default for existing lists
When Digest Size Threshold is not reached, mails seems to be sent according to digest_volume_frequency': which is set to 'monthly'. The web interface doesn't seem to have a setting for this.
How do I change this setting, both on a single list and the default for new lists?
I am using Docker-mailman (currently Mailman version 3.2.0a1).
I have a list with 38513 subscribers and when I operate on a very large number of them (for example click Unsubscribe all), the web interface times out. The same happens if I use the REST API, one member at the time, but run from a python script i've made).
The Docker containers for both Mailman core (mostly) and mailman web (sometimes) are using 100% CPU (quart of the server's amount of CPUs). By doubleing the CPU shares that the two docker containers can use (using RHEL Cockpit) from 1024 to 2048 for each, Mailman-core had a max usage of 190% and Mailman-web about 101%.
Still, mass unsubscribing the members by clicking Unsubscribe all made theinterface time out. Using the REST API succeeded unsubscribing all, but still made the Mailman web interface inaccessible.
How can I make Docker-mailman perform better, to avoid these timeouts.
University of Copenhagen