Search results for "Cannot connect to SMTP server"

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

by Mark Sapiro

On 8/13/22 15:57, Mark Sapiro wrote: > > 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? I think that should be /var/lib/mailman3/templates in the debian package. Also, all that directory and all its subordinate directories and files should be user:group list:list. If you ever ran Mailman core as `root` and not as user `list`, this can create things that `list` can't read. See these threads: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…, https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and perhaps others from this search https://lists.mailman3.org/archives/search?q=Cannot+connect+to+SMTP+server -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

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

by Mark Sapiro

On 9/21/19 1:28 AM, Manos Pitsidianakis wrote: > > I cannot discern anything in the qfiles. It'd take some effort to > deanonymise them for posting here. > > I've had new posts in the list and they get stuck as well. It's a stretch, but I suggest you examine the list membership and remove any invalid 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

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

by Manos Pitsidianakis

Hello, I've been getting "Cannot connect to SMTP server localhost on port 25" from runner "out" in mailman.log over some mails stuck in shunt queue, postfix logs show nothing when this happens, tcpdump on lo interface port 25 shows nothing. The log shows up when I start mailman, and then it seems not to show up again. This is my mailman.cfg's relevant parts: [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix I can do 'telnet localhost 25' just fine, including as mailman user. I can send and receive mail on my mail server. I tried making a test list and sent/received messages fine. smtp debug logs show "Using agent: <mailman.mta.deliver.Deliver object at 0x7fdd9793c940>" and "IndividualDelivery to: <email(a)address.tld>" on repeat, where the email address is one of the addresses of the shunted mails. version 3.2.2

7 years

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

by Manos Pitsidianakis

Thank you for your prompt response Mark, Στις 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 > Do some deliveries of the problem message succeed? > I think not, the IndividualDelivery lines list all all recipients (list is small so I was able to check) > Postfix can return a 421 status > and drop the connection if there are too many invalid local recipients, > although I don't know if this would apply in the VERP case. 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.

7 years

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

by Stefan Bauer

Yes it does. Am Do., 4. Juni 2026 um 15:33 Uhr schrieb Stephen Daniel <swd(a)pobox.com>: > 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 >> >

3 months, 3 weeks

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

by Manos Pitsidianakis

Thank you again for your reply, Mark. Στις 2019-09-18 21:53, Mark Sapiro έγραψε: > What are these entries? I have these log entries, are these what you were referring to? https://paste.debian.net/hidden/37d863f6/ > > 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. I think the problematic e-mails that cause this issue are stuck on the outgoing queue. Right now there are 2 pck files and one .bak in var/queue/out changing filenames repeatedly.

7 years

[MM3-users] Re: Uncaught runner exception

by Stephen J. Turnbull

Wolfgang Bock via Mailman-users writes: > I tested port 25 with swaks ->mail to user on server: localhost > port 25 -> everything fine What is "swaks"? > Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server > localhost on port 25 Is it possible that Postfix is configured for TLS connections only? If so, it is probably listening on port 465 (the "submissions" port, AKA ssmtp and smtps) or (less likely) 587 (the "submission" port -- no trailing "s"). Mailman needs to be configured correctly for this. See https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht… It's barely possible that Postfix is listening on port 25 but insists on TLS. But that's very unusual, and I think that would produce a SMTP error such as "Need STARTTLS" or "Need SASL" (which happen *after* the TCP connection is established) instead of "Cannot connect" (which suggests a TCP error before a connection is completed). > I have no idea what to do for solving my problems. That's when we're most of service. At least, I hope so! :-) Steve

6 years, 5 months

[MM3-users] Re: including a template failed

by Wolfgang Bock

Dear Mark, Q: Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li sts.domain-03.de/list:member:regular:footer on the Mailman machine? A: No Q: What is your setting for POSTORIUS_TEMPLATE_BASE_URL? A: was: POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' Changed it to: POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' Now another problem occurs: Sep 23 22:51:34 2020 (13492) Cannot connect to SMTP server localhost on port 25 HTTPSConnectionPool ... 'localhost' doesn't match either of 'blog.domain-04.de', 'lists.domain-04.de', 'mail.domain-04.de', 'domain-04.de', 'www.domain-04.de'"))) Port 25 entry results from the manual regarding the postfix configuration: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht ml e.g.: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Sonntag, 20. September 2020 01:05 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: including a template failed On 9/19/20 2:47 PM, Wolfgang Bock via Mailman-users wrote: > Hi, > > I created a new mailinglist and got during the test-process the > following errormessage in my mailman.log after: > ... > Sep 19 22:55:08 2020 (1433) ACCEPT: > <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> > > Errors: > > Sep 19 22:55:09 2020 (1436) Cannot connect to SMTP server localhost on > port > 25 > HTTPSConnectionPool(host='webmail.domain-02.de', port=443): Max > retries exceeded with url: > /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list: > member :regular:footer (Caused by NewConnectionError('<urllib3.connec > tion.VerifiedHTTPSConnection object at 0x7fc8380f1748>: Failed to > establish a new connection: [Errno -2] Name or service not known')) > ... This is wierd. It looks like we are trying to establish a connection to host='webmail.domain-02.de', port=443 in order to GET /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member :regular:footer, but the error says "Cannot connect to SMTP server localhost on port 25". I have no idea how port 25 is coming into it. Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li sts.domain-03.de/list:member:regular:footer on the Mailman machine? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? -- 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/

6 years

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

by mkummini＠cmi.ac.in

Thank you! ownership and permissions of the template files was the problem. Manoj.

4 years, 1 month

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

by Mark Sapiro

On 9/18/19 11:29 AM, Manos Pitsidianakis wrote: > Hello, > > I've been getting "Cannot connect to SMTP server localhost on port 25" > from runner "out" in mailman.log over some mails stuck in shunt queue, > postfix logs show nothing when this happens, tcpdump on lo interface > port 25 shows nothing. The log shows up when I start mailman, and then > it seems not to show up again. That log message is only written once. It won't be written again unless the out runner is restarted or there is a successful delivery followed by another socket.error. > I can do 'telnet localhost 25' just fine, including as mailman user. I > can send and receive mail on my mail server. I tried making a test list > and sent/received messages fine. Is only one list affected, and is it all messages from this list or only some? > smtp debug logs show "Using agent: <mailman.mta.deliver.Deliver object > at 0x7fdd9793c940>" and "IndividualDelivery to: <email(a)address.tld>" on > repeat, where the email address is one of the addresses of the shunted > mails. Do some deliveries of the problem message succeed? I.e., in the normal case without failure, there will be one "IndividualDelivery to: <email(a)address.tld>" message for each recipient in the recipients list. In the shunted message case, the msgdata object in the shunted pickle contains the recipients. Are there "IndividualDelivery to: <email(a)address.tld>" entries for some but not all recipients. Is the last of these an invalid local address? (Postfix can return a 421 status and drop the connection if there are too many invalid local recipients, although I don't know if this would apply in the VERP case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Search results for query "Cannot connect to SMTP server"