Search results for "Cannot connect to SMTP server"

[MM3-users] Cannot connect to SMTP server

by mkummini＠cmi.ac.in

Hello. I am setting up a new mailman3 server (debian 11). `mailman3-full` is installed on the same server as postfix (our MTA). There is just one test mailing list now. When I send a message to it (I am a subscriber), mailman3 accepts the message through LMTP. Both the postfix log and mailman.log confirm this. Postfix log: Aug 14 03:21:25 mail postfix/lmtp[4097036]: 44E49272437D: to=<testlist(a)cmi.ac.in>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.15, delays=0.02/0.03/0.01/0.09, dsn=2.0.0, status=sent (250 Ok) mailman.log: Aug 14 03:21:26 2022 (4096856) ACCEPT: <Yvgc3WsoFlpZbypw(a)cmi.ac.in> (The digest.mmdf file shows the test message I sent. Hence mailman3 has received the message from postfix.) However, after this, the postfix log does not show any attempt by mailman3 to send the message to the list members. The following runners have started (after the most recent mailman3 restart) Aug 14 03:19:53 2022 (4096853) archive runner started. Aug 14 03:19:53 2022 (4096863) retry runner started. Aug 14 03:19:53 2022 (4096862) rest runner started. Aug 14 03:19:54 2022 (4096855) command runner started. Aug 14 03:19:54 2022 (4096854) bounces runner started. Aug 14 03:19:55 2022 (4096860) pipeline runner started. Aug 14 03:19:55 2022 (4096866) digest runner started. Aug 14 03:19:55 2022 (4096858) nntp runner started. Aug 14 03:19:55 2022 (4096857) lmtp runner started. Aug 14 03:19:55 2022 (4096865) virgin runner started. Aug 14 03:19:56 2022 (4096856) in runner started. Aug 14 03:19:57 2022 (4096859) out runner started. 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. Following <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/runners/do…>, I tried to create an outgoing test runner, but that resulted in the following errors. >>> from mailman.runners.outgoing import OutgoingRunner >>> from mailman.testing.helpers import make_testable_runner >>> outgoing = make_testable_runner(OutgoingRunner, 'out') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 92, in make_testable_runner return EmptyingRunner(name) File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 79, in __init__ super().__init__(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 53, in __init__ super().__init__(slice, numslices) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 63, in __init__ section = getattr(config, 'runner.' + name) File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 123, in __getattr__ return getattr(self._config, name) AttributeError: 'NoneType' object has no attribute 'runner.out' Here are the lines in mailman.cfg referring to smtp smtp_secure_mode : starttls smtp_host: localhost smtp_port: 587 If you could suggest how I could fix this issue, it would be great. Thank you. Manoj.

4 years, 3 months

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

by Mark Sapiro

On 9/19/19 2:22 AM, Manos Pitsidianakis wrote: > 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/ No. You referred to "shunted" mails. I assumed that mail was winding up in the shunt queue, but this is apparently not the case. >> 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. What is happening is you have three messages in the out queue which are problematic. When Mailman or the out runner is restarted, for some reason the attempt to send these triggers the "Cannot connect to SMTP server" issue which is logged only once. Here's what happens: The oldest .pck file in the out queue gets picked up by the out runner and renamed to a .bak. The runner attempts to send the message and gets a socket.error exception so it requeues the message to be tried again. This removes the .bak and creates a new .pck. This process continues so the files keep getting renamed. I suggest you stop Mailman, and move the three files out of the out/ queue, and then restart Mailman. This should stop the out runner from "spinning" on these messages. Then you can examine the files with Mailman's 'bin/mailman qfile' command and see if you can identify something in the recipients list or other metadata that might be causing this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

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

by Manos Pitsidianakis

Στις 2019-09-19 18:52, Mark Sapiro έγραψε: > No. You referred to "shunted" mails. I assumed that mail was winding up > in the shunt queue, but this is apparently not the case. But they are. Not exactly when or why but they show up in queue/shunt and queue/out at times. (maybe because I used mailman unshunt?) > > This should stop the out runner from "spinning" on these messages. Then > you can examine the files with Mailman's 'bin/mailman qfile' command > and > see if you can identify something in the recipients list or other > metadata that might be causing this. 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.

7 years, 1 month

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

6 years, 1 month

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

by Mark Sapiro

On April 25, 2026 10:27:06 PM GMT+02:00, Craig Leres via Mailman-users <mailman-users(a)mailman3.org> wrote: > >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: Did you by chance run import21 as root or another non-mailman user resulting in template files unreadable by Mailman? > Apr 25 12:32:22 2026 (82977) Cannot connect to SMTP server 127.0.0.1 on port 25 This is a well known issue. See <https://gitlab.com/mailman/mailman/-/work_items/582> and related issues referenced therein. >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. The default web service port (Postorius and HyperKitty) is 8000. Port 8001 is Mailman core's rest api. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

6 months, 2 weeks

[MM3-users] Re: Mailman3 moving to new server, not able to establish SMTP connection

by Andrew Hodgson

Guys, This has been fixed and was nothing to do with the SMTP server. I stepped through the code of the outgoing runner and found that an exception was being handled and giving an unhelpful error message. Once I got to the real exception I found it was due to this error: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… downgrading importlib_resources fixed the issue straight away. Thanks. Andrew. From: Andrew Hodgson Sent: 28 March 2020 16:41 To: mailman-users(a)mailman3.org Subject: Mailman3 moving to new server, not able to establish SMTP connection Hi, Whilst we are all stuck in doors I have started a project to move Mailman3 from a Docker installation to a new server using a Python venv. Old server was Debian Jessie and the new one is Buster. Using Exim with stock config. Everything seems to be going ok but mail isn't delivering (cannot connect to SMTP server). I have /opt/mailman which I did chown -R list:list mailman.cfg has following MTA settings: [mta] incoming: mailman.mta.exim4.LMTP configuration: python:mailman.config.exim4 I wrote a Systemd unit which starts Mailman from the venv and started up Mailman once I got Postgres sorted so it would create the necessary files in the var directory structure. One thing I noticed and had to fix is that it doesn't creat the directories for existing lists, and the Exim config examples out there check for the existance of those directories to identify whether the address exists. I created those anyway and set ownership perms as before. Once I fixed that I sent a test message to the owner address and that routed correctly and the headers indicated the message was sent back to localhost by Mailman. However I can't get it to route a list message, here is a log showing the start of the Mailman master processes and me sending a test message from Outlook (so incoming mail is routing ok): Mar 28 16:03:20 2020 (21877) Master started Mar 28 16:03:32 2020 (21889) lmtp runner started. Mar 28 16:03:32 2020 (21896) virgin runner started. Mar 28 16:03:32 2020 (21887) command runner started. Mar 28 16:03:32 2020 (21890) nntp runner started. Mar 28 16:03:32 2020 (21886) bounces runner started. Mar 28 16:03:33 2020 (21892) pipeline runner started. Mar 28 16:03:33 2020 (21888) in runner started. Mar 28 16:03:33 2020 (21895) retry runner started. Mar 28 16:03:34 2020 (21894) rest runner started. [2020-03-28 16:03:34 +0000] [21894] [INFO] Starting gunicorn 20.0.4 [2020-03-28 16:03:34 +0000] [21894] [INFO] Listening at: http://127.0.0.1:8001 (21894) [2020-03-28 16:03:34 +0000] [21894] [INFO] Using worker: sync [2020-03-28 16:03:34 +0000] [21963] [INFO] Booting worker with pid: 21963 Mar 28 16:03:34 2020 (21885) archive runner started. [2020-03-28 16:03:34 +0000] [21965] [INFO] Booting worker with pid: 21965 Mar 28 16:03:34 2020 (21897) digest runner started. Mar 28 16:03:36 2020 (21891) out runner started. Mar 28 16:04:25 2020 (21888) ACCEPT: <AM0PR08MB39085771D0E2D9114FDE8E83AFCD0(a)AM0PR08MB3908.eurprd08.prod.outlook.com<mailto:AM0PR08MB39085771D0E2D9114FDE8E83AFCD0@AM0PR08MB3908.eurprd08.prod.outlook.com>> Mar 28 16:04:26 2020 (21885) HyperKitty archived message <AM0PR08MB39085771D0E2D9114FDE8E83AFCD0(a)AM0PR08MB3908.eurprd08.prod.outlook.com<mailto:AM0PR08MB39085771D0E2D9114FDE8E83AFCD0@AM0PR08MB3908.eurprd08.prod.outlook.com>> to https://lists.hodgsonfamily.org/hyperkitty/list/blind-sysadmins@lists.hodgs… [28/Mar/2020:16:04:26 +0000] "GET /3.0/lists/blind-sysadmins(a)lists.hodgsonfamily.org<mailto:/3.0/lists/blind-sysadmins@lists.hodgsonfamily.org> HTTP/1.1" 200 445 "-" "GNU Mailman REST client v3.3.0" Mar 28 16:04:27 2020 (21891) Cannot connect to SMTP server localhost on port 25 [28/Mar/2020:16:04:27 +0000] "GET /3.0/lists/blind-sysadmins(a)lists.hodgsonfamily.org/config<mailto:/3.0/lists/blind-sysadmins@lists.hodgsonfamily.org/config> HTTP/1.1" 200 2595 "-" "GNU Mailman REST client v3.3.0" [28/Mar/2020:16:04:27 +0000] "GET /3.0/users/andrew(a)hodgson.io<mailto:/3.0/users/andrew@hodgson.io> HTTP/1.1" 200 439 "-" "GNU Mailman REST client v3.3.0" Now in the out queue I have this: root@elrond:/opt/mailman# ls -la /opt/mailman/var/queue/out total 32 drwxrwx--- 2 list list 4096 Mar 28 16:34 . drwxr-xr-x 14 list list 4096 Mar 28 13:25 .. -rw-rw---- 1 list list 11152 Mar 28 16:34 1585413255.2412584+390ab148e589108ed9e849445e5e90410f69def3.bak -rw-rw---- 1 list list 11152 Mar 28 16:34 1585413255.4891446+75bde47331619263b05f582c28ceb85a13bb5265.pck.tmp There is no connection attempt in the Exim log from Mailman and I can connect to localhost:25. This is a dualstack machine and I was wondering whether we had any IPV6 issues (I had an issue with Gunicorn and Nginx routing traffic due to this earlier that I had to sort), but as owner addresses are working I don't know what is different on that. Any suggestions? Thanks. Andrew.

6 years, 7 months

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

by Manos Pitsidianakis

Στις 2019-09-22 09:11, Manos Pitsidianakis έγραψε: > 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? > I created an ssh-tunnel that forwards postorious 8000 port to localhost as a systemd service to workaround this temporarily.

7 years, 1 month

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

by Mark Sapiro

On 9/21/19 1:00 PM, Manos Pitsidianakis wrote: > > Can I use a debugger to see exactly what happens in the runner? You might be able to run the runner under pdb <https://docs.python.org/3.2/library/pdb.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Mailman3 moving to new server, not able to establish SMTP connection

by Andrew Hodgson

Hi, Whilst we are all stuck in doors I have started a project to move Mailman3 from a Docker installation to a new server using a Python venv. Old server was Debian Jessie and the new one is Buster. Using Exim with stock config. Everything seems to be going ok but mail isn't delivering (cannot connect to SMTP server). I have /opt/mailman which I did chown -R list:list mailman.cfg has following MTA settings: [mta] incoming: mailman.mta.exim4.LMTP configuration: python:mailman.config.exim4 I wrote a Systemd unit which starts Mailman from the venv and started up Mailman once I got Postgres sorted so it would create the necessary files in the var directory structure. One thing I noticed and had to fix is that it doesn't creat the directories for existing lists, and the Exim config examples out there check for the existance of those directories to identify whether the address exists. I created those anyway and set ownership perms as before. Once I fixed that I sent a test message to the owner address and that routed correctly and the headers indicated the message was sent back to localhost by Mailman. However I can't get it to route a list message, here is a log showing the start of the Mailman master processes and me sending a test message from Outlook (so incoming mail is routing ok): Mar 28 16:03:20 2020 (21877) Master started Mar 28 16:03:32 2020 (21889) lmtp runner started. Mar 28 16:03:32 2020 (21896) virgin runner started. Mar 28 16:03:32 2020 (21887) command runner started. Mar 28 16:03:32 2020 (21890) nntp runner started. Mar 28 16:03:32 2020 (21886) bounces runner started. Mar 28 16:03:33 2020 (21892) pipeline runner started. Mar 28 16:03:33 2020 (21888) in runner started. Mar 28 16:03:33 2020 (21895) retry runner started. Mar 28 16:03:34 2020 (21894) rest runner started. [2020-03-28 16:03:34 +0000] [21894] [INFO] Starting gunicorn 20.0.4 [2020-03-28 16:03:34 +0000] [21894] [INFO] Listening at: http://127.0.0.1:8001 (21894) [2020-03-28 16:03:34 +0000] [21894] [INFO] Using worker: sync [2020-03-28 16:03:34 +0000] [21963] [INFO] Booting worker with pid: 21963 Mar 28 16:03:34 2020 (21885) archive runner started. [2020-03-28 16:03:34 +0000] [21965] [INFO] Booting worker with pid: 21965 Mar 28 16:03:34 2020 (21897) digest runner started. Mar 28 16:03:36 2020 (21891) out runner started. Mar 28 16:04:25 2020 (21888) ACCEPT: <AM0PR08MB39085771D0E2D9114FDE8E83AFCD0(a)AM0PR08MB3908.eurprd08.prod.outlook.com> Mar 28 16:04:26 2020 (21885) HyperKitty archived message <AM0PR08MB39085771D0E2D9114FDE8E83AFCD0(a)AM0PR08MB3908.eurprd08.prod.outlook.com> to https://lists.hodgsonfamily.org/hyperkitty/list/blind-sysadmins@lists.hodgs… [28/Mar/2020:16:04:26 +0000] "GET /3.0/lists/blind-sysadmins(a)lists.hodgsonfamily.org HTTP/1.1" 200 445 "-" "GNU Mailman REST client v3.3.0" Mar 28 16:04:27 2020 (21891) Cannot connect to SMTP server localhost on port 25 [28/Mar/2020:16:04:27 +0000] "GET /3.0/lists/blind-sysadmins(a)lists.hodgsonfamily.org/config HTTP/1.1" 200 2595 "-" "GNU Mailman REST client v3.3.0" [28/Mar/2020:16:04:27 +0000] "GET /3.0/users/andrew(a)hodgson.io HTTP/1.1" 200 439 "-" "GNU Mailman REST client v3.3.0" Now in the out queue I have this: root@elrond:/opt/mailman# ls -la /opt/mailman/var/queue/out total 32 drwxrwx--- 2 list list 4096 Mar 28 16:34 . drwxr-xr-x 14 list list 4096 Mar 28 13:25 .. -rw-rw---- 1 list list 11152 Mar 28 16:34 1585413255.2412584+390ab148e589108ed9e849445e5e90410f69def3.bak -rw-rw---- 1 list list 11152 Mar 28 16:34 1585413255.4891446+75bde47331619263b05f582c28ceb85a13bb5265.pck.tmp There is no connection attempt in the Exim log from Mailman and I can connect to localhost:25. This is a dualstack machine and I was wondering whether we had any IPV6 issues (I had an issue with Gunicorn and Nginx routing traffic due to this earlier that I had to sort), but as owner addresses are working I don't know what is different on that. Any suggestions? Thanks. Andrew.

6 years, 7 months

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

by Stefan Tatschner

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

6 years, 7 months

Search results for query "Cannot connect to SMTP server"