AFAIK, as long as the user isn't still connected, and the size of the $tempdrop/.user.pop file is 0 bytes, you can simply delete the .pop and .lock files. Qpopper might generate an error, but the poplock is cleared by force. If the user is still connected, or connects while you are 'fixing' it, you can loose all of the spool file this way though. :-(

Ken


[EMAIL PROTECTED] wrote:
Hello,

I have checked the FAQ for this answer but could not find it :(

Is there a quick way to unlock a users mailbox after a failed pickup of
emails? Currently, we have to tell our users if this happens they must
wait approximately 20 mins for the mailbox to unlock itself and some are
finding this unacceptable.


We are running qpopper 4.05 on redhat9. It is also run in server mode.

Thanks

Nick


Reply via email to