Subject: RE: mailbox locked by other session

From: "Sobocinski, Todd" <[email-masked]>
Date: Sat, 10 Aug 2002 13:29:04 -0400

This has happened to me with imap when the server-side process didn't
die, and held onto the mailbox lock.  I bet if you go onto the mail
server, you will find your pop3d process still running.  New mail never
got delivered for me, because the server-side process still had the
lock.  But maybe with the way you lock, new mail was enough to knock
your pop3d process out of its reverie and make it quit.  Killing the
offending pop3d process should fix it though.  (Remove any ".lock" files
too, if you're using that style of locking.)

Not sure what the ultimate cause of that was though.  The problem went
away in our last server upgrade, and I don't recall if we ever figured
out why the server processes were hanging.

Todd

-----Original Message-----
From: Bruce Cohen [mailto:[email-masked]] 
Sent: Saturday, August 10, 2002 3:03 AM
To: Pine Discussion Forum
Subject: mailbox locked by other session

All of a sudden things are happening that have never happened before
(pine
4.33/pop3): If something happens during the pine session [(1) can't
login, waiting for response from server - manually disconnect session;
(2) while logged in Mailbox closed due to access error] then on the next
attempt to run pine I can't login: "Mailbox closed by a pop3 session".
There is nothing I can do on the unix shell (no pine session still
running I could kill). It's happened twice so far, the first time I
could log in after 5 minutes (new mail had been delivered in the
meantime - maybe that was the
problem) - right now I have waited 10 minutes and still can't log in.

If anything like this has happened in the past, I could always get right
back into pine by simply quitting and starting over. The only time I
haven't been able to do that is if there is still a pine session running
as a ghost which I could see with the command "ps" and then kill and log
right back on.

I think something has happened on the pop3 side, but what?

(Even if I telnet directly to the popper the same thing happens: can't
get in, "mailbox locked by other server")

Anyone have any ideas?

Thanks

Bruce Cohen

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Bruce Cohen <[email-masked]>
Date: Sat, 10 Aug 2002 19:38:17 +0200 (MET DST)

Problem is I can't kill anything - and I can't logon to the popper
either - tried telnetting there - same story. At least I can't by
telnetting to port 110 and logging in with USER and PASS: the lock
applies there also. Is there a way to just telnet there and see what
processes are running? I suppose I could kill it if I could find it
since I am the owner. My knowledge of the popper commands is very
limited, however, I believe I only know USER, PASS, LIST, DELE (or at
least that's all I remember). Is there any documentation to be found on
this?

Sending mail to myself does seem to help, albeit not immediately - at
least at some point within the next half hour I can get back on again - so
at some point it manages to get unlocked.

 Bruce