On Sat, Apr 1, 2023 at 7:55 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users@mailman3.org> wrote:
This morning I upgraded the mailman3 installation of the less traffic server I have: a bunch of lists, with very slow traffic.
(see pip lists at the end)
I sent test mails to a pair of lists, but none were distributed or archived. postorius seemed working well. First I thought it was some I did wrong in the upgrade procedure, but then I realized the lmtp runner was not running.
I followed old messages about similar problem (many of them in this same mailman-users list), but I cannot see what is wrong. There is no error logged in mailman.log. the mailman.cfg of the lmtp is the default (and was working at least a pair of weeks ago)
*-*-*-*-*-*-*-*-* from mailman.cfg
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix
*-*-*-*-*-*-*-*-*
There is no one listening in port 8024. I tried changing the port (to 9024), with the same results.
postfix seems working well. I's just there is nothing listening on port 8024 because lmtp runner is not running :)
(from maillog):
connect to 127.0.0.1[127.0.0.1]:8024: Connection refused
(another simple test)
root@www:/usr/local/mailman3 # telnet localhost 8024 Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused
I'm running out of ideas. Any clue to somewhere to dig in?
*-*-*-*-*-*-*-*-*-*-* runners started
Apr 01 17:24:40 2023 (4681) out runner started. Apr 01 17:24:40 2023 (4680) virgin runner started. Apr 01 17:24:41 2023 (4679) command runner started. Apr 01 17:24:42 2023 (4688) retry runner started. Apr 01 17:24:43 2023 (4686) in runner started. Apr 01 17:24:44 2023 (4683) digest runner started. Apr 01 17:24:44 2023 (4684) nntp runner started. Apr 01 17:24:45 2023 (4682) archive runner started. Apr 01 17:24:46 2023 (4685) bounces runner started. Apr 01 17:24:47 2023 (4687) task runner started. Apr 01 17:24:47 2023 (4687) Task runner evicted 0 expired pendings Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned workflows Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned requests Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned messages Apr 01 17:24:47 2023 (4687) Task runner evicted expired cache entries Apr 01 17:24:48 2023 (4678) pipeline runner started. Apr 01 18:24:48 2023 (4687) Task runner evicted 0 expired pendings Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned workflows Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned requests Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned messages Apr 01 18:24:48 2023 (4687) Task runner evicted expired cache entries
*-*-*-*-*-*-*-*-*-* pip lists with versions installed
root@www:/usr/local/mailman3 # pip list | grep mailman django-mailman3 1.3.9 mailman 3.3.8 mailman-hyperkitty 1.2.1 mailmanclient 3.3.5
root@www:/usr/local/mailman3 # pip list | grep django django-allauth 0.51.0 django-appconf 1.0.5 django-compressor 4.0 django-extensions 3.2.0 django-gravatar2 1.4.4 django-haystack 3.2.1 django-mailman3 1.3.9 django-picklefield 3.1 django-q 1.3.9 djangorestframework 3.13.1
root@www:/usr/local/mailman3 # pip list | grep postorius postorius 1.3.8
Bumping either mailman|lmtp loglevel to DEBUG might help find out.
[logging.lmtp] level: debug
And I think you can debug everything with (untested): [logging.here] level: debug
And restart mailman.
Maybe??
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)