On 10/1/20 11:18 AM, gordon@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@dickens.com> Oct 01 11:51:07 2020 (7885) HyperKitty archived message <f92eeaad-245c-124b-dd09-b31a6b3c5686@dickens.com> to https://georgiajets.org /mailman3/hyperkitty/list/members@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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan