On 08/25/2017 06:29 AM, Julian H. Stacey wrote:
Hi mailman-users@python.org I hope I may have solved some postings being shunted on a few of my lists, necessitating occasional cd /usr/local/mailman; unshunt qfiles/shunt
I discovered 3 lists had missing '\n', shown with cd /usr/local/mailman/lists; config_list -o - ListName bounce_matching_headers = """# Lines that *start* with a '#' are comments.
What is the rest of this up to the terminating """?
Fixed with cd /usr/local/mailman/lists ; config_list -o ~/tmp/ListName ListName vi ~/tmp/ListName ; config_list -i ~/tmp/ListName ListName & I hope the shunting will stop.
I did autopsy snapshots of /usr/local/mailman before & after last unshunt, if anyone feels like telling me what to look for.
What is the traceback from the 'shunt' message in Mailman's error log?
Unfortunately the corrupt bounce_matching_headers lines in configuration were undetected by these automatic checks cd /usr/local/etc/rc.d; ./mailman stop ; ./mailman start cd /usr/local/mailman/lists ; ../bin/check_db -a cd /usr/local/mailman/lists ; ../bin/check_perms
If bounce_matching_headers contains an invalid line, there should be entries in Mailman's 'config' log like
'bad bounce_matching_header line: LISTNAME LINE
or
bad regexp in bounce_matching_header line: LISTNAME REGEXP (cause: ERROR)
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan