As you provided few details I quoted what the Wiki says about locked mailboxes in general. The part about IMAP access says:

"multiple IMAP client sessions against the same mailbox through MercuryI are allowed" 

If you have a situation where there is a problem with this, please post a MercuryI session log (or relevant parts of one).

/Rolf 

When I leave my email open at home and go to work, I get the following response when I try to access my inbox.

The current operation on inbox did not succeed. The mail server for account X responded: Folder in use by other connections.

Now I always thought one advantage of imap was that it would allow me to do this sort of thing. Is that not the case, or have I not configured things correctly?

This is what is says about locked mailboxes on the Wiki:

If you use Mercury/32 as your back-end mail system and have the MercuryI IMAP Server module enabled, then Mercury/32 will create a MAILBOXM.LCK lock file in your mailbox directory whenever you access your mailbox via an IMAP client. If you then also try to run Pegasus Mail against that mailbox, Pegasus Mail will also bring up the "Mailbox is locked" warning dialog. Or if you have Pegasus Mail currently running and attempt to connect to your mailbox via an IMAP client through MercuryI, then the IMAP connection will be denied. You can only access a mailbox via one Pegasus Mail session or via Mercury/32's IMAP module (though multiple IMAP client sessions against the same mailbox through MercuryI are allowed).

/Rolf 

I don’t

understand your reply. You imply that the MAILBOXM.LCK file prevents multiple

client access, but later state that multiple IMAP client sessions against the

same mailbox through MercuryI are allowed. In my situation, the IMAP client is,

in all cases, Thunderbird. This is the client that is showing the message I

posted. Should I be able to do multiple client access?<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />