Hi
I am using qpopper 3.0.2 in non-server mode and have read the following
faq:
If my users cancel during a long download, the .lock file and the
.user.pop file, along with the Qpopper process, hang around.
As the size of the spool file increases (more and larger messages
left on the server), the time required to start and stop the POP
session will go up, especially if Server Mode is not used. If you
check the spool directory just after a session ends, you may see
the lock file and the temporary spool still there, and the Qpopper
process still active. Do not kill the process, as it is updating
the spool. You should make sure to run the latest version of
Qpopper. You may want to review the options which affect
performance.
However on rare occasions (eg once per week) a qpopper process will hang
around indefinitely. I have seen such processes and the corresponding
.user.pop file hang around overnight. What is the solution? Will
upgrading to the latest version solve this particular problem?
At the moment I ignore the advice about not killing the process, append
any new mail from "user" to the .user.pop file manually, rename it to
"user", then kill the process.
Regards
Jim Holland
System Administrator
MANGO - Zimbabwe's non-profit e-mail service
