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

Re: Held messages not delivered after approval

by Stephen J. Turnbull

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

6 months, 1 week

Re: Held messages not delivered after approval

by Krinetzki, Stephan

Hi Mark, >That's a misleading message. It's been improved by https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the underlying issue is inability to access a header or footer template when decorating the message. This in turn is most likely >caused by some template(s) in Mailman's var/templates/ directory being owned by `root` or some other non-mailman user and not readable by the Mailman user which in turn most likely results from running `mailman import21` as root. You are my hero! After "patching" the outgoing.py file with the error messages I got Aug 06 09:52:51 2025 (443278) Cannot connect to SMTP server 127.0.0.1 on port 25: HTTPSConnectionPool(host='lists.example.com', port=443): Max retries exceeded with url: /postorius/api/templates/list/hpc-admintreffen-info.lists.example.com/list:member:regular:footer (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1006)'))) And was shocked. Why is there an SSL Certificate Error? Why can't python requests verify the certificate? So I googled a bit and found, that we can fix this be editing the cacert.pem of certifi. I did, but the error was still there. So I checked my https VHost (Apache btw) and there was a wrong chain in it. Oof. An error, that a browser does not see, but any ssl client. I fixed it and boom - everything works again. Thank you again and thank you Stephen for trying to resolve the problem 😊 -- Stephan Krinetzki IT Center Gruppe: Anwendungsbetrieb und Cloud Abteilung: Systeme und Betrieb RWTH Aachen University Seffenter Weg 23 52074 Aachen Tel: +49 241 80-24866 Fax: +49 241 80-22134 krinetzki(a)itc.rwth-aachen.de www.itc.rwth-aachen.de Social Media Kanäle des IT Centers: https://blog.rwth-aachen.de/itc/ https://www.facebook.com/itcenterrwth https://www.linkedin.com/company/itcenterrwth https://twitter.com/ITCenterRWTH https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 5, 2025 6:19 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Held messages not delivered after approval On 8/5/25 02:06, Krinetzki, Stephan wrote: > Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost > on port 25 > > The last error is a very often in the mailman.log: That's a misleading message. It's been improved by https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the underlying issue is inability to access a header or footer template when decorating the message. This in turn is most likely caused by some template(s) in Mailman's var/templates/ directory being owned by `root` or some other non-mailman user and not readable by the Mailman user which in turn most likely results from running `mailman import21` as root. Bottom line - check that all sub-directories and files in Mailman's var/templates/ directory are searchable and readable by the Mailman user. -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to krinetzki(a)itc.rwth-aachen.de

6 months, 1 week

Re: Held messages not delivered after approval

by Mark Sapiro

On 8/5/25 02:06, Krinetzki, Stephan wrote: > Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost on port 25 > > The last error is a very often in the mailman.log: That's a misleading message. It's been improved by https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the underlying issue is inability to access a header or footer template when decorating the message. This in turn is most likely caused by some template(s) in Mailman's var/templates/ directory being owned by `root` or some other non-mailman user and not readable by the Mailman user which in turn most likely results from running `mailman import21` as root. Bottom line - check that all sub-directories and files in Mailman's var/templates/ directory are searchable and readable by the Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

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

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

3 years, 2 months

Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Odhiambo Washington

