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

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/

6 years, 5 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

4 years, 1 month

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

6 years

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, 4 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

3 years, 9 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/

6 years, 5 months

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, 5 months

Incorrect error log message in OutgoingRunner._dispose()

by Stephen J. Turnbull

Craig Leres via Mailman-users writes: > 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: > > Apr 25 12:32:22 2026 (82977) Cannot connect to SMTP server > 127.0.0.1 on port 25 > > 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. That is a bug. The error isn't a temporary failure, at least not if it occurs several times. Also, I don't see how that error could result from the exception below. > 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"))) That suggests that Postorius isn't running. Port 8000 is the default port used by Postorius (and if running, HyperKitty). The problem is that Postorius and HyperKitty are intentionally separate applications because a lot of sites wanted the ability write their own. I don't really understand the design, but what happens is that when you configure a template via Postorius, it gets stored in storage accessible to Postorius. What Postorius returns to Mailman is a URL for Mailman core to query to retrieve the template from Postorius. Core fetches from that URL, then applies it to the outgoing message. The first thing to do is to check that all your host and port configurations are consistent. The defaults are all localhost (but you should specify either 127.0.0.1 or ::1 because Postfix doesn't look in /etc/hosts at all and we've seen cases where one program thinks it's using IPv4 and the other IPv6), and the ports are 8000 for Django (Postorius and HyperKitty, configured in settings.py) and 8001 for the core REST API (configured in mailman.cfg). (If the defaults are satisfactory you may not see any settings for those in settings.py and mailman.cfg, depending on how you created those conffiles.) Then make sure Postorius is running. At least try running Postorius and then "mailman unshunt" to see if that is the problem. If for some reason you want to normally run Mailman core without Postorius, then you will have to either edit the templates in place in the Mailman package, or add local directory to the search path (offhand I don't know if there is one, the fallback template directory may be hard-coded). I guess it would also be possible to write a very lightweight template manager process that emulates the Postorius API endpoint, but that wouldn't give you a GUI for template management. You'd still need to run Postorius for that unless you're really into web development. > I'm using the default webservice port (8001) "webservice" in mailman.cfg refers to the REST API. The web UIs run in different processes and use 8000 (by default). > so I would not expect anything to ever be listening on 8000. > > When I stop the runners, the problematic queue file is moved to the > shunt queue. That's normal. Once you get the configuration straightened out, "mailman unshunt" should cause those posts and other mail to flow properly. > ! except socket.error: Ah, that's quite generic, and I see now why that would catch the attempt to fetch the template. It's obnoxious that the dev who wrote the code chose to throw away the exception data in favor of a generic "something's broke" message, but that happens. It was probably written before the web GUI for managing templates was added. Regards, Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 4 weeks

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, 1 month

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

6 years, 5 months

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