Search results for "Cannot connect to SMTP server"

[MM3-users] 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

3 years, 6 months

[MM3-users] Re: Mailman3 not able to deliver emails sent through list, but moderation notifications

by Mark Sapiro

On 11/26/22 05:09, Daniel Böhmer wrote: > > During startup /var/log/mailman3/mailman.log receives: > >> Cannot connect to SMTP server localhost on port 25 ... > 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? The article is relevant and mentions the most likely issue which is lack of permission on one or more message templates. Everything in Mailman's var/ directory should be owned by Mailman's user:group - normally `list:list` in Debian packages. I'm only guessing here, but I suspect you ran `mailman import21` at some point as `root`. Never run `mailman` commands as `root`. Only run them as the Mailman user - `list` in Debian packages. Note that Mailman core in Debian Buster is 3.2.1. Since 3.3.5, "The mailman command will refuse to run as root unless the new --run-as-root option is specified." in order to help avoid this issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Can't deliver mails in queue

by Nathanael Schneider

>>> May 19 18:54:40 2021 (8280) Using agent: >>> <mailman.mta.deliver.Deliver object at 0x7fb49b143780> >>> May 19 18:54:40 2021 (8280) IndividualDelivery to: >>> nathanael(a)lumenliquid.net >>> May 19 18:54:40 2021 (8280) Using agent: >>> <mailman.mta.deliver.Deliver object at 0x7fb4974541d0> >>> May 19 18:54:40 2021 (8280) IndividualDelivery to: >>> nathanael(a)lumenliquid.net >> >> The fact that these are the only messages says that the attempt to send >> that message via smtp raised no exception as exceptions would have been >> logged, yet you say there's nothing in the maillog so there was no >> connect to Postfix. What are your settings for smtp_host: and >> smtp_port: in the [mta] section of mailman.cfg? > > I set nothing explicitly as the default options fit my needs, so > localhost:25 it is to my knowledge. Postfix itself was configured by > Plesk and the config for mailman3 was manually added as prescribed. A > manual telnet on localhost 25 gives me the expected 220 message from > postfix. > >> It says the message in queue entry >> 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd is handled >> but gets requeued as >> 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e which >> presumably is handled and requeued again ... > > Ok. Then I just need to figure out why it gets requeued. That also > explains why the out-queue folder keeps creating a single message with > different filenames over and over. But the logs keep silent about the > reason.. Ok I figured out what happened.. First I tried to get more infos by running the runner manually once. And indeed, now I see that the runner "can't connect to SMTP": (venv) mailman@h2831057:~$ runner -C /etc/mailman3/mailman.cfg -o -v --runner=out:0:1 May 20 12:17:24 2021 (20303) out runner started. May 20 12:17:24 2021 (20303) out runner started. May 20 12:17:24 2021 (20303) Using agent: <mailman.mta.deliver.Deliver object at 0x7f8a51649be0> May 20 12:17:24 2021 (20303) Using agent: <mailman.mta.deliver.Deliver object at 0x7f8a51649be0> May 20 12:17:24 2021 (20303) IndividualDelivery to: business(a)lumenliquid.net May 20 12:17:24 2021 (20303) IndividualDelivery to: business(a)lumenliquid.net May 20 12:17:24 2021 (20303) Starting new HTTP connection (1): localhost:8000 May 20 12:17:24 2021 (20303) Starting new HTTP connection (1): localhost:8000 May 20 12:17:24 2021 (20303) Cannot connect to SMTP server localhost on port 25 May 20 12:17:24 2021 (20303) Cannot connect to SMTP server localhost on port 25 May 20 12:17:24 2021 (20303) out runner exiting. May 20 12:17:24 2021 (20303) out runner exiting. Which turns out is the completely wrong error message. SMTP works fine, it is the connection before (localhost:8000) that fails. After some more digging on that particular error I found a thread that linked this error with the use of templates. And indeed, if I add a footer template to my working list, it stops working. If I remove the footer from the broken list, it starts working. So there is something wrong with the templates. After some more digging I looked into the database how my footers were saved and indeed, if I did a wget on the url it timed out because it didn't work. I then dug a little bit more and found the setting "POSTORIUS_TEMPLATE_BASE_URL" which apparently you also have to set. I didn't know because it was mentioned nowhere in the starting guide. So I set it to the url of my frontend and bang, it works (after fixing the urls in the database aswell). It would have been nice though to have a more refined error to figure this out. But its solved now and hopefully this will help someone else as well. -- Nathanael Schneider

