On 3/10/23 05:07, Christian via Mailman-users wrote:
There are no such messages as you describe.
After turning on debugging I got this from a test message sent to the new list:
Mar 10 04:39:51 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 04:39:51 2023 (1005) Peer: ('127.0.0.1', 51982) Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) handling connection Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'MAIL FROM:<christian@naturalintelligence.us> SIZE=3499' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) sender: christian@naturalintelligence.us Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'RCPT TO:<redlatinleg@lists.ccalternatives.org>' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) recip: redlatinleg@lists.ccalternatives.org Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'DATA' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'QUIT' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) connection lost Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) Connection lost during _handle_client()
Again, that's only the post being delivered to Mailman. What comes after that in the log?
And have you checked if Mailman's out runner is running? Note that if it died for some reason and wasn't restarted or used up its restarts, restarting Mailman core won't start it. You need to stop Mailman core and then start it.
Are there files in mailman's var/queue/out/ or var/queue/shunt/ directories?
You say that only the new list and one other have this issue, but I wonder if the issue is not with specific lists, but rather with posts after a certain time.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan