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
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
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
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
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
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
