I restarted Mercury thinking that would kill it but it reconnected within minutes.  I then noticed connection activity every 5 minutes so it was definitely auto checking.  I ended up creating a temporary user and copying the mailbox contents of the locked mailbox to the temp user mailbox.  I then created a forward file to forward all mail from the locked mailbox to the temp one.  My user then spent the day working in Pegasus as the temp user.  I had him make a new folder to place copies to self in so that we could easily copy those to his actual mailbox once the lock was released.  After doing all that it dawned on me that I could probably stopped the IMAP client from connecting by changing the password then restart Mercury.

I have a user who IMAPed in from his iPAD from home at 7:29 AM.  It's now 9:31 AM and the mailboxm.lck file is still in place.  MercuryI shows a current connection for that user but also shows the 7:29 AM connection as closed.  This user needs access to the mailbox from our LAN install of Pegasus Mail.  Is there a way for MercuryI to kill his IMAP connection?

FWIW, the IMAP idle timeout is set to 30 minutes.

--
Brian Fluet

So the IMAP client is presumably just auto-checking for new mail at some preset interval? There is probably no way to get MercuryI to close the connection, other than an IMAP request from the client, but if you are sure the IMAP session is in fact idle it might work to simply delete the lock file. When Pegasus Mail connects it will create a lock file of its own and prevent further IMAP access. 

Deleting lock files can definitely cause problems if the existing session isn't passive, so it should be done with great care.

/Rolf