mail.imap.expunge_after_delete not working properly in 101.0b1
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(thunderbird_esr91 unaffected)
| Tracking | Status | |
|---|---|---|
| thunderbird_esr91 | --- | unaffected |
People
(Reporter: aholtz, Unassigned)
References
Details
(Keywords: regression, regressionwindow-wanted)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.54 Safari/537.36
Steps to reproduce:
Select to move deleted messages to a folder or select the option to delete messages immediately in the server/account settings.
Actual results:
When you delete a message it no longer shows in the folder list within Thunderbird. However, viewing the folder from another IMAP client shows the messages are still there.
If you have chosen to move deleted messages to a new folder, then the other IMAP client still sees the messages in the inbox without any flags. If you have chosen to delete the messages immediately, then the message in the other IMAP client shows it is marked for delete. But no expunge is occurring automatically as it has in prior versions of Thunderbird.
Expected results:
The folder should expunge the deleted messages immediately based on the mail.imap.expunge_after_delete setting being true. This behavior only appears to have occurred after the update to the 101.0 beta 1.
|
||
Updated•3 years ago
|
|
||
Comment 2•2 years ago
|
||
Confirmed in 102.10.1 (most recent on the release channel); basically, expunge_after_delete is completely broken.
I'm testing as follows. The mail server is running Dovecot, and:
(1) I have Dovecot enabled for rawlog_dir, so that I can trace IMAP commands
(2) I'm checking the size of the cur and .Trash direcopries to determine when a message is actually removed from the server
(3) I'm running doveadm quota get -u foo@example.com on the server to determine how much storage is used on the server. This always agrees with the results of (2) above
Additionally:
(4) I'm running Thunderbird in safe mode
(5) I have Roundcube running as well
(6) On TB, the mail account 'delete' settings are set to move the message to the Deleted folder. I can set it 'remove immediately' but that doesn't actually remove anything, of course
(7) mail.imap.expunge_after_delete is set to true
(8) I have tried mail.imap.expunge_option both at the default of 0, and set to 1; it makes no difference
When I delete a message from the inbox, it moves to 'Deleted'. The server shows a move for 'cur' to '.Trash', as expected. Disk usage does not decrease. When I then delete the message from 'Deleted' nothing happens on the server. Roundcube still shows the message as deleted. When I 'Empty' on Roundcube, the message is deleted on the server.
So, Roundcube works, TB doesn't. TB does communicate with the server and sends IMAP requests when deleting from 'Deleted', but the request does nothing. Roundcube sends a diferent request, which deletes the message. I hesitate to add lots of IMAP stuff here (which I don't understand), but the TB message is
1683553455.399035 A0002 SELECT Trash
1683553455.399917 A0003 UID STORE 1:* +FLAGS.SILENT (\Deleted)
1683553455.400664 A0004 CLOSE
1683553455.403481 A0005 LOGOUT
Curiously, when TB is run in normal (not safe) mode, it sends no IMAP request when deleting from the 'deleted' folder. I have no idea what that's about.
One more data point: moving an inbox message to local storage does not delete anything on the server. You still have to compress.
So, basically, the only way to force a delete on the server is to compress folders or restart TB.
There are two bugs related to Expunge that my explain the problem you are reporting:
|
||
Comment 4•1 year ago
|
||
(In reply to Felipe from comment #3)
There are two bugs related to Expunge that my explain the problem you are reporting:
aholtz do either of these describe part of what you see?
|
|
||
Updated•1 year ago
|
Description
•