5 years

[MM3-users] Re: mail stuck in "out" queue

by Mark Sapiro

On 6/15/20 8:47 AM, rongxinliu(a)cs50.harvard.edu wrote: > > We tried deleting this mailing list and recreating a new one, but no luck. We also tried restarting mailman, and the issue persists. When looking at the mailman.log, messages sent to this problematic mailing list are accepted and archived successfully without a noticeable issue. > > In the smtp.log, also no errors are found except one line "Connection lost during _handle_client()", but this is true for all other mailing lists. Yes, that's normal. ... > However, the mailing list having issue will just stop at: > ....... > Jun 15 14:04:29 2020 (23) Connection lost during _handle_client() There are a couple of things. The post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… includes the log message: Jun 09 17:36:31 2020 (82) Cannot connect to SMTP server postfix on port 25 This is strange as it says that Mailman is trying to connect to hostname `postfix`. Is this actually a legitimate host name on the Mailman server that Mailman can connect to? However, it doesn't seem that this is the issue as that name comes from the smtp_host setting in the [mta] section of the configuration and is global so if it were wrong, it would affect all lists. The fact that there is nothing after "Connection lost during _handle_client()" message means only that the message wasn't successfully delivered. A database issue seems unlikely. Set [logging.smtp] level: debug in mailman.cfg and see if the increased logging helps. It seems to me that the most likely issue is a list member whose address in an smtp RCPT TO command causes some issue with the MTA. Does the MTA actually see a connect and commands for the delivery attempt. I'm also confused by > The out-runner keeps creating new .pck and .bak files endlessly whenever an email gets sent to this mailing list. Mailman should create a .pck in the out queue. Then the out runner processes it and renames it as a .bak during processing for recovery purposes and when done processing removes the .bak. If in the process it encounters retryable errors for one or more recipients, it will remove the successful and perm failure recips from the metadata and queue the message in the retry queue. It should never be just requeueing the message in the out queue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

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

by Stephen J. Turnbull

Krinetzki, Stephan writes: > 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. By that you mean the incoming mail is fine? Or smtp.log is fine? smtp.log should include two (or more) lines for each successful post, like Jan 02 16:09:17 2025 (42985) <43007@turnbull> smtp to list-1(a)turnbull.jp for 1 recips, completed in 0.6027507781982422 seconds Jan 02 16:09:17 2025 (42985) <43007@turnbull> post to list-1(a)turnbull.jp from list-1-owner(a)turnbull.jp, 992 bytes, 1 failures Jan 02 16:09:17 2025 (42985) <43007@turnbull> delivery to list-1-owner(a)turnbull.jp failed with code 550, b'5.1.1 <list-1-owner(a)turnbull.jp>: Recipient address rejected: User unknown in local recipient table' (That last line shows an example of a failure report.) > Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost on port 25 Postfix for some reason doesn't know about the alias "localhost" (it has something to do with trusting the DNS and not reading the /etc/hosts file). 127.0.0.1 works. I don't understand how any lists' posts get delivered at all with that. If it's postfix it's possible that the connection pool is exhausted intermittently (but that wouldn't explain why it's consistently impossible to post to a subset of lists). You can specify that connections from the loopback interfaces are less restricted. That might help. > Even after changing the smtp_host in mailman.cfg this error appears > randomly. Note that > Sadly the mail does not get delivered. :-( -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

10 months, 1 week

[MM3-users] including a template failed

