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

2 years, 11 months

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

1 year, 5 months

WG: Re: Uncaught runner exception

by Wolfgang Bock

Hello Stephen, I have to apologize for misspelling your name! Sorry! Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Wolfgang Bock via Mailman-users <mailman-users(a)mailman3.org> Gesendet: Montag, 6. April 2020 23:44 An: 'mailman-users' <mailman-users(a)mailman3.org> Betreff: [MM3-users] Re: Uncaught runner exception 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/ _______________________________________________ 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, 1 month

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

2 years, 1 month

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.

1 year, 9 months

Re: Uncaught runner exception

by Mark Sapiro

On 4/7/20 3:22 AM, Wolfgang Bock via Mailman-users wrote: > 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. Can you successfully telnet localhost 25 from a shell on the 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

Re: Uncaught runner exception

by Wolfgang Bock

Yes, and I made all the tests as discribed here: https://workaround.org/ispmail/buster/relaying-through-postfix/ including the swaks test mentioned before output of sudo netstat -lntup | grep ":25" tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 20660/master tcp6 0 0 :::25 :::* LISTEN 20660/master output of sudo lsof -i :25 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME master 20660 root 13u IPv4 1474228 0t0 TCP *:smtp (LISTEN) master 20660 root 14u IPv6 1474229 0t0 TCP *:smtp (LISTEN) Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Dienstag, 7. April 2020 21:28 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Uncaught runner exception On 4/7/20 3:22 AM, Wolfgang Bock via Mailman-users wrote: > 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. Can you successfully telnet localhost 25 from a shell on the server? -- 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, 1 month

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

3 years, 7 months

Re: Mailman3 not delivering list mail

by gordon＠dickens.com

Hi Mark, I have errors like these in the mailman3 logs but they occurred earlier (that is prior to my attempting to post messages to the new mailman3 mailing list and which are not echoed to list members): Oct 01 11:08:22 2020 (7895) Skipping and preserving unparseable message: 1601564901.8696995+c2b86623e2dcc8e9800b10ca2bcf8b82e8d8d662 Oct 01 11:08:23 2020 (7895) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1601564902.28165 63+16bd684dfb18c6175f3e7b0b11312cb203dc9c89.pck' Oct 01 11:08:23 2020 (7895) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 158, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1601564902.2816563+16bd684dfb18c6175f3e7b0b11312cb203dc9c89.pck' The above errors occurred prior to the time that I attempted to send to the mailman3 list. However, here is what I see in the logs immediately after I sent a message to the list and which was not then echoed to list members: Oct 01 11:51:03 2020 (7888) ACCEPT: <f92eeaad-245c-124b-dd09-b31a6b3c5686(a)dickens.com> Oct 01 11:51:07 2020 (7885) HyperKitty archived message <f92eeaad-245c-124b-dd09-b31a6b3c5686(a)dickens.com> to https://georgiajets.org /mailman3/hyperkitty/list/members(a)georgiajets.org/message/NUOU6UQ6DSHSK2WKNVZFIN5AELK5EYBU/ Oct 01 11:51:07 2020 (7891) Cannot connect to SMTP server localhost on port 25 Please note the message about the SMTP server not being able to connect to local host on port 25. Please let me know what you think is wrong and how to fix it. Thanks, Gordon

3 years, 7 months

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.

4 years, 1 month

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