Some entries in the log files can be very scary, while in actual sense they are harmless. Such inconsequential, but scary entiess can mess up the well-being of a SysAdmin. I humbly request for the logs related to posts by non-members to a MM3 list to be improved a little bit :-) Here is the example in mailman.log:
<cut> Jan 31 10:03:54 2023 (92481) DISCARD: < 2a1c588a6ccd47abbf57ee5fc61c9946@phellineconsultancy.co.ke>; ['The message is not from a list member'] [31/Jan/2023:10:04:48 +0300] "GET /3.1/users/1bad08f703fe4bc0a829f4bdce10fc8f HTTP/1.1" 200 253 "-" "GNU Mailman REST client v3.3.5" [31/Jan/2023:10:04:48 +0300] "GET /3.1/users/1bad08f703fe4bc0a829f4bdce10fc8f/addresses HTTP/1.1" 200 473 "-" "GNU Mailman REST client v3.3.5" Jan 31 10:18:09 2023 (92343) deque: do_confirm_verify Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/app/subscriptions.py", line 476, in _step_send_confirmation raise StopIteration StopIteration </cut>
Is there a possibility to change the logging engine to just *fold* the last 7 lines into "The message is not from a list member. It was discarded", or something close?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)