On 1/30/22 08:22, Jacob Sievert via Mailman-users wrote:
Yes they should. This is https://gitlab.com/mailman/mailman/-/issues/257 fixed in Mailman core 3.3.5. Also in Mailman 3.3.5 is a new Task runner that runs periodic tasks, one of which is to remove orphaned pendings. Hmm our running system right now already was on 3.3.5 since a few days after release. But maybe all of those were still from before.
Task runner cleans some things, but not all.
...>> # Prior to Mailman 3.3.5, some tokens for user confirmations were
pended with # too long a lifetime. This script removes those pendings based on when they # were pended and the configured pending_request_life rather than their # expiration. With the script we went down to around 16k entries in pendedkeyvalue removed were the following: expunged 6932 orphaned pended held messages
When a message is held, two tokens are pended; one for the moderator and one for the user. Notification to the user doesn't currently include the user's token or instructions on removing the held post; that needs to be done, but the token is pended anyway. Prior to 3.3.5, when a held message was handled, the moderator's token was removed, but not the user's. That's what these are.
expunged 254 expired held messages expunged 21 expired (un)subscription confirmations
Prior to 3.3.5, some things were pended with excessively long lifetimes. The script expires these based on 3 days for user confirmations and 180 days for moderator actions. The above were older than that.
This shows that there were a lot of things in an unfinished state to my understanding in our system. For a time this system was running with less RAM than it should have had. So maybe some of the problems came from there.
These were all problems with pre 3.3.5 Mailman, not specific to your system.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan