Hi,
We migrated from mailman2 to mailman3 a week ago. Since then we are unable to send messages the our students through the mailing list. Here are some symptoms:
- I go to mass subscribe and subscribe 400 emails
- I click subscribe, the browser (in my case safari) tries to load the page for a few seconds
- The request times out
- Once the service becomes responsible again, I see that only part of my emails got subscribed (~50 in this case).
For me this really looks like the emails are sent on the "web-thread" that gets killed once the request times out. Looking at this https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.py... https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.py... seems to confirm my suspicions.
Some quick overview of our infrastructure: The TCP endpoints are: browser -> haproxy in kubernetes-entry-router -> nginx in kubernetes-ingress -> nginx in mailman -> mailman
We mitigated the issue by giving it more CPU power and increasing the timeouts in one of the nginx endpoints. We also have a problem with sending out emails to "large" (>50) groups, as they seem to not getting sent out at all. Do you have any idea what the problem here could be?
We would be really glad if you can help us getting our mailman up and running, as I currently have to send emails out by "hand". I will happily provide you with more details about our configuration, just let me know what you need.
Kind regards,
Jonas
Jonas Felber
VIS - Verein der Informatik Studierenden an der ETH Zürich CAB E 31, Universitätstr. 6, ETH Zentrum, CH-8092 Zürich https://www.vis.ethz.ch https://www.vis.ethz.ch/