On Fri, May 24, 2024 at 2:34 PM marcus--- via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hello, > > i already send this question to the plesk-forum but it seems that nobody > there can help me :-( > > After updating from Debian 10 to 11 to 12, I now have mailman3 running on > my server > I then converted all lists from Mailman2 to Mailman3 following the > instructions from mailman. > I can access it via the web interface, manage everything etc. > When I register on the web interface, I also receive the corresponding > mails from Mailman (forgotten password...) > Mails are also arriving, at least mails that are not allowed go into the > mails to be approved. > > The problem, however, is that it does not send out any mails, nor do they > appear in the archive. > > When I look in the Mailman-Log I find: > > May 16 01:44:55 2024 (6833) Cannot connect to SMTP server localhost on > port 25 > May 16 01:48:15 2024 (61252) error opening connection to nntp_host: > localhost > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Why is it talking about NNTP_HOST here? > [Errno 111] Connection refused > May 16 01:48:15 2024 (61252) NNTP error for list > vereinsmitglieder(a)ludothek.de: > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Also here! > [Errno 111] Connection refused > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is okay anyway, since we do not need nntp anyways. The configuration of Mailman.cfg looks like this: > > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > smtp_host: localhost > smtp_port: 25 > smtp_user: > smtp_pass: > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > So I assume you followed some other guide to install your MM3. You did not follow https://docs.mailman3.org/en/latest/install/virtualenv.html. Is that right? If you used the above (recommended) method of installation, you'd end up with mailman.cfg whose contents of the [mta] section would look different from what you've shown above. Also, you'd have ended up with the following directory and files: ``` odhiambo@lists:/opt/mailman/mm/var/data$ pwd /opt/mailman/mm/var/data odhiambo@lists:/opt/mailman/mm/var/data$ ls -al total 100 drwxr-xr-x 2 mailman mailman 4096 Mar 16 00:11 . drwxr-xr-x 12 mailman mailman 4096 Mar 15 04:50 .. -rw-rw---- 1 mailman mailman 359 Mar 16 00:11 postfix_domains -rw-r----- 1 mailman mailman 12288 Mar 16 00:11 postfix_domains.db -rw-rw---- 1 mailman mailman 26481 Mar 16 00:11 postfix_lmtp -rw-r----- 1 mailman mailman 49152 Mar 16 00:11 postfix_lmtp.db odhiambo@lists:/opt/mailman/mm/var/data$ ``` Also, you'd have ended with the following (or equivalent) in your /etc/postfix/main.cf: ``` transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains ``` For now, you should find where these files are and point your Postfix to them and that may solve your problem. I am no Postfix Admin and I don't know nada about Plesk. > In Mailman manuals I find hints that the transport routes have to be added > to the Postfix-config. Doesn't Debian/Plesk do this automatically? > There is only one DEFINITIVE manual for Mailman3 and it is https://docs.mailman3.org/en/latest/install/virtualenv.html. It doesn't mention Plesk or cPanel :-) > Does anyone else have an idea what I need to change to get my mails out? > Yes. As I have detailed above, sin permissions issues. I did the conversion from mailman2 to mailman3 with root because it didn't > work with "sudo -u list "m, but the files stored in the file system all > belong to list, so that shouldn't be the problem. > Looks like a problem with the HOWTO that you followed. Here we're happier to help when you follow OUR HOWTO <https://docs.mailman3.org/en/latest/install/virtualenv.html> above. We're not quite enthusiastic when you follow other HOWTOs out there. Good luck! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 8 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

4 years, 4 months

Re: footer template priority

by Mark Sapiro

On 6/19/25 14:30, Sam Darwin via Mailman-users wrote: > Thanks. That fixed it. > > Comments: > 1. In the docs, the instructions say "POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000'. As a reader, you are thinking, I'm running both hyperkitty and postorius. Hyperkitty is at /archives/ and postorius is at /mailman3/ . What about the path '/mailman3/ for postorius? > The doc could mention the path even if it's to explain why it's not needed. (The reason perhaps it's not needed is root will redirect to '/mailman3/'.) I'm guessing you are looking at https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail… Although the name of the setting includes Postorius, the definition there says "Base URL where Django/Mailman-web would be listening for requests." I.e., the base URL for accessing Django, not Postorius. > 2. This all seems very self-referential. The setting goes into settings.py which is the website for postorius itself. It is accessing itself. > Given that's the case do you really need to tell Django about it's own URL? Doesn't it know it's own URL already? Could Django just contact itself without being configured? It and in this case Postorius know the /mailman3/... part, but they don't necessarily know the appropriate base url for accessing the Django WSGI. > 3. Logging... when it can't find the templates, does it log an error anywhere? Mailman's outgoing runner logs an error to the mailman.error log, usually written to mailman.log. The not at all descriptive log message says "Cannot connect to SMTP server <configured smtp_host> on port <configured smtp_port>", but it only logs it the first time and not again until there is a successful delivery. This issue is https://gitlab.com/mailman/mailman/-/issues/514 which I am in the process of fixing. > 4. The server had been up for a year. After I rebooted, the problem vanished, even after removing the new setting. So either it's caching the setting in Redis, or else the problem is really gone. Very strange. See https://gitlab.com/mailman/mailman/-/issues/514#note_101644301 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

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

5 years, 2 months

Re: Importing config and archives only partially succeeded?

by Eric Broens

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 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). 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. 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 Best Regards,Eric On Sunday, December 13, 2020, 06:29:19 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 7:40 PM, Eric Broens via Mailman-users wrote: > There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail. I'm not sure what is causing the repeated access of /archives/api/mailman/urls... This call comes from Mailman core in order to request the URL at which a message will be archived. It is called from mailman/src/mailman/handlers/rfc_2369.py when adding the Archived-At: header and from mailman/src/mailman/handlers/decorate.py in order to get the hyperkitty_url replacement value. I don't understand why it would be called repeatedly for the same message. Are there any clues in mailman.log. > I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)." What if you look at "threads by month" and select the current month? > Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list. I think the basic issue is when you see no messages, HyperKitty, for whatever reason thinks there are no current messages. I'm not sure, but if there are recent posts, are they all in threads started more than 30 days ago? As far as all the participants/discussions counts being zero, I think one of the periodic jobs will fix that (possibly the daily recent_threads_cache job) -- 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/

5 years, 2 months

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