No, we are not at the EXPUNGE stage yet.

Before an e-mail can be expunged, it has to be flagged as DELETED first. For most imap clients this means the mail is no longer displayed in the mailfolder (or it appears as "striked through"). This flag disappears, i.e. the e-mail appears again in my inbox, as if I had only read it, not deleted it.

Initial testing suggests, the Marking of the e-mail is lost, if the client connection is lost without EXPUNGE. This would be really bad, since up to Mercury 4.72, disconnecting your imap client was the only way to assure such flags where saved to disk.

I had to switch back to 4.72 on our user servers.

Greetings

Markus Borst

It seems that the new Mercury 4.73 is very erratic when deleting mails: Sometimes they retain the "deleted" flag, sometimes they don't. If a mail in the inbox is deleted via imap (14:09:32.468: >> 14 uid store 25 +FLAGS (\Deleted \Seen)<cr><lf>), sometimes nothing is written to the cnm file itself (Header "X-PMFLAGS:") nor to the _INBOX_.PNM. 

Actually, the files have a newer modified date, but they are identical to the version before.

Something is written to newmail.cac, but since this file is binary, I can't so easily tell what has changed.

Is this a known problem? The forum post "Mercury 4.73 & Thunderbird - multiple duplicate mail" seems to result from a similar or the same problem. I will have to revert to 4.71, which I'd like to avoid, since the new version seems to be much more stable than the old.

Greetings

Markus

> Is this a known problem? The forum post "Mercury 4.73 & Thunderbird - multiple duplicate mail" seems to result from a similar or the same
> problem. I will have to revert to 4.71, which I'd like to avoid, since the new version seems to be much more stable than the old.

Mercury does not delete (EXPUNGE) a file when there are multiple connections to the mailbox.  Could this be your problem?