[Mailman-Users] Bad Confirmation String to cancel Message that was too large.

[Bryan Carbonnell]

On 3 April 2017 at 12:01, Mark Sapiro <mark at msapiro.net> wrote:
> On 04/03/2017 11:36 AM, Bryan Carbonnell wrote:

>> I don't see the confirmation string in the list's db even though I
>> still see the email in held moderation queue.
>
>
> Did you give the '-m' option to the script. Without it, you won't see
> held messages.

Yes. (Down to 5 now)

$ ./list_pending -m -v dba-ot

cookie: e218b075f231a8aceeeae3bc9bb301b4328b0d79
    type: H
    data: 5640
    expiration: Thu Apr  6 06:56:58 2017
cookie: 628801c2354da0f1472f6a20a7fbe9e32f8dff48
    type: H
    data: 5637
    expiration: Wed Apr  5 14:01:54 2017
cookie: b63c013faa69b2d37d3d1c53580294a8fe3ed669
    type: H
    data: 5635
    expiration: Mon Apr  3 23:46:25 2017
cookie: 20ea7168e15b739d8b56b8a68057c86f6fdf11ff
    type: H
    data: 5636
    expiration: Wed Apr  5 06:23:30 2017
cookie: 10f908cac1d37bc935d215bcb51f74421b5cb236
    type: H
    data: 5638
    expiration: Wed Apr  5 17:43:59 2017

>> It's actually weird. There are 6 messages that are held in the db, but
>> only 2 in the moderation queue
>
> Perhaps the admindb interface is not for the current mailman installation?

AFAIK it's the only Mailman installation on the server. I've been the
only one who has done anything on this server in a long time (but that
doesn't mean I haven't messed something up :).

> If you run the list_requests script from
> <https://www.msapiro.net/scripts/list_requests> with the -l LISTNAME and
> -v options, does it correlate with the admindb list?

Yes. Both only have 2 messages.

$ ./list_requests -l dba-ot

2 dba-OT moderator request(s) waiting

Pending posts:
From: eptept at gmail.com on Mon Apr  3 04:42:48 2017
Subject: Re: [dba-OT] Turmoil on the Home Front
Cause: Message body is too big: 27563 bytes with a limit of 20 KB


From: ssharkins at gmail.com on Mon Apr  3 06:56:58 201v
Subject: Re: [dba-OT] Turmoil on the Home Front (Redux)
Cause: Message body is too big: 20749 bytes with a limit of 20 K

$ ./list_requests -v

2 dba-OT moderator request(s) waiting

Pending posts:
From: eptept at gmail.com on Mon Apr  3 04:42:48 2017
Subject: Re: [dba-OT] Turmoil on the Home Front
Cause: Message body is too big: 27563 bytes with a limit of 20 KB
        5639


From: ssharkins at gmail.com on Mon Apr  3 06:56:58 2017
Subject: Re: [dba-OT] Turmoil on the Home Front (Redux)
Cause: Message body is too big: 20749 bytes with a limit of 20 KB
        5640

> Do the IDs in that output correlate with those in the list_pending -m -v
> output?

Yes and no. One, 5640, is there. One, 5639, isn't and 5639 is the one
that had the problem with the confirmation string.

> Also, do the data/heldmsg-LISTNAME-ID.pck files correlate with the admindb.

Yes. There are only 2 heldmsg-LISTNAME-ID.pck files The IDs correspond
to the IDs after running ./list_request -v

$ ls ../data/heldmsg-dba-ot-*

../data/heldmsg-dba-ot-5639.pck  ../data/heldmsg-dba-ot-5640.pck

> If there are discrepancies, are there any exceptions logged in Mailman's
> error log?

Nothing in the error log except a couple of invalid listname errors
and an invalid arcive file request

>> Is there anything else I can check, or should I write this one off as
>> an anomoly?
>
>
> If the message is in the admindb interface, it should be in the
> pending.pck, at least if it's recent. Older messages could have had
> their pending confirmations removed after PENDING_REQUEST_LIFE (default
> 3 days).

Thanks for trying to help me out Mark. I do appreciate it.

-- 
Bryan Carbonnell - carbonnb at gmail.com
Life's journey is not to arrive at the grave safely in a
well-preserved body, but rather to skid in sideways, totally worn out,
shouting "What a great ride!"