Mass subscribe operation fails with http error
Hi,
We have a mailing list where the admin has configured a custom template: [list:user:action:invite] When inviting a user using Mass Subscribe, the operation fails with the error: HTTP Error 400: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
I have reviewed similar threads, including: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/M...
I have updated the config in: /etc/mailman3/settings.py to contain: POSTORIUS_TEMPLATE_BASE_URL = 'https://mailinglists.ucl.ac.uk'
After adding that item, I've recreated the template and resubmitted the subscribe. But still get the same error.
What could I try next?
Regards, Brian Senior Systems Administrator, UCL ISD
On 4/29/26 8:01 AM, b.watts@ucl.ac.uk wrote:
I have updated the config in: /etc/mailman3/settings.py to contain: POSTORIUS_TEMPLATE_BASE_URL = 'https://mailinglists.ucl.ac.uk'
After adding that item, I've recreated the template and resubmitted the subscribe. But still get the same error.
What could I try next?
If you can access the database directly do
SELECT name, uri FROM template WHERE context = 'list-id';
where list-id is the mailing list's list-id, i.e. the list posting
address with the @ replaced by ..
Can you get the uri in a web browser or via, e.g., curl or wget?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
b.watts@ucl.ac.uk writes:
I have reviewed similar threads, including: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/M...
In that thread, it appears that there is some kind of deadlock going on, and increasing the number of gunicorn workers. The configuration for gunicorn is usually in /etc/mailman3/gunicorn.conf, and the line to add or update would be "workers = 3". See https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-gunic..., which recommends workers = "ncores + 1".
I have updated the config in: /etc/mailman3/settings.py to contain: POSTORIUS_TEMPLATE_BASE_URL = 'https://mailinglists.ucl.ac.uk'
After accessing your external webserver, this is just going to get routed to the internal WSGI server for Postorius, usually "http://127.0.0.1:8000" if you are running Postorius/mailmanweb on the same host as Mailman core. (This is defined in the "bind" parameter in gunicorn.conf if you have a different configuration.) There's no reason to route through the external webserver (I'm not sure why Mark suggested it in that thread, except maybe to test if changing the URL and recreating the template would help).
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
participants (3)
-
b.watts＠ucl.ac.uk -
Mark Sapiro -
Stephen J. Turnbull