Thanks, Thomas.  That's what I need to know.

Chris

I'm using Mercury/32 4.72 under Windows XP with 2 local XP clients (Thunderbird, multiple accounts) and a smartphone accessing mail using IMAP (MercuryI) . None of the clients seem to be able to expunge (ie, purge deleted emails) if any of the other clients are logged in. I have read of other people finding the same problem, but perhaps only with Thunderbird - I don't see anything in the RFC to say that expunge won't work if other clients are connected.

Does anyone know if this is normal IMAP behaviour or a Thunderbird bug?

I also had Mercury crash yesterday. Both Thunderbird clients were closed within a few seconds - the core process and MercuryS logs show nothing unusual, but MercuryI log cuts off after reporting log-out of one account on the second client to be closed - and Hierarch.pm for that account was corrupted. I've restored the corrupted file from backup and all is well, this post is just for info in case anyone has a similar crash. I'm guessing there may have been some issue with the two clients shutting down together and getting out of sync?

Chris

That is normal IMAP behaviour. Expunge only works when there is one client connected.

I have several IMAP accountd with regular multiple access and have no problems with crashes. (not since 4.01 anyway)

Thanks, dilberts. You would'nt happen to have a reference to show that IMAP is supposed to do that, would you? I'm trying to get the author of the phone software I use to accept that there's a bug, because it shows a message count which includes messages flagged for deletion - but he thinks I should be able to expunge them so it shouldn't be an issue.

Thanks, dilberts. You would'nt happen to have a reference to show that

IMAP is supposed to do that, would you? I'm trying to get the author of

the phone software I use to accept that there's a bug, because it shows

a message count which includes messages flagged for deletion - but he

thinks I should be able to expunge them so it shouldn't be an issue.

Concurrent access deletion is an IMAP4 server option and this is not implemented in a lot of IMAP4 servers; MercuryI for one does not support this option. You can find out which options are supported by a server with the CAPABILITY command.  Here's one from smtp.bayarea.net

* CAPABILITY IMAP4REV1 LITERAL+ IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT
 SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND SASL-IR LOGIN-REFERRALS AUTH=LOGIN
a1 OK CAPABILITY completed

and one from my local mercury

a1 capability
* CAPABILITY IMAP4rev1 AUTH=PLAIN X-MERCURY-1
a1 OK CAPABILITY complete.