Error when sending customized welcome message template
Dear List,
As soon as a template "[list:user:notice:welcome]" exists, and at least one email address is provided during mass subscribe, while sending an invitation is disabled and sending a welcome message is enabled, the following error occurs:
HTTP Error 400: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))The new member(s) are added to the mailing list, but the welcome message is not sent. In the log file </var/log/mailman3/mailman.log>, I find:
--------------- >8 ---------------
[13/Mar/2025:08:09:49 +0100] "GET /3.1/lists/testliste.mailman.uni-konstanz.de HTTP/1.1" 200 422 "-" "GNU Mailman REST client v3.3.5" Mar 13 08:09:49 2025 (1072) deque: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 705, in urlopen httplib_response = self._make_request( ^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 388, in _make_request self._validate_conn(conn) File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1050, in _validate_conn conn.connect() File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 414, in connect self.sock = ssl_wrap_socket( ^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in ssl_wrap_socket ssl_sock = _ssl_wrap_socket_impl( ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl return ssl_context.wrap_socket(sock, server_hostname=server_hostname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/ssl.py", line 517, in wrap_socket return self.sslsocket_class._create( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/ssl.py", line 1108, in _create self.do_handshake() File "/usr/lib/python3.11/ssl.py", line 1379, in do_handshake self._sslobj.do_handshake() ConnectionResetError: [Errno 104] Connection reset by peer
During handling of the above exception, another exception occurred:
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/lib/python3/dist-packages/requests/adapters.py", line 489, in send resp = conn.urlopen( ^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 789, in urlopen retries = retries.increment( ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 552, in increment raise six.reraise(type(error), error, _stacktrace) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/six.py", line 718, in reraise raise value.with_traceback(tb) File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 705, in urlopen httplib_response = self._make_request( ^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 388, in _make_request self._validate_conn(conn) File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1050, in _validate_conn conn.connect() File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 414, in connect self.sock = ssl_wrap_socket( ^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in ssl_wrap_socket ssl_sock = _ssl_wrap_socket_impl( ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl return ssl_context.wrap_socket(sock, server_hostname=server_hostname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/ssl.py", line 517, in wrap_socket return self.sslsocket_class._create( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/ssl.py", line 1108, in _create self.do_handshake() File "/usr/lib/python3.11/ssl.py", line 1379, in do_handshake self._sslobj.do_handshake() urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() ^^^^^^ File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 362, in _step_do_subscription self.member = self.mlist.subscribe( ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 106, in wrapper return function(args[0], config.db.store, *args[1:], **kws) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 539, in subscribe notify(SubscriptionEvent( File "/usr/lib/python3/dist-packages/zope/event/__init__.py", line 32, in notify subscriber(event) File "/usr/lib/python3/dist-packages/mailman/app/membership.py", line 183, in handle_SubscriptionEvent send_welcome_message(mlist, member, member.preferred_language) File "/usr/lib/python3/dist-packages/mailman/app/notifications.py", line 79, in send_welcome_message welcome_message = wrap(getUtility(ITemplateLoader).get( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 192, in get contents = getUtility(ITemplateManager).get( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 106, in wrapper return function(args[0], config.db.store, *args[1:], **kws) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 114, in get contents = protocols.get(actual_uri, **auth) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line 39, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/api.py", line 73, in get return request("get", url, params=params, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/api.py", line 59, in request return session.request(method=method, url=url, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/sessions.py", line 587, in request resp = self.send(prep, **send_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/sessions.py", line 701, in send r = adapter.send(request, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/adapters.py", line 547, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer')) [13/Mar/2025:08:09:49 +0100] "POST /3.1/members HTTP/1.1" 400 125 "-" "GNU Mailman REST client v3.3.5" [13/Mar/2025:08:09:49 +0100] "GET /3.1/lists/testliste@mailman.uni-konstanz.de/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" [13/Mar/2025:08:09:49 +0100] "GET /3.1/lists/testliste@mailman.uni-konstanz.de/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5"
--------------- 8< ---------------
If no template "[list:user:notice:welcome]" exists, the default welcome message is sent without an error.
Could you please help me to solve this issue? Your help would be much appreciated.
Best regards, Markus Grandpré
-- Markus Grandpré Mailinglisten-Administration, Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342
-- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342
On 3/13/25 2:54 PM, Markus Grandpré wrote:
Dear List,
As soon as a template "[list:user:notice:welcome]" exists, and at least one email address is provided during mass subscribe, while sending an invitation is disabled and sending a welcome message is enabled, the following error occurs:
HTTP Error 400: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
Was this template set in Postorius? If so, there is an issue with your setting for POSTORIUS_TEMPLATE_BASE_URL. The default is
POSTORIUS_TEMPLATE_BASE_URL = http://localhost:8000/
which should work if your wsgi server is listening on the local host, port 8000, but setting it to the base scheme and host you use to access Postorius is generally good.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Dear Mr. Sapiro,
Thank you once again for your help. The templates are now being sent without any errors.
However, while using the many variables that can be sent with a template, I noticed that the resolution of the variable $hyperkitty_url is not working, even though i am using a private archive in this list and a URL to this archive exists.
Best regards, Markus Grandpré
Am 13.03.25 um 14:12 schrieb Mark Sapiro:
On 3/13/25 2:54 PM, Markus Grandpré wrote:
Dear List,
As soon as a template "[list:user:notice:welcome]" exists, and at least one email address is provided during mass subscribe, while sending an invitation is disabled and sending a welcome message is enabled, the following error occurs:
HTTP Error 400: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
Was this template set in Postorius? If so, there is an issue with your setting for POSTORIUS_TEMPLATE_BASE_URL. The default is
POSTORIUS_TEMPLATE_BASE_URL = http://localhost:8000/which should work if your wsgi server is listening on the local host, port 8000, but setting it to the base scheme and host you use to access Postorius is generally good.
-- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: +49 7531 88 4342
Markus Grandpré writes:
However, while using the many variables that can be sent with a template, I noticed that the resolution of the variable $hyperkitty_url is not working, even though i am using a private archive in this list and a URL to this archive exists.
That variable is documented only for use in the header and footer templates for regular (non-digest) posts, and a quick grep suggests it is only implemented for those two cases. I would assume it does not work in the welcome message template.
Steve
Dear Steve,
thank you very much for your reply.
I would assume it does not work in the welcome message template.
it doesn't work in the welcome message template for sure.
Kind regards Markus
Am 21.03.25 um 15:56 schrieb Stephen J. Turnbull:
Markus Grandpré writes:
However, while using the many variables that can be sent with a template, I noticed that the resolution of the variable $hyperkitty_url is not working, even though i am using a private archive in this list and a URL to this archive exists.
That variable is documented only for use in the header and footer templates for regular (non-digest) posts, and a quick grep suggests it is only implemented for those two cases. I would assume it does not work in the welcome message template.
Steve
-- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: +49 7531 88 4342
participants (3)
-
Mark Sapiro -
Markus Grandpré -
Stephen J. Turnbull