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

Uncaught runner exception

by Stephen J. Turnbull

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

4 years, 1 month

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.

4 years, 1 month

Re: Mailman3 not delivering list mail

by Mark Sapiro

On 10/1/20 11:18 AM, gordon(a)dickens.com wrote: > 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' These relate to the messages in the `bad` queue. It seems there is/was andn issue with ownership and/or permissions on some directory or directories is the path `/var/lib/mailman3/queue/virgin`. Is mailman3, queue and virgin user and group `list` and searchable, readable and writable by `list`. Are all the runners running as user `list` ps -fwwA|grep runner > 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 This is delivery of the outgoing message which looks like it was successfully archived. These messages come from `/var/lib/mailman3/queue/out` and after the failure are put in `/var/lib/mailman3/queue/retry` and periodically are moved back to the `out` queue and tried again. > 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. Normally it means exactly what is says. Is your MTA (Postfix or ??) running? Can you `telnet localhost 25` successfully? Note that if the message actually says `local host` and not `localhost`, the setting for smtp_host in the [mta] section of mailman.cfg needs to be fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

Re: signup / registration error - permissions and cert chains

by Victoriano Giralt

El viernes, 31 de diciembre de 2021 1:48:38 (CET) David Newman escribió: > I'd like for regular (non-admin) list subscribers to be able to manage > their subscription preferences and view list archives. That's a good way to go :-) My response is more of a (very) old sysadmin and Django user (since 2008) hunch that a proper one based on code and documentation review, but I've been trying to contribute several times and always (super) Mark Sapiro beats me :-) > If I'm reading the error correctly, this is related to an inability to > verify the cert chain. The /etc/mailman3/settings.py file points to the > same cert and key files used by Nginx, Postfix, and Dovecot. You are right in your diagnose but not in your interpretation (see my comment below inside the traceback). It is certificate related, but not for server TLS, but for CLIENT authentication. > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > EMAIL_HOST_USER = 'dnewman(a)networktest.com' > EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' > EMAIL_USE_TLS = 'True' > EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' > EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' All these settings above are used for SENDING messages and, if I'm not mistaken, the SSL key and cert are used for authenticating the user sending the email. Actually, using TLS and SMTP Auth for localhost is a bit too much. I've been configuring SMTP servers since 1990 and my mail servers just accept mail form localhost, if they are broken into, the user and password have already been exposed :-) > But this might only be for email, not Postorius/Django. You are right (if I also am) > What additional configuration is needed to allow regular users to create > and manage their own accounts? I'd say that is more what is not needed (the SMTP TLS authentication) I'll remove the "noise". These are the tell tale lines: > "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smt > p.py", line 67, in open > self.connection.starttls(keyfile=self.ssl_keyfile, > certfile=self.ssl_certfile) The SMTP Django backend is trying to connect to the mail server to send the Mailman account confirmation message and failing, probably because the user Django runs as cannot open the private key (which is a very sensible thing if that private key is the one used for the web facing TLS certificate, I can tell you how bad in private or search for my name, wasd, apache and VMS ;-)) That certificate is not needed for sending email from Django, and, as I said, not even SMTP Auth for sending via localhost. Actually, doing SMTP Auth on port 25 is not even recommended practice. Happy, healthy, safe and well ventilated New Year to all. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

2 years, 4 months

Uncaught runner exception

by Wolfgang Bock

