At 9:04 AM -0500 12/21/00, Brian Curtis wrote:
> A response to the last thread "need help" reminded me of a question I've
> been meaning to ask...
>
> Is there a quick remedy to fixing a users mailbox when their connection is
> terminated abnormally resulting in a lingering .username.pop lockfile?
>
> Right now I just tell them to wait a short while, and the mailbox will
> unlock itself. However, I'm waiting for the user that says "I need my mail
> immediately!".
As soon as Qpopper is notified that the connection is broken it will
clean up and terminate. If Qpopper doesn't get an EOF error on read
or a SIGPIPE signal, it will timeout and then cleanup and terminate.
You can always adjust the timeout value if you want.
>
> I've tried copying the .pop file back to the normal mail spool file and
> deleting the lockfile, but that produced some strange results.
Was the popper process still active for the user? If so, you you
could create quite a mess. And if mail was also being delivered for
the user, it would be even worse.
