Search results for "Cannot connect to SMTP server"

[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

2 years, 8 months

[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

5 years, 7 months

[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?

5 years, 6 months

[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

2 years, 8 months

[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

5 years, 6 months

[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

5 years, 7 months

[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.

5 years, 7 months

[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.

5 years, 7 months

[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

5 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.

2 years, 8 months

Search results for query "Cannot connect to SMTP server"