On Sun, 2018-10-14 at 16:28 -0700, Mark Sapiro wrote:
> Fix it by removing the corrupt lists/LISTNAME/pending.pck file.
Can I assume a proper replacement will be auto-generated going forward?
> If you are interested in trying to determine what happened, you can save
> that file. If bin/dumpdb wil
On 10/14/2018 09:50 AM, Lindsay Haisley wrote:
>
> And yes, I can trigger the recursion with the bash snippet you posted,
> and it is indeed in the list which had 49 disablements (and manual re-
> enablements) after our blacklisting by Microsoft last weekend.
>
> The question now is how to fix it
On 10/14/2018 09:41 AM, Lindsay Haisley wrote:
> On Fri, 2018-10-12 at 11:31 -0700, Mark Sapiro wrote:
>> cd /usr/lib64/mailman/
>> for list in `bin/list_lists --bare`; do
>> if [ -f lists/$list/pending.pck ]; then
>> echo $list
>> bin/dumpdb lists/$list/pending.pck|grep evictio
On Fri, 2018-10-12 at 11:31 -0700, Mark Sapiro wrote:
> You are looking for a list that doesn't print the 'evictions' line or
> that exhibits the loop.
And yes, I can trigger the recursion with the bash snippet you posted,
and it is indeed in the list which had 49 disablements (and manual re-
enab
On Fri, 2018-10-12 at 11:31 -0700, Mark Sapiro wrote:
> cd /usr/lib64/mailman/
> for list in `bin/list_lists --bare`; do
> if [ -f lists/$list/pending.pck ]; then
> echo $list
> bin/dumpdb lists/$list/pending.pck|grep evictions
> fi
> done
Thanks for the code, Mark. I shoul
Here's what happened. Among the lists my server hosts is one for a
local folk music mailing list. It's a large, "general announcements"
list, on a short fuse for bounces (bounce_score_threshold = 1.0). Last
weekend I noticed 49 disablement notices in my inbox, all of them from
Microsoft domain name