Search results for "Cannot connect to SMTP server"

[MM3-users] Re: Held messages not delivered after approval

by Krinetzki, Stephan

Hi Mark, Hi Stephen, so I updated now my configuration a bit. The logging is now default: [logging.archiver] datefmt: %b %d %H:%M:%S %Y [logging.archiver] format: %(asctime)s (%(process)d) %(message)s [logging.archiver] level: info [logging.archiver] path: mailman.log [logging.archiver] propagate: no [logging.bounce] datefmt: %b %d %H:%M:%S %Y [logging.bounce] format: %(asctime)s (%(process)d) %(message)s [logging.bounce] level: info [logging.bounce] path: bounce.log [logging.bounce] propagate: no [logging.config] datefmt: %b %d %H:%M:%S %Y [logging.config] format: %(asctime)s (%(process)d) %(message)s [logging.config] level: info [logging.config] path: mailman.log [logging.config] propagate: no [logging.database] datefmt: %b %d %H:%M:%S %Y [logging.database] format: %(asctime)s (%(process)d) %(message)s [logging.database] level: warn [logging.database] path: mailman.log [logging.database] propagate: no [logging.debug] datefmt: %b %d %H:%M:%S %Y [logging.debug] format: %(asctime)s (%(process)d) %(message)s [logging.debug] level: info [logging.debug] path: debug.log [logging.debug] propagate: no [logging.error] datefmt: %b %d %H:%M:%S %Y [logging.error] format: %(asctime)s (%(process)d) %(message)s [logging.error] level: info [logging.error] path: mailman.log [logging.error] propagate: no [logging.fromusenet] datefmt: %b %d %H:%M:%S %Y [logging.fromusenet] format: %(asctime)s (%(process)d) %(message)s [logging.fromusenet] level: info [logging.fromusenet] path: mailman.log [logging.fromusenet] propagate: no [logging.gunicorn] datefmt: %b %d %H:%M:%S %Y [logging.gunicorn] format: %(t)s "%(r)s" %(s)s %(b)s "%(f)s" "%(a)s" [logging.gunicorn] level: info [logging.gunicorn] path: mailman.log [logging.gunicorn] propagate: no [logging.http] datefmt: %b %d %H:%M:%S %Y [logging.http] format: %(asctime)s (%(process)d) %(message)s [logging.http] level: info [logging.http] path: mailman.log [logging.http] propagate: no [logging.locks] datefmt: %b %d %H:%M:%S %Y [logging.locks] format: %(asctime)s (%(process)d) %(message)s [logging.locks] level: info [logging.locks] path: mailman.log [logging.locks] propagate: no [logging.mischief] datefmt: %b %d %H:%M:%S %Y [logging.mischief] format: %(asctime)s (%(process)d) %(message)s [logging.mischief] level: info [logging.mischief] path: mailman.log [logging.mischief] propagate: no [logging.plugins] datefmt: %b %d %H:%M:%S %Y [logging.plugins] format: %(asctime)s (%(process)d) %(message)s [logging.plugins] level: info [logging.plugins] path: plugins.log [logging.plugins] propagate: no [logging.root] datefmt: %b %d %H:%M:%S %Y [logging.root] format: %(asctime)s (%(process)d) %(message)s [logging.root] level: info [logging.root] path: mailman.log [logging.root] propagate: no [logging.runner] datefmt: %b %d %H:%M:%S %Y [logging.runner] format: %(asctime)s (%(process)d) %(message)s [logging.runner] level: info [logging.runner] path: mailman.log [logging.runner] propagate: no [logging.smtp] datefmt: %b %d %H:%M:%S %Y [logging.smtp] every: $msgid smtp to $listname for $recip recips, completed in $time seconds [logging.smtp] failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg [logging.smtp] format: %(asctime)s (%(process)d) %(message)s [logging.smtp] level: info [logging.smtp] path: smtp.log [logging.smtp] propagate: no [logging.smtp] refused: $msgid post to $listname from $sender, $size bytes, $refused failures [logging.smtp] success: $msgid post to $listname from $sender, $size bytes [logging.subscribe] datefmt: %b %d %H:%M:%S %Y [logging.subscribe] format: %(asctime)s (%(process)d) %(message)s [logging.subscribe] level: info [logging.subscribe] path: mailman.log [logging.subscribe] propagate: no [logging.task] datefmt: %b %d %H:%M:%S %Y [logging.task] format: %(asctime)s (%(process)d) %(message)s [logging.task] level: info [logging.task] path: mailman.log [logging.task] propagate: no [logging.vette] datefmt: %b %d %H:%M:%S %Y [logging.vette] format: %(asctime)s (%(process)d) %(message)s [logging.vette] level: info [logging.vette] path: mailman.log [logging.vette] propagate: no Further, I edited the logrotate: /var/log/mailman/mailman-logs/*.log { missingok daily compress delaycompress nomail notifempty rotate 14 dateext su mailman mailman olddir /var/log/mailman/mailman-logs/oldlogs postrotate /bin/kill -HUP `cat /opt/mailman/var/master.pid 2>/dev/null` 2>/dev/null || true # Don't run "mailman3 reopen" with SELinux on here in the logrotate # context, it will be blocked /opt/mailman/mailman-venv/bin/mailman reopen >/dev/null 2>&1 || true endscript } It is now more like the Fedora one and seems to be better. Now in the mailman.log I see the HOLD messages and the approved messages. The smtp.log logs just the incoming Mail, which seems to be fine. So, here a complete Trace: smtp.log: Aug 05 10:18:40 2025 (217984) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 05 10:18:40 2025 (217984) Peer: ('127.0.0.1', 57074) Aug 05 10:18:40 2025 (217984) ('127.0.0.1', 57074) handling connection Aug 05 10:18:40 2025 (217984) ('127.0.0.1', 57074) >> b'LHLO lists.rwth-aachen.de' Aug 05 10:18:40 2025 (217984) ('127.0.0.1', 57074) >> b'MAIL FROM:<SENDER> SIZE=15187' Aug 05 10:18:40 2025 (217984) ('127.0.0.1', 57074) sender: SENDER Aug 05 10:18:40 2025 (217984) ('127.0.0.1', 57074) >> b'RCPT TO:<stephansmodliste(a)lists.example.com>' Aug 05 10:18:40 2025 (217984) ('127.0.0.1', 57074) recip: stephansmodliste(a)lists.example.com Aug 05 10:18:40 2025 (217984) ('127.0.0.1', 57074) >> b'DATA' Aug 05 10:18:40 2025 (217984) ('127.0.0.1', 57074) >> b'QUIT' Aug 05 10:18:40 2025 (217984) ('127.0.0.1', 57074) connection lost Aug 05 10:18:40 2025 (217984) ('127.0.0.1', 57074) Connection lost during _handle_client() The mailman.log: Aug 05 10:18:40 2025 (217983) HOLD: stephansmodliste(a)lists.example.com post from SENDER held, message-id=<b93e46d8342f42039c99e1d2d036c711@SENDERDOMAIN>: The message is not from a list member Aug 05 10:21:04 2025 (218015) held message approved, message-id: <b93e46d8342f42039c99e1d2d036c711@SENDERDOMAIN> [05/Aug/2025:10:21:04 +0200] "POST /3.1/lists/stephansmodliste(a)lists.example.com/held/211056 HTTP/1.1" 204 0 "-" "GNU Mailman REST client v3.3.5" [05/Aug/2025:10:21:04 +0200] "GET /3.1/lists/stephansmodliste(a)lists.example.com/held?count=0&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" [05/Aug/2025:10:21:04 +0200] "GET /3.1/lists/stephansmodliste(a)lists.example.com/held?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" [05/Aug/2025:10:21:04 +0200] "GET /3.1/lists/stephansmodliste(a)lists.example.com/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" [05/Aug/2025:10:21:04 +0200] "GET /3.1/lists/stephansmodliste(a)lists.example.com/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" 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: Aug 05 09:46:12 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 09:46:13 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 09:46:13 2025 (217988) Cannot connect to SMTP server localhost on port 25 Aug 05 09:46:14 2025 (217987) Cannot connect to SMTP server localhost on port 25 Aug 05 09:46:24 2025 (217987) Cannot connect to SMTP server localhost on port 25 Aug 05 09:50:22 2025 (217988) Cannot connect to SMTP server localhost on port 25 Aug 05 09:50:24 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 09:53:30 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 09:55:01 2025 (217987) Cannot connect to SMTP server localhost on port 25 Aug 05 09:55:01 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 09:55:09 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 09:57:44 2025 (217987) Cannot connect to SMTP server localhost on port 25 Aug 05 09:57:46 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 09:58:50 2025 (217988) Cannot connect to SMTP server localhost on port 25 Aug 05 09:58:52 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 09:58:52 2025 (217987) Cannot connect to SMTP server localhost on port 25 Aug 05 09:58:53 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 09:58:53 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 09:58:53 2025 (217988) Cannot connect to SMTP server localhost on port 25 Aug 05 10:01:18 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 10:02:02 2025 (217987) Cannot connect to SMTP server localhost on port 25 Aug 05 10:07:11 2025 (217987) Cannot connect to SMTP server localhost on port 25 Aug 05 10:10:36 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 10:11:35 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:16:04 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:16:05 2025 (217988) Cannot connect to SMTP server localhost on port 25 Aug 05 10:16:07 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:16:58 2025 (217988) Cannot connect to SMTP server localhost on port 25 Aug 05 10:17:42 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 10:18:30 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:20:13 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:28:08 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:28:08 2025 (217988) Cannot connect to SMTP server localhost on port 25 Aug 05 10:28:31 2025 (217987) Cannot connect to SMTP server localhost on port 25 Aug 05 10:28:37 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:28:44 2025 (217988) Cannot connect to SMTP server localhost on port 25 Aug 05 10:28:47 2025 (217988) Cannot connect to SMTP server localhost on port 25 Aug 05 10:28:50 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:28:57 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 10:29:22 2025 (217988) Cannot connect to SMTP server localhost on port 25 Aug 05 10:29:40 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 10:29:41 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:30:37 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:30:37 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 10:30:50 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:31:15 2025 (217987) Cannot connect to SMTP server localhost on port 25 Aug 05 10:33:42 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:33:53 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:34:27 2025 (217985) Cannot connect to SMTP server localhost on port 25 Aug 05 10:34:28 2025 (217986) Cannot connect to SMTP server localhost on port 25 Aug 05 10:38:25 2025 (230250) Cannot connect to SMTP server lists.example.com on port 25 Aug 05 10:38:25 2025 (230247) Cannot connect to SMTP server lists.example.com on port 25 Even after changing the smtp_host in mailman.cfg this error appears randomly. Sadly the mail does not get delivered. -- 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 krinetzki(a)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 <mark(a)msapiro.net> Sent: Tuesday, August 5, 2025 12:51 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Held messages not delivered after approval On 8/4/25 00:21, Krinetzki, Stephan wrote: >> >> And for every one of those shunted messages there should be an exception with traceback logged in mailman.log. Those tracebacks should be helpful. > > If there were any. Maybe the "debug" level should be "info". But for which logs? The standard logging levels from lowest to highest are debug info warning error critical Whatever level is set for a log results in all messages of that level or higher being logged. I.e. if the log's level is debug, all messages for that log of any level should be logged. For every shunted message, a message like `SHUNTING: <file name without the .pck extention>` preceded by the exception and traceback is logged to error.log with level error. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/runner.py… > Maybe the restart at night after the lograte maybe the issue. As I said before, blindly restarting Mailman is a bad idea. On servers that I maintain, I always verify that all queues are empty before stopping or restarting Mailman. If necessary, I'll kill the incoming runner and wait for the out queue to empty and then stop mailman. If you want to do this daily, you could automate that., e.g. ``` if queues empty: restart Mailman else: when in queue is empty, sigterm incoming runner when out queue is empty, stop Mailman when Mailman stopped, start Mailman ``` The stop/start is needed because a simple restart at that point won't start the sigtermed incoming runner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)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 krinetzki(a)itc.rwth-aachen.de

10 months, 1 week

[MM3-users] Re: Generic Cannot connect to SMTP server error, no outgoing smtp connections

by Thomas Hochstein

Stefan Bauer via Mailman-users wrote: > Mailman logs Cannot connect to SMTP server, however the server is > listening, but i see no connection attempts. [...] > If i restart the docker-core container, i see a single time the error > "Cannot connect to SMTP server 172.17.0.1 on port 587". Is it possibly to connect e.g. via telnet (from the host/IP mailman is running on, as the user mailman is running as) to the SMTP server? That looks more like a connection problem from A to B than a mailman problem. -thh

2 weeks

[MM3-users] Re: Generic Cannot connect to SMTP server error, no outgoing smtp connections

by Mark Sapiro

On 6/4/26 6:09 AM, Stefan Bauer via Mailman-users wrote: > Dear Users, > > I'm debugging since several days a mailman3 installation and can not get > mailman to deliver mails to list members. > > Mailman logs Cannot connect to SMTP server, however the server is > listening, but i see no connection attempts. This issue with unobtainable templates and a misleading log message is <https://gitlab.com/mailman/mailman/-/issues/514> and the logging is improved for the next release by <https://gitlab.com/mailman/mailman/-/merge_requests/1362>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks

[MM3-users] Re: Generic Cannot connect to SMTP server error, no outgoing smtp connections

by Stefan Bauer

I found the problem. Thanks for your help: As mailman3 via docker, consists of 2 independent containers (mailman-core & web) the templates, the runner used a wrong url when looking for templates. after adjusting my templates via SQL, all is fine now: # sqlite3 /opt/mailman/core/var/data/mailman.db "SELECT * FROM template;" 1|list:user:notice:probe|cubewerk.de| http://localhost:8000/postorius/api/templates/domain/cubewerk.de/list:user:… 3|list:member:regular:footer|cubewerk.de| http://localhost:8000/postorius/api/templates/domain/cubewerk.de/list:membe… 4|list:member:regular:footer|lists.cubewerk.de| http://localhost:8000/postorius/api/templates/domain/lists.cubewerk.de/list… sqlite3 /opt/mailman/core/var/data/mailman.db "UPDATE template SET uri = REPLACE(uri, 'localhost:8000', '172.18.0.3:8000');" # sqlite3 /opt/mailman/core/var/data/mailman.db "SELECT * FROM template;" 1|list:user:notice:probe|cubewerk.de| http://172.18.0.3:8000/postorius/api/templates/domain/cubewerk.de/list:user… 3|list:member:regular:footer|cubewerk.de| http://172.18.0.3:8000/postorius/api/templates/domain/cubewerk.de/list:memb… 4|list:member:regular:footer|lists.cubewerk.de| http://172.18.0.3:8000/postorius/api/templates/domain/lists.cubewerk.de/lis… Am Do., 4. Juni 2026 um 16:48 Uhr schrieb Thomas Hochstein <thh(a)thh.name>: > Stefan Bauer via Mailman-users wrote: > > > Mailman logs Cannot connect to SMTP server, however the server is > > listening, but i see no connection attempts. > [...] > > If i restart the docker-core container, i see a single time the error > > "Cannot connect to SMTP server 172.17.0.1 on port 587". > > Is it possibly to connect e.g. via telnet (from the host/IP mailman is > running on, as the user mailman is running as) to the SMTP server? > That looks more like a connection problem from A to B than a mailman > problem. > > -thh > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)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 cubewerk(a)gmail.com >

2 weeks

[MM3-users] Generic Cannot connect to SMTP server error, no outgoing smtp connections

by Stefan Bauer

Dear Users, I'm debugging since several days a mailman3 installation and can not get mailman to deliver mails to list members. Mailman logs Cannot connect to SMTP server, however the server is listening, but i see no connection attempts. In queue/out, i see changing files all the time: drwxrwx--- 2 mailman nogroup 4.0K Jun 4 13:04 . drwxr-xr-x 15 mailman nogroup 4.0K Jun 4 08:22 .. -rw-rw---- 1 mailman nogroup 6.1K Jun 4 12:22 1780575734.9281623+0ad5f564c9fc5f27750a09b948f3480d9047cbaa.pck.tmp -rw-rw---- 1 mailman nogroup 6.1K Jun 4 13:04 1780578250.2070453+752ca17af5c64af7aab5f0fc61ac2ea28b091825.bak 038b90c74d8d:/opt/mailman/var/queue/out# ls -alh total 24K drwxrwx--- 2 mailman nogroup 4.0K Jun 4 13:04 . drwxr-xr-x 15 mailman nogroup 4.0K Jun 4 08:22 .. -rw-rw---- 1 mailman nogroup 6.1K Jun 4 12:22 1780575734.9281623+0ad5f564c9fc5f27750a09b948f3480d9047cbaa.pck.tmp -rw-rw---- 1 mailman nogroup 6.1K Jun 4 13:04 1780578250.7552953+6350a013583657c317c0a64b9cf2039dca645974.bak 038b90c74d8d:/opt/mailman/var/queue/out# SMTP/DEBUG-Log is flooded with over and over same attempts: ==> /opt/mailman/core/var/logs/smtp.log <== Jun 04 13:04:46 2026 (26) Using agent: <mailman.mta.deliver.Deliver object at 0x79ed98555310> Jun 04 13:04:46 2026 (26) IndividualDelivery to: cubewerk(a)gmail.com ==> /opt/mailman/core/var/logs/debug.log <== Jun 04 13:04:46 2026 (31) [VirginRunner] starting oneloop Jun 04 13:04:46 2026 (31) [VirginRunner] ending oneloop: 0 Jun 04 13:04:46 2026 (26) [OutgoingRunner] finishing filebase: 1780578286.711373+091038a49a00758fdd2ba5265714e2fa31ea4843 Jun 04 13:04:46 2026 (26) [OutgoingRunner] doing periodic Jun 04 13:04:46 2026 (26) [OutgoingRunner] committing transaction Jun 04 13:04:46 2026 (26) [OutgoingRunner] checking short circuit Jun 04 13:04:46 2026 (26) [OutgoingRunner] ending oneloop: 1 Jun 04 13:04:46 2026 (26) [OutgoingRunner] starting oneloop Jun 04 13:04:46 2026 (26) [OutgoingRunner] processing filebase: 1780578286.7329357+2ec378350ee99307adc287fc8727fb9120a385d3 Jun 04 13:04:46 2026 (26) [OutgoingRunner] processing onefile Jun 04 13:04:46 2026 (26) [outgoing] <function deliver at 0x79ed98b85d00>: <gxZS.-LyKCSHn9UWsyVepCakA9g(a)flTQyy2_BUC0KFtMliiieCkabFXP1SdNnP1xIyNQp-k.xz> ==> /opt/mailman/core/var/logs/smtp.log <== Jun 04 13:04:46 2026 (26) Using agent: <mailman.mta.deliver.Deliver object at 0x79ed98a43bf0> Jun 04 13:04:46 2026 (26) IndividualDelivery to: cubewerk(a)gmail.com If i restart the docker-core container, i see a single time the error "Cannot connect to SMTP server 172.17.0.1 on port 587". my config: [runner.retry] sleep_time: 10s [webservice] hostname: 172.18.0.2 port: 8001 admin_user: restadmin admin_pass: restpass configuration: /etc/gunicorn.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.18.0.2 lmtp_port: 8024 smtp_host: 172.17.0.1 smtp_port: 587 smtp_user: smtp_pass: smtp_secure_mode: starttls smtp_verify_hostname: false smtp_verify_cert: false configuration: /etc/postfix-mailman.cfg [logging.smtp] level: debug [logging.error] level: debug [logging.debug] level: debug [archiver.mail_archive] enable: no configuration: /opt/mailman/mail_archive_dummy.cfg [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman-hyperkitty.cfg Any helps is greatly appreciated. thank you. Stefan

2 weeks

[MM3-users] Re: Cannot connect to SMTP server

by Mark Sapiro

On 8/13/22 15:14, mkummini(a)cmi.ac.in wrote: > > However, I get the following line each time I do a restart > Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 > I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error. You only see this message once at startup because it is only issued once until there is a successful delivery. This error can occur for reasons other than an inability to connect to the smtp server. In particular, if there are errors in decorating the message with a header and/or a footer because of permissions or other problems in retrieving a list:member:regular:header or list:member:regular:footer template, this will occur. Have you put templates in Mailman's var/templates directory (possibly named /var/lib/mailman/templates in the debian package). If so, can the Mailman user (I think `list` in a debian package) find and read them? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Incorrect error log message in OutgoingRunner._dispose()

by mailman26＠xse.com

I'm trying to bring up mailman 3 in a spare vm prior to upgrading a production system from mailman 2. One feature the existing mailman 2 lists uses that I can't get working with mailman 3 are templates. After using "mailman import21" I found files with names such as list:member:regular:footer.txt in the list tree. However they were ignored so I removed them I tried tried creating a template using the web postorius gui. When a message is injected, I see an error log from the out runner: Apr 25 12:32:22 2026 (82977) Cannot connect to SMTP server 127.0.0.1 on port 25 Following the error message, the out runner goes cpu bound, creating and deleting queue files in queue/out with .pck and .bak extensions, very quickly. I updated the code to print the exception and it tells a completely different story: Apr 25 12:38:15 2026 (83339) Cannot connect to SMTP server 127.0.0.1 on port 25 (HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /api/templates/list/test.example.com/list:member:regular:footer (Caused by NewConnectionError("HTTPConnection(host='localhost', port=8000): Failed to establish a new connection: [Errno 61] Connection refused"))) I'm using the default webservice port (8001) so I would not expect anything to ever be listening on 8000. When I stop the runners, the problematic queue file is moved to the shunt queue. Here's what I changed to get the exception detail: mm 287 # pwd /usr/local/lib/python3.11/site-packages/mailman/runners mm 288 # diff -c /var/tmp/outgoing.py outgoing.py *** /var/tmp/outgoing.py Thu Apr 23 14:26:22 2026 --- outgoing.py Sat Apr 25 12:34:33 2026 *************** *** 110,116 **** self._func, msg.get('message-id', 'n/a'))) self._func(mlist, msg, msgdata) self._logged = False ! except socket.error: # There was a problem connecting to the SMTP server. Log this # once, but crank up our sleep time so we don't fill the error # log. --- 110,116 ---- self._func, msg.get('message-id', 'n/a'))) self._func(mlist, msg, msgdata) self._logged = False ! except socket.error as e: # There was a problem connecting to the SMTP server. Log this # once, but crank up our sleep time so we don't fill the error # log. *************** *** 118,125 **** if port == 0: port = 'smtp' # Log this just once. if not self._logged: ! log.error('Cannot connect to SMTP server %s on port %s', ! config.mta.smtp_host, port) self._logged = True return True except SomeRecipientsFailed as error: --- 118,125 ---- if port == 0: port = 'smtp' # Log this just once. if not self._logged: ! log.error('Cannot connect to SMTP server %s on port %s (%s)', ! config.mta.smtp_host, port, e) self._logged = True return True except SomeRecipientsFailed as error:

1 month, 3 weeks

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Mark Sapiro

On 9/18/19 2:29 PM, Manos Pitsidianakis wrote: > > Στις 2019-09-18 19:12, Mark Sapiro έγραψε: >> Is only one list affected, and is it all messages from this list or only >> some? > > Just two messages from this certain list. Subsequent messages and other > activity seems to work properly There should be entries in the mailman.log for each shunted message listing the exception with a traceback and the fact that the message was shunted. What are these entries? > Well there is no connection to postfix at all when the runner starts and > the "Cannot connect to SMTP server" log shows up. Otherwise I'd have > seen something in the postfix logs or tcpdumps in localhost. The "Cannot connect to SMTP server" log message should not occur immediately on startup unless there are queued messages. That log message should only occur on an attempt to actually send a message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Generic Cannot connect to SMTP server error, no outgoing smtp connections

by Stephen Daniel

Does outbound email work for other applications? Does something like mail -s 'Test Email' cubewerk(a)gmail.com < /opt/mailman/core/var/logs/smtp.log work? On Thu, Jun 4, 2026 at 9:10 AM Stefan Bauer via Mailman-users < mailman-users(a)mailman3.org> wrote: > Dear Users, > > I'm debugging since several days a mailman3 installation and can not get > mailman to deliver mails to list members. > > Mailman logs Cannot connect to SMTP server, however the server is > listening, but i see no connection attempts. > > In queue/out, i see changing files all the time: > > drwxrwx--- 2 mailman nogroup 4.0K Jun 4 13:04 . > drwxr-xr-x 15 mailman nogroup 4.0K Jun 4 08:22 .. > -rw-rw---- 1 mailman nogroup 6.1K Jun 4 12:22 > 1780575734.9281623+0ad5f564c9fc5f27750a09b948f3480d9047cbaa.pck.tmp > -rw-rw---- 1 mailman nogroup 6.1K Jun 4 13:04 > 1780578250.2070453+752ca17af5c64af7aab5f0fc61ac2ea28b091825.bak > 038b90c74d8d:/opt/mailman/var/queue/out# ls -alh > total 24K > drwxrwx--- 2 mailman nogroup 4.0K Jun 4 13:04 . > drwxr-xr-x 15 mailman nogroup 4.0K Jun 4 08:22 .. > -rw-rw---- 1 mailman nogroup 6.1K Jun 4 12:22 > 1780575734.9281623+0ad5f564c9fc5f27750a09b948f3480d9047cbaa.pck.tmp > -rw-rw---- 1 mailman nogroup 6.1K Jun 4 13:04 > 1780578250.7552953+6350a013583657c317c0a64b9cf2039dca645974.bak > 038b90c74d8d:/opt/mailman/var/queue/out# > > SMTP/DEBUG-Log is flooded with over and over same attempts: > > ==> /opt/mailman/core/var/logs/smtp.log <== > Jun 04 13:04:46 2026 (26) Using agent: <mailman.mta.deliver.Deliver object > at 0x79ed98555310> > Jun 04 13:04:46 2026 (26) IndividualDelivery to: cubewerk(a)gmail.com > > ==> /opt/mailman/core/var/logs/debug.log <== > Jun 04 13:04:46 2026 (31) [VirginRunner] starting oneloop > Jun 04 13:04:46 2026 (31) [VirginRunner] ending oneloop: 0 > Jun 04 13:04:46 2026 (26) [OutgoingRunner] finishing filebase: > 1780578286.711373+091038a49a00758fdd2ba5265714e2fa31ea4843 > Jun 04 13:04:46 2026 (26) [OutgoingRunner] doing periodic > Jun 04 13:04:46 2026 (26) [OutgoingRunner] committing transaction > Jun 04 13:04:46 2026 (26) [OutgoingRunner] checking short circuit > Jun 04 13:04:46 2026 (26) [OutgoingRunner] ending oneloop: 1 > Jun 04 13:04:46 2026 (26) [OutgoingRunner] starting oneloop > Jun 04 13:04:46 2026 (26) [OutgoingRunner] processing filebase: > 1780578286.7329357+2ec378350ee99307adc287fc8727fb9120a385d3 > Jun 04 13:04:46 2026 (26) [OutgoingRunner] processing onefile > Jun 04 13:04:46 2026 (26) [outgoing] <function deliver at 0x79ed98b85d00>: > <gxZS.-LyKCSHn9UWsyVepCakA9g(a)flTQyy2_BUC0KFtMliiieCkabFXP1SdNnP1xIyNQp-k.xz > > > > ==> /opt/mailman/core/var/logs/smtp.log <== > Jun 04 13:04:46 2026 (26) Using agent: <mailman.mta.deliver.Deliver object > at 0x79ed98a43bf0> > Jun 04 13:04:46 2026 (26) IndividualDelivery to: cubewerk(a)gmail.com > > If i restart the docker-core container, i see a single time the error > "Cannot connect to SMTP server 172.17.0.1 on port 587". > > my config: > > [runner.retry] > sleep_time: 10s > > [webservice] > hostname: 172.18.0.2 > port: 8001 > admin_user: restadmin > admin_pass: restpass > configuration: /etc/gunicorn.cfg > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: 172.18.0.2 > lmtp_port: 8024 > smtp_host: 172.17.0.1 > smtp_port: 587 > smtp_user: > smtp_pass: > smtp_secure_mode: starttls > smtp_verify_hostname: false > smtp_verify_cert: false > configuration: /etc/postfix-mailman.cfg > > [logging.smtp] > level: debug > > [logging.error] > level: debug > > [logging.debug] > level: debug > > [archiver.mail_archive] > enable: no > configuration: /opt/mailman/mail_archive_dummy.cfg > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /etc/mailman-hyperkitty.cfg > > > Any helps is greatly appreciated. > > thank you. > > Stefan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)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 swd(a)pobox.com >

2 weeks

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Manos Pitsidianakis

Thanks for the reply Mark, Στις 2019-09-21 16:19, Mark Sapiro έγραψε: > It's a stretch, but I suggest you examine the list membership and > remove > any invalid local addresses. There aren't any local addresses. > Also, look in the mail server's logs to see if you can see anything > about incoming connections being established and then dropped. Unfortunately no. Listening on all interfaces with tcpdump and there are no packets when mailman starts and the "Cannot connect to SMTP" log appears. It looks like there is no connection at all. Can I use a debugger to see exactly what happens in the runner?

6 years, 8 months

Search results for query "Cannot connect to SMTP server"