Search results for "Cannot connect to SMTP server localhost on port 25" - Mailman-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

5 years, 7 months

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/

4 years, 6 months

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

5 years

Re: including a template failed

by Mark Sapiro

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.l… 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

4 years, 6 months

Re: Uncaught runner exception

by Wolfgang Bock

Hello Mark, thanks for your hint. Postfix is runnig as mta on my machine. I tested port 25 with swaks ->mail to user on server: localhost port 25 -> everything fine Mailman is configured with localhost for incoming and outgoing mails. After stopping mailman3, deleting all files in the queue directories, restart mailman3 I sent a test-mail /var/log/mailman3/mailman.log Apr 07 12:08:23 2020 (28198) Master started Apr 07 12:08:24 2020 (28206) out runner started. Apr 07 12:08:24 2020 (28202) command runner started. Apr 07 12:08:24 2020 (28203) in runner started. Apr 07 12:08:24 2020 (28200) archive runner started. Apr 07 12:08:24 2020 (28201) bounces runner started. Apr 07 12:08:24 2020 (28210) retry runner started. Apr 07 12:08:25 2020 (28208) rest runner started. Apr 07 12:08:25 2020 (28212) digest runner started. Apr 07 12:08:25 2020 (28205) nntp runner started. Apr 07 12:08:26 2020 (28211) virgin runner started. Apr 07 12:08:26 2020 (28207) pipeline runner started. Apr 07 12:08:26 2020 (28204) lmtp runner started. Apr 07 12:09:19 2020 (28203) ACCEPT: <000f01d60cc4$96c9a8d0$c45cfa70$@[domain]> Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server localhost on port 25 I have no idea what to do for solving my problems. Regards from Hamburg Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Montag, 6. April 2020 23:50 An: Wolfgang Bock <mailinglisten(a)wbock.de> Betreff: Re: [MM3-users] Re: Uncaught runner exception On 4/6/20 2:44 PM, Wolfgang Bock via Mailman-users wrote: > Thank you Steven for your reply! > > I Set smtp_server to port 25 and got a "Cannot connect ro SMTP Server > on port 25", the former error message didn't show again. > > As I see port 25 is reseved for postfix. So I have to fiddle out how > mailman3 could also use this port for sending mails out. .... You need an MTA for Mailman to deliver its mail to. Normally this will be Postfix, sendmail, Exim, etc running on localhost and listening on port 25. Do you have such an MTA running on localhost? Note, Mailman does not directly send mail to end recipients. It only delivers mail to an outgoing MTA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

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

5 years, 7 months

Mailman3 not able to deliver emails sent through list, but moderation notifications

by Daniel Böhmer

Hello Mailman users, I've been using Mailman2 for 10+ years and have recently upgraded to Debian Buster with Mailman3. I've tried to setup Mailman3 similarly but it fails to deliver emails sent through a list. I do receive all moderation notifications at the same time. During startup /var/log/mailman3/mailman.log receives: > Cannot connect to SMTP server localhost on port 25 but I've made sure postfix is listening on *:25 for both IPv4 and IPv6. When sending a message to a list the same file receives: > Nov 25 11:38:14 2022 (70371) ACCEPT: <MESSAGEID@HOST> (message ID and host redacted) and nothing else happens: no more log messages, Postfix logs the email sent TO Mailman but doesn't log anything about emails sent BY Mailman. If Mailman fails to send emails via Postfix I'd expect it to log error messages but it doesn't seem to do so. I found this article stating the the SMTP error message might be misleading: https://blog.tfiu.de/mailman3-cannot-connect-to-smtp-server-localhost-on-po… How to further debug this? What could be wrong with my Mailman3 instance and how to fix it? Kind regards Daniel Böhmer

2 years, 4 months

Re: Uncaught runner exception

by Wolfgang Bock

Thank you Steven for your reply! I Set smtp_server to port 25 and got a "Cannot connect ro SMTP Server on port 25", the former error message didn't show again. As I see port 25 is reseved for postfix. So I have to fiddle out how mailman3 could also use this port for sending mails out. .... Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Gesendet: Montag, 6. April 2020 14:56 An: Wolfgang Bock <mailinglisten(a)wbock.de> Cc: 'mailman-users' <mailman-users(a)mailman3.org> Betreff: [MM3-users] Uncaught runner exception Wolfgang Bock via Mailman-users writes: > smtp_host: Tried with 127.0.0.1/localhost/server ip or FQDN=servername > smtp_port: (got a "cannot connect to SMTP Server on port 25") so I let this > item empty ... This is your problem. By default, it should be port 25. Apparently there is no fallback for this in case it's left empty. (I would guess if you commented it out, it *would* fall back to port 25. > Apr 06 00:03:26 2020 (31153) ACCEPT: > <6a504834-123a-60f6-3a0e-494623b74523(a)mailbox.org> > Apr 06 00:03:26 2020 (31156) Uncaught runner exception: invalid literal for > int() with base 10: '' This is saying int() was called with the empty string as argument. > Apr 06 00:03:26 2020 (31156) Traceback (most recent call last): [intermediate frames omitted] > File "/usr/lib/python3/dist-packages/mailman/mta/base.py", line 45, in > __init__ > config.mta.smtp_host, int(config.mta.smtp_port), The call to int() in the line above is getting the empty value from the config file. Changing smtp_port to '25' (or the appropriate value) in the config file will prevent the "Uncaught runner exception". If localhost's smptd is not listening on port 25, as the comment above seems to indicate, you either need to - find out the correct value if smptd is listening on a different port, - enable that daemon if it's not running, or - point smtp_host at a functioning outgoing mail server if localhost is not expected to be a mail server. In the latter two cases you also need to make sure smtp_port is correct for the server you use. There are some other, rarer and more complicated, possibilities, so if your answer is "none of the above", feel free to say so. But check those first, please. Steve _______________________________________________ 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/

5 years

Re: including a template failed

by Mark Sapiro

On 9/23/20 3:03 PM, Wolfgang Bock via Mailman-users wrote: > > 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/' Can you get https://localhost/mailman3/postorius/api/templates/list/mylist.lists.domain… on the Mailman machine? > 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'"))) The 'HTTPSConnectionPool' message has nothing to do with the 'Cannot connect' issue. > 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 And I wonder why it's trying to connect to localhost when smtp_host is mail.example.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

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

2 years, 8 months

Mailman-users search results for query "Cannot connect to SMTP server localhost on port 25"