Unexpected imap expunge of "mark as deleted" tb client by "move to trash" tb client by doing imap CLOSE before shutting down
Categories
(Thunderbird :: General, task)
Tracking
(Not tracked)
People
(Reporter: gds, Unassigned)
Details
This is more documentation than a real bug. I've run into this a few times doing testing and always have to research what is going on.
You have a tb client set up to use imap "just mark as deleted" and you have several messages marked as delete in folder A so they appear crossed out on that client.
On another tb client you have the same account set to "move deleted to trash" and select folder A. Of course, the messages marked out on the other client are not visible, as expected. But if you shut down the "move deleted to trash" client, the crossed out messages in folder A are expunged from the server causing them to unexpectedly vanish from the "just mark as deleted" client.
When tb shuts down normally, the imap CLOSE occurs and imap CLOSE always does an expunge of any messages in the SELECTed mailbox that are marked \DELETED. However, the imap CLOSE is skipped if the delete method is other than "move deleted to trash"
and only a LOGOUT occurs so no unexpected expunge occurs if both clients are set to "just mark as deleted" or to "remove immediately".
I suppose that the the imap CLOSE on shutdown could be skipped for all delete methods and just do LOGOUT. Doing CLOSE for "move to trash" (causing an expunge) is probably less important now that more servers support imap MOVE extension or UIDPLUS (to simulate MOVE) and don't leave messages marked \DELETED from doing a COPY to trash that need to be expunged.
|
Reporter | |
Updated•4 years ago
|
|
|
Reporter | |
Comment 1•2 years ago
|
||
I'm marking this RESOLVED as a DUPLICATE of bug 1828372 which eliminated the imap CLOSE issue described above.
Description
•