This is definitely a problem with your docker environment configuration and not a Mailman issue.
What does your environment look like? (Host version, host OS, docker version, network config, etc?)
From a shell _inside_ the container, can you ping publicsuffix.org? traceroute to it?
--Jered
----- On Jan 9, 2024, at 8:22 AM, bob B via Mailman-users mailman-users@mailman3.org wrote:
In my testing, from the docker host, I can curl "https://publicsuffix.org" But from inside the container, it just times out.
It looks like mailman needs to contact publicsuffix.org when you set the "DMARC mitigation action" to "replace from with list address" The mailman core log shows
/list/public_suffix_list.dat (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f8b38d318a0>, 'Connection to publicsuffix.org timed out. (connect timeout=5)'))
I had another thread for this issue (https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...), but started this one because it seems to just be an issue with the docker container not being able to get out to publicsuffix.org
I am running the maxking docker images version 0.4.3
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to jered@convivian.com