Hello, I need your help. I got a "Uncaught runner exception: invalid literal for int() with base 10:" Referring to a discussion in Sept. 2019 with Manos Pitsidianakis "Cannot connect to SMTP server localhost on port 25" I did following: stop both postfix and mailman 3 services. Deleted all files in the /var/lib/mailman3/queue directories. Restarted both services. With following configurations: (extracts): /etc/mailman3/mailman.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver 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 ... smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 configuration: python:mailman.config.postfix /var/log/postfix/mail.info Apr 6 00:02:22 ... postfix/postfix-script[31407]: starting the Postfix mail system Apr 6 00:02:22 ... postfix/master[31409]: daemon started -- version 3.4.8, configuration /etc/postfix Apr 6 00:03:09 ... postfix/smtpd[31462]: connect from mout-p-103.mailbox.org[80.241.56.161] Apr 6 00:03:09 ... policyd-spf[31468]: prepend Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=80.241.56.161; helo=mout-p-103.mailbox.org; envelope-from=[mail address]; receiver=<UNKNOWN> Apr 6 00:03:09 ... postfix/smtpd[31462]: D29FE138023E: client=mout-p-103.mailbox.org[80.241.56.161] Apr 6 00:03:09 ... postfix/cleanup[31471]: D29FE138023E: message-id=<6a504834-123a-60f6-3a0e-494623b74523(a)mailbox.org> Apr 6 00:03:25 ... postfix/qmgr[31411]: D29FE138023E: from=<[mail address]>, size=2811, nrcpt=1 (queue active) Apr 6 00:03:25 ... postfix/smtpd[31462]: disconnect from mout-p-103.mailbox.org[80.241.56.161] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Apr 6 00:03:25 ... postfix/lmtp[31481]: D29FE138023E: to=<[list address]>, relay=127.0.0.1[127.0.0.1]:8024, delay=16, delays=16/0.01/0/0.1, dsn=2.0.0, status=sent (250 Ok) Apr 6 00:03:25 ... postfix/qmgr[31411]: D29FE138023E: removed /var/log/mailman3/mailman.log Apr 06 00:02:12 2020 (31148) Master started Apr 06 00:02:13 2020 (31158) rest runner started. Apr 06 00:02:13 2020 (31150) archive runner started. Apr 06 00:02:13 2020 (31159) retry runner started. Apr 06 00:02:14 2020 (31161) virgin runner started. Apr 06 00:02:14 2020 (31154) lmtp runner started. Apr 06 00:02:14 2020 (31155) nntp runner started. Apr 06 00:02:14 2020 (31153) in runner started. Apr 06 00:02:14 2020 (31151) bounces runner started. Apr 06 00:02:15 2020 (31157) pipeline runner started. Apr 06 00:02:15 2020 (31152) command runner started. Apr 06 00:02:15 2020 (31162) digest runner started. Apr 06 00:02:16 2020 (31156) out runner started. 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: '' Apr 06 00:03:26 2020 (31156) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 77, in deliver agent = BulkDelivery(int(config.mta.max_recipients)) File "/usr/lib/python3/dist-packages/mailman/mta/bulk.py", line 50, in __init__ super().__init__() File "/usr/lib/python3/dist-packages/mailman/mta/base.py", line 45, in __init__ config.mta.smtp_host, int(config.mta.smtp_port), Any hints how to solve the problem?? Regards Wolfgang

4 years, 1 month

Re: signup / registration error - permissions and cert chains

by David Newman

