I am unable to duplicate this problem. I changed a list's password twice with bin/change_pw -l mylist -p mynewpassword while a message was waiting approval. and when I finally logged in to the admindb interface, the message was still there. Perhaps the original poster canceled the post before you got to it. If the message is no longer in the admindb interface, it might possibly still be in the data/heldmsg-mylist-nn.pck (or .txt) file, but that's really unlikely. If the file is there, there is a script at http://www.msapiro.net/scripts/hold_again that can be used to reprocess it. ** Changed in: mailman Status: New => Invalid ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- List password reset while pending messages, they are deleted! https://bugs.launchpad.net/bugs/515305 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

Yes, that is a normal 'empty' pending.pck. And, I didn't expect there to be any heldmsg* files. The fact that the pending.pck is empty is further evidence that the confirmation cookie that was sent to the user along with the email that her post was held was actually used to cancel the post. I.e., the user sends a post which is held for some reason. If the list's respond_to_post_requests setting is Yes (the default), an email is sent to the poster which contains a link which can be followed to cancel the post. Replying to the email will also cancel the post. This requires no 'awareness' on the part of the user. Look in Mailman's vette log and you should find an entry for the holding of the post and another entry for it's cancellation indicating what was done and why. Also, I'm certain there's no way that bin/change_pw would cause a post to be discarded. -- List password reset while pending messages, they are deleted! https://bugs.launchpad.net/bugs/515305 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.