Hi Mark,

>That's a misleading message. It's been improved by 
>https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the 
>underlying issue is inability to access a header or footer template when 
>decorating the message. This in turn is most likely >caused by some 
>template(s) in Mailman's var/templates/ directory being owned by `root` or 
>some other non-mailman user and not readable by the Mailman user which in turn 
>most likely results from running `mailman import21` as root.

You are my hero! After "patching" the outgoing.py file with the error messages 
I got

Aug 06 09:52:51 2025 (443278) Cannot connect to SMTP server 127.0.0.1 on port 
25: HTTPSConnectionPool(host='lists.example.com', port=443): Max retries 
exceeded with url: 
/postorius/api/templates/list/hpc-admintreffen-info.lists.example.com/list:member:regular:footer
 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: 
CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local 
issuer certificate (_ssl.c:1006)')))

And was shocked. Why is there an SSL Certificate Error? Why can't python 
requests verify the certificate?

So I googled a bit and found, that we can fix this be editing the cacert.pem of 
certifi. I did, but the error was still there. So I checked my https VHost 
(Apache btw) and there was a wrong chain in it. Oof. An error, that a browser 
does not see, but any ssl client. I fixed it and boom - everything works again.

Thank you again and thank you Stephen for trying to resolve the problem 😊



--
Stephan Krinetzki
 
IT Center
Gruppe: Anwendungsbetrieb und Cloud
Abteilung: Systeme und Betrieb
RWTH Aachen University
Seffenter Weg 23 
52074 Aachen
Tel: +49 241 80-24866
Fax: +49 241 80-22134
krinet...@itc.rwth-aachen.de
www.itc.rwth-aachen.de

Social Media Kanäle des IT Centers:
https://blog.rwth-aachen.de/itc/ 
https://www.facebook.com/itcenterrwth 
https://www.linkedin.com/company/itcenterrwth
https://twitter.com/ITCenterRWTH
https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ​

-----Original Message-----
From: Mark Sapiro <m...@msapiro.net> 
Sent: Tuesday, August 5, 2025 6:19 PM
To: mailman-users@mailman3.org
Subject: [MM3-users] Re: Held messages not delivered after approval

On 8/5/25 02:06, Krinetzki, Stephan wrote:

> Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost 
> on port 25
> 
> The last error is a very often in the mailman.log:


That's a misleading message. It's been improved by 
https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the 
underlying issue is inability to access a header or footer template when 
decorating the message. This in turn is most likely caused by some template(s) 
in Mailman's var/templates/ directory being owned by `root` or some other 
non-mailman user and not readable by the Mailman user which in turn most likely 
results from running `mailman import21` as root.

Bottom line - check that all sub-directories and files in Mailman's 
var/templates/ directory are searchable and readable by the Mailman user.

-- 
Mark Sapiro <m...@msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an 
email to mailman-users-le...@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/HPKY54EBOYBFIZRR4LLLSGNFI2UAMQGB/

This message sent to krinet...@itc.rwth-aachen.de

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@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/TTJCTY5Q3NTRGTDD3MA76FITVSB7WJJO/

This message sent to arch...@mail-archive.com

Reply via email to