On Dec 31, 2021, at 03:43, Victoriano Giralt <victoriano(a)uma.es> wrote: > > El viernes, 31 de diciembre de 2021 1:48:38 (CET) David Newman escribió: >> I'd like for regular (non-admin) list subscribers to be able to manage >> their subscription preferences and view list archives. > > That's a good way to go :-) > > My response is more of a (very) old sysadmin and Django user (since 2008) > hunch that a proper one based on code and documentation review, but I've been > trying to contribute several times and always (super) Mark Sapiro beats me :-) > >> If I'm reading the error correctly, this is related to an inability to >> verify the cert chain. The /etc/mailman3/settings.py file points to the >> same cert and key files used by Nginx, Postfix, and Dovecot. > > You are right in your diagnose but not in your interpretation (see my comment > below inside the traceback). It is certificate related, but not for server > TLS, but for CLIENT authentication. > > >> EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' >> EMAIL_HOST = 'localhost' >> EMAIL_PORT = 25 >> EMAIL_HOST_USER = 'dnewman(a)networktest.com' >> EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' >> EMAIL_USE_TLS = 'True' >> EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' >> EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' > > All these settings above are used for SENDING messages and, if I'm not > mistaken, the SSL key and cert are used for authenticating the user sending > the email. Actually, using TLS and SMTP Auth for localhost is a bit too much. > I've been configuring SMTP servers since 1990 and my mail servers just accept > mail form localhost, if they are broken into, the user and password have > already been exposed :-) > >> But this might only be for email, not Postorius/Django. > > You are right (if I also am) > >> What additional configuration is needed to allow regular users to create >> and manage their own accounts? > > I'd say that is more what is not needed (the SMTP TLS authentication) > > I'll remove the "noise". These are the tell tale lines: > >> "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smt >> p.py", line 67, in open >> self.connection.starttls(keyfile=self.ssl_keyfile, >> certfile=self.ssl_certfile) > > The SMTP Django backend is trying to connect to the mail server to send the > Mailman account confirmation message and failing, probably because the user > Django runs as cannot open the private key (which is a very sensible thing if > that private key is the one used for the web facing TLS certificate, I can > tell you how bad in private or search for my name, wasd, apache and VMS ;-)) > > That certificate is not needed for sending email from Django, and, as I said, > not even SMTP Auth for sending via localhost. Actually, doing SMTP Auth on > port 25 is not even recommended practice. Hi Victoriano, Thanks for this. I could use some clarification on what specific changes you are suggesting. I *think* you are saying to remove the EMAIL_USE_TLS stuff and also move to another port (maybe 587), but I am not sure. Also, the reason I added the TLS in the first place was that I was getting errors without it. And I am unclear why the cert / private key pair do not work for Django when they do work OK for Postfix, Nginx, and Dovecot. Thanks for clarifying — and happy and safe 2022 to you as well! dn > > Happy, healthy, safe and well ventilated New Year to all. > > -- > Victoriano Giralt Innovation Director > Digital Transformation Vicerectorate University of Malaga > +34952131415 SPAIN > ================================================================== > Note: signature.asc is the electronic signature of present message > A: Yes. >> Q: Are you sure ? >>> A: Because it reverses the logical flow of conversation. >>>> Q: Why is top posting annoying in email ? > > > > _______________________________________________ > 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/

2 years, 4 months

Trying to set up mailman3 on my mail server

by Shawn Heisey

I'm having a lot of trouble with trying to set up mailman3 on my mail server. It's on an AWS instance, running Ubuntu 20.04 LTS. All software is installed from Ubuntu packages. Mailman version is 3.2.2. The problem I am trying to troubleshoot first is how this can be happening: Oct 14 11:27:26 2021 (2341) ACCEPT: <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd(a)elyograg.org> Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on port 25 From the shell, I can "telnet localhost 25" successfully, even as the "list" user. Apparmor is disabled. The UFW firewall is enabled, which allows all traffic on the loopback interface. I disabled ipv6 at the kernel level, but had the same problem with ipv6 enabled, so I don't think ipv6 is related at all. I do not see any connections in the postfix log that correspond to the mailman connection error. From a fresh install of mailman, I created two mailing lists. Once upon a time I had those lists active on a Debian 6 machine running mailman 2.1.13 ... I copied the mailing list config from that machine over and used the "import21" facility to import the configuration into the new mailman3 install. That worked without error and I can see the lists and their members with the "mailman" command. I found instructions for integration with postfix, and added the required three config lines to the postfix config. When I try to send a message to the list, I get what I pasted above in the mailman log. I think that means the postfix integration is working, and is forwarding to mailman. I'm hoping somebody can give me some pointers, and if more information is needed for troubleshooting, let me know what is needed. I'm also having trouble with the web UI ... I thought I had found what to do with Apache, but it's having problems and I do not know what to do so it works. The UI is not super important right now, I'd like to get the lists working first. I first tried to get help on the IRC channel, but that appears to be a dead end. I did give it several hours. Thanks, Shawn

2 years, 7 months

Re: Mailman3 not able to deliver emails sent through list, but moderation notifications

by Ruth Ivimey-Cook