by Wolfgang Bock

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')) ... domain02.de isn't involved in mailman3 either as a user domain nor as a list-domain. After deleting the template mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member: regular:footer the mail to the list is processed without problems: Sep 19 22:56:22 2020 (1436) <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> smtp to mylist(a)list.domain-03.de for 1 recips, completed in 0.21389174461364746 seconds Sep 19 22:56:22 2020 (1436) <000001d68ec7$2553e6e0$6ffbb4a0$(a)wbock.de> post to mylist(a)list.domain-03.de from user(a)domain-01.de, 1331 bytes Please help to solve this problem? Thanks and regards Wolfgang

5 years, 8 months

[MM3-users] Re: Is a directory: '…/mailman/templates'

by Abhilash Raj

You need to downgrade one of the dependency of Mailman, importlib_resources to 1.0.2 version. Depending on how you installed it, you can use pip to install that version. This is a recent change and probably happened if you installed or upgraded your Mailman instance. Abhilash (Sent from mobile device) On Tue, Mar 31, 2020, at 12:53 AM, Stefan Tatschner wrote: > hey folks, > > I am struggling with my mailman server for quite some time now. I am on > 3.3 and the out runner cannot sent emails any more. According to this > issue [1] I found out--by logging the exception as well--, that mailman > has this problem: > > Mar 31 09:34:51 2020 (71057) ACCEPT: > <c1e4aa1be5b61c289c69a66a6d55565333d5a35b.camel(a)rumpelsepp.org> > Mar 31 09:34:52 2020 (71079) Cannot connect to SMTP server 127.0.0.1 on > port 25: [Errno 21] Is a directory: > '/usr/lib/python3.8/site-packages/mailman/templates' > > What the hell is going on here? ☹︎ any ideas what's wrong? > The runner doesn't try to connect to postfix, since it fails with a > strange template error. > > Stefan > > [1]: https://gitlab.com/mailman/mailman/-/issues/514 > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 2 months

[MM3-users] Re: MAILMAN_ARCHIVER_KEY - 401 error

by Mark Sapiro

On 4/12/22 23:54, Torsten R. wrote: > > The only thing left now seems to be some weird message in the mailman.log telling me that it can't connect to the SMTP server listening on localhost port 25. > But I think I will find out why Mailman doesn't want to talk to my mail server. This issue sometimes is due to templates that can't be accessed. See https://lists.mailman3.org/archives/search?mlist=mailman-users%40mailman3.o… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

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

by Mark Sapiro

On 9/22/19 2:11 AM, Manos Pitsidianakis wrote: > > mailman3 tries to get the template I've set via the mailman suite > interface but it assumes it is hosted locally: > 'http://localhost:8000/mailman3/api/templates/list/meli-announce.meli.delive…' > In my setup, they are separate machines. I can't find any way to change > this in the configuration. Also, can't the same template be loaded from > the master's localhost:8001 api? See <https://mailman.readthedocs.io/en/latest/build/lib/mailman/rest/docs/templa…>. There are other ways to set the URI for a template which will work in your case. When you set a template via Postorius, it sets the URI for that template to point to itself to return what it set. In your case, this URI points to localhost which is Postorius' localhost, but it is set in core and core's localhost is a different machine so it doesn't work. You could file an issue at <https://gitlab.com/mailman/postorius/issues> about this. > Haven't fiddled with python for some time, why is this exception catched > by "except socket.error"? Is it a subclass of > requests.exceptions.ConnectionError? The other way around. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Is a directory: '…/mailman/templates'

by Andrew Hodgson

Stefan Tatschner wrote: >I am struggling with my mailman server for quite some time now. I am on >3.3 and the out runner cannot sent emails any more. According to this issue [1] I found out--by logging the exception as well--, that mailman has this problem: >Mar 31 09:34:51 2020 (71057) ACCEPT: <c1e4aa1be5b61c289c69a66a6d55565333d5a35b.camel(a)rumpelsepp.org> >Mar 31 09:34:52 2020 (71079) Cannot connect to SMTP server 127.0.0.1 on port 25: [Errno 21] Is a directory: '/usr/lib/python3.8/site-packages/mailman/templates' I had this issue over the weekend and wasted many hours on it. Downgrade importlib-resources to 1.0.2 and it should work fine. There was a prior post on this list a few days ago as well which I missed. Best. Andrew.

6 years, 2 months

Search results for query "Cannot connect to SMTP server"