On 23.10.24 00:09, Mark Sapiro wrote:
How are you creating the template? If you are creating it via Postorius,
Yes, via Postorius created using the url
https://lists.example.org/mailman3/lists/community.lists.example.com/templat...
what is your setting for POSTORIUS_TEMPLATE_BASE_URL and what does the
I did not set POSTORIUS_TEMPLATE_BASE_URL in settings.py.
entry in the template table in the database look like?
in mailman.template:
mailman=# select * from template where id = 6; 6|list:user:action:subscribe|community.lists.example.com|http://localhost:8000/mailman3/api/templates/list/community.lists.example.com/list:user:action:subscribe||
in mailmanweb.template:
mailmanweb=# select * from postorius_emailtemplate where id = 6; 6|list:user:action:subscribe|test1234||2024-09-09 13:52:22.377792+02|2024-10-14 15:11:43.029873+02|list|community.lists.example.com
POSTORIUS_TEMPLATE_BASE_URL should be the same URL you use to access Postorius up to but not including the
/postorius/or/mailman3/part. I.e, for this list whose info page is at https:// lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/, the setting isPOSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org'
For testing I have set
POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.example.org'
to the URL of our main domain, however, if I test an anonymous subscribe through the list info page I still get the timeout error
HTTPConnectionPool(host='localhost', port=8000): Read timed out. (read
timeout=5)
Logs still show the same behaviour: the request for the template comes into the server but is finished and logged after 5 seconds:
127.0.0.1 - - [23/Oct/2024:05:51:38 +0000] "GET /mailman3/api/templates/list/community.lists.example.com/list:user:action:subscribe HTTP/1.1" 200 8 "-" "python-requests/2.32.3"
The tcpdump of the tcp conection also looks the same: the response is pushed with the termination of the connection.
I can access http://localhost:8000/mailman3/api/templates/list/community.lists.example.co... with curl and immediately get the response.
So it still looks to me as if the response is stuck in the tcp buffers of the connection and not pushed immediately, but only once the requestor times out after 5 seconds and closes the connection.
Thanks,
Gerald