See after: On 26/11/2022 18:18, Mark Sapiro wrote: > 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. While this is always true for mailman-core, in some configurations the mailman-web files are also inside the ./var/ tree, and they need to be readable (and, for some, writable) by the process acting as webserver, which may or may not be list:list. In my case (a bit off-piste) I have set mailman-web it up to run as owner=www-data, for example (I forget quite why this was needed now!!). Regards Ruth -- Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

1 year, 5 months

Re: Trying to set up mailman3 on my mail server

by Mark Sapiro

On 10/14/21 7:51 PM, Shawn Heisey wrote: > I'm having a lot of trouble with trying to set up mailman3 on my mail > server. > > It's on an AWS instance, running Ubuntu 20.04 LTS. All software is > installed from Ubuntu packages. Mailman version is 3.2.2. Please see <https://wiki.list.org/x/12812344>[1] > The problem I am trying to troubleshoot first is how this can be happening: > > Oct 14 11:27:26 2021 (2341) ACCEPT: > <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd(a)elyograg.org> > Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on > port 25 > > From the shell, I can "telnet localhost 25" successfully, even as the > "list" user. Apparmor is disabled. The UFW firewall is enabled, which > allows all traffic on the loopback interface. I disabled ipv6 at the > kernel level, but had the same problem with ipv6 enabled, so I don't > think ipv6 is related at all. I do not see any connections in the > postfix log that correspond to the mailman connection error. There's a long thread on this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. Your issue may not be the same, but that one had to do with templates, perhaps created in Postorius, that couldn't be accessed. > From a fresh install of mailman, I created two mailing lists. Once upon > a time I had those lists active on a Debian 6 machine running mailman > 2.1.13 ... I copied the mailing list config from that machine over and > used the "import21" facility to import the configuration into the new > mailman3 install. That worked without error and I can see the lists and > their members with the "mailman" command. I found instructions for > integration with postfix, and added the required three config lines to > the postfix config. > > When I try to send a message to the list, I get what I pasted above in > the mailman log. I think that means the postfix integration is working, > and is forwarding to mailman. Yes, and the message should be archived in whatever archivers are enabled. If the prototype archiver is enabled you should see the message in Mailman's var/archives/prototype/<list-id>/new/ directory and if HyperKitty is enabled, in mailman's database in the hyperkitty_email table. > I'm hoping somebody can give me some pointers, and if more information > is needed for troubleshooting, let me know what is needed. If your web UI isn't working, you probably haven't created any templates in Postorius, but import21 will create templates and if you ran import21 as root, you may have created templates and perhaps other things that can't be accessed by the Mailman user (`list` in your case). All Mailman related commands should be run only by the Mailman user. [1] This FAQ says you should be going to Debian/Ubuntu for support. If you've tried that and are not getting help there, I respectfully submit that you should purge the Debian/Ubuntu package and start over from here <https://docs.mailman3.org/en/latest/install/virtualenv.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

Re: Importing config and archives only partially succeeded?

by Mark Sapiro

On 12/13/20 7:11 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25. > This is weird because other mails have been distributed. > The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id > > Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25 That message is in response to a socket.error exception in attempted delivery. It is logged only once until there is a successful delivery, but the message keeps being retried. > webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0" > <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0" > This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too). Those GETs are part of normal message processing. As I said, they result from core handlers asking HyperKitty for the URL at which the message will be archived so they can add that URL to the Archived-At: header and maybe to a message header or footer. Presumably the one that keeps repeating is the one message/message-id that is throwing the socket.error and being continuously retried. I would stop Mailman and move that one .pck or .bak file out of Mailman's var/queue/out/ directory and then start mailman. You can then examine the queue entry with `mailman qfile` and maybe see what the issue is. > 2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there. OK. > 3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these? > mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings /opt/mailman/venv/bin/django-admin runjobs --list will show you what the jobs are. The hourly jobs are new_lists_from_mailman, thread_starting_email and update_index. The one running long is almost certainly update_index. I would stop running the hourly jobs until you have successfully updated the search index for all lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

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