On 12/24/2012 12:31 PM, Con Wieland wrote: > Thanks Mark, that did the trick, ArchRunner started right up without any > errors. Fingers crossed the only thing left are the 542 messages in > qfiles/bad. They mostly seem to just be message headers that were bounces or > the body was omitted.... Can they safely be deleted?
In your case, the messages in the 'bad' queue are almost certainly all messages that had no content left after content filtering on lists for which filter_action = Preserve. Yes, you can just remove them. Further, since no one is apparently pro-actively looking for these, I suggest setting OWNERS_CAN_PRESERVE_FILTERED_MESSAGES = No in mm_cfg.py so that these messages will not be moved to the 'bad' queue in the future. You could also run something like: #!/bin/bash cd /path/to/mailman for list in `mmp/bin/list_lists --bare`; do echo $list mmp/bin/config_list -o - $list | grep "filter_action = 3" done to find those lists with filter_action = Preserve and then you can change them to one of the other settings. As far as ArchRunner is concerned, if your logs go back far enough, you will find messages in the 'qrunner' log about ArchRunner dieing and restarting until its restart limit was reached and possibly corresponding 'error' log messages. This may have been due to corrupt files after the power outage hard crash, or it may be something that should be investigated. -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
