Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-15 Thread Lindsay Haisley
On Mon, 2018-10-15 at 21:43 -0700, Mark Sapiro wrote: > On 10/15/18 9:23 PM, Lindsay Haisley wrote: > > On Mon, 2018-10-15 at 21:09 -0700, Mark Sapiro wrote: > > > There should be "delivery disabled" entries in Mailman's bounce log. > > > > Nada, even though I got email notifications of the disabl

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-15 Thread Mark Sapiro
On 10/15/18 9:23 PM, Lindsay Haisley wrote: > On Mon, 2018-10-15 at 21:09 -0700, Mark Sapiro wrote: >> There should be "delivery disabled" entries in Mailman's bounce log. > > Nada, even though I got email notifications of the disablement. There must be entries of the form Oct 12 03:20:10 2018

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-15 Thread Lindsay Haisley
On Mon, 2018-10-15 at 21:09 -0700, Mark Sapiro wrote: > There should be "delivery disabled" entries in Mailman's bounce log. Nada, even though I got email notifications of the disablement. > It's as if something was > updating the list and the pending database and had a single file > descriptor f

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-15 Thread Mark Sapiro
On 10/15/18 8:14 PM, Lindsay Haisley wrote: > > Unfortunately, I don't have the disablement notification emails (with > timestamps) which I received from MM which alerted me to the Microsoft > blocking issue. I've combed through the mail log a bit, but don't see > it there. There should be "deli

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-15 Thread Lindsay Haisley
On Mon, 2018-10-15 at 18:16 -0700, Mark Sapiro wrote: > Granted if all that was done was that bounce processing disabled a bunch > of deliveries (and pended a re-enable token for each one), the file > shouldn't have been corrupted. Re-enabling delivery via the member > management UI doesn't touch p

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-15 Thread Mark Sapiro
On 10/14/18 7:33 PM, Lindsay Haisley wrote: > 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? Yes, the next time something is pended, the file will

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-14 Thread Lindsay Haisley
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

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-14 Thread Mark Sapiro
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

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-14 Thread Mark Sapiro
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

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-14 Thread Lindsay Haisley
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

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-14 Thread Lindsay Haisley
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

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-14 Thread Lindsay Haisley
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

Re: [Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-12 Thread Mark Sapiro
On 10/12/2018 08:20 AM, Lindsay Haisley wrote: > I'm running Mailman 2.1.18-1 > I'm running cron job daily with this command: > > /usr/bin/python -S /usr/lib64/mailman/cron/disabled > > I've started getting the following messages indicating a code problem > with this script, to wit: > > Tracebac

[Mailman-Users] Recursion problem with "disabled" cron job.

2018-10-12 Thread Lindsay Haisley
I'm running Mailman 2.1.18-1 I'm running cron job daily with this command: /usr/bin/python -S /usr/lib64/mailman/cron/disabled I've started getting the following messages indicating a code problem with this script, to wit: Traceback (most recent call last):   File "/usr/lib64/mailman/cron/disabl