[Mailman-Users] How to kill zombie pending moderator requests?

[Bill Cole]

I recently migrated a set of Mailman lists from a standard 2.1.18 
installation (on ancient RedHat) to a cPanel host (CentOS 7) running 
Mailman 2.1.27. One glitch in that migration involves a pending 
moderation issue, which ultimately does not need to be dealt with 
because it was just spam to the list address from a non-member. Due to 
some flaw in my migration process (probably related to cPanel's list 
name mangling) the daily pending request reminder script is sending the 
moderator a reminder of the issue, however the issue is not visible in 
the web UI.

The pending.pck file for the list has this unilluminating content:

# ../../bin/dumpdb pending.pck
[----- start pickle file -----]
<----- start object 1 ----->
{   'evictions': {   'fe643c3a29afd79686e7ee0578f83b2fa2ae1eba': 
1550223270.461477},
     'fe643c3a29afd79686e7ee0578f83b2fa2ae1eba': ('H', 2440),
     'version': 2}
[----- end pickle file -----]


Python is not a language I use much so I'm not sure what the daily 
'checkdbs' script is seeing that makes it think there's a pending issue 
or what exactly the contents of that pending.pck means, although I 
expect it is relevant. The other 3 lists that were migrated in the same 
way at the same time which did not have pending issues have similar 
pending.pck contents but DO NOT generate the phantom notifications.

My first impulse is to just clobber the pending.pck file, but I am not 
sure if that is safe. Advice would be greatly appreciated.


-- 
Bill Cole
bill at scconsult.com or billcole at apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole


-- 
Bill Cole
bill at scconsult.com or billcole at apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole