Bug 729 - IMAP immediate expunge of deleted messages
Summary: IMAP immediate expunge of deleted messages
Status: RESOLVED FIXED
Alias: None
Product: Sylpheed-Claws (GTK1)
Classification: Unclassified
Component: Folders/IMAP (show other bugs)
Version: 1.0.4
Hardware: PC FreeBSD
: P3 enhancement
Assignee: sylpheed-claws-users
URL:
Depends on:
Blocks: 704
  Show dependency tree
 
Reported: 2005-04-27 18:00 UTC by Eugeny N Dzhurinsky
Modified: 2005-06-13 21:39 UTC (History)
1 user (show)

See Also:


Attachments

Description Eugeny N Dzhurinsky 2005-04-27 18:00:38 UTC
May be I missing something - sorry then - but i really need the deleted message
e DELETED - not  moved to Trash folder, which griefly will take a lot of time if
message is too long (i almost sure the Sylpheed downloading the message and then
uploading the message back to server, but i may be wrong).

I hope there is some configuration parameter, which controls this, otherwise it
seems to be a bug?
Comment 1 Peter Gervai 2005-04-29 14:04:22 UTC
Just a sidenote: when moving messages from IMAP to local, s-c does that in this
highly stupid way:

[...]
[09:49:42] IMAP4< 650 OK Fetch completed.
[09:49:42] IMAP4> 651 UID FETCH 135348 BODY.PEEK[]
[09:49:42] IMAP4< * 574 FETCH (UID 135348 BODY[] {1942}
[09:49:42] IMAP4< )
[09:49:42] IMAP4< 651 OK Fetch completed.
[09:49:42] IMAP4> 652 UID FETCH 134792 BODY.PEEK[]
[09:49:42] IMAP4< * 18 FETCH (UID 134792 BODY[] {7405}
[09:49:42] IMAP4< )
[09:49:42] IMAP4< 652 OK Fetch completed.
[09:49:42] IMAP4> 653 UID FETCH 135349 BODY.PEEK[]
[09:49:42] IMAP4< * 575 FETCH (UID 135349 BODY[] {7022}
[09:49:42] IMAP4< )
[09:49:42] IMAP4< 653 OK Fetch completed.
[09:49:47] IMAP4> 654 UID STORE 134794 +FLAGS.SILENT (\Deleted)
[09:49:47] IMAP4< 654 OK Store completed.
[09:49:47] IMAP4> 655 EXPUNGE
[09:49:49] IMAP4< * 20 EXPUNGE
[09:49:49] IMAP4< 655 OK Expunge completed.
[09:49:49] IMAP4> 656 UID STORE 135351 +FLAGS.SILENT (\Deleted)
[09:49:49] IMAP4< 656 OK Store completed.
[09:49:49] IMAP4> 657 EXPUNGE
[09:49:49] IMAP4< * 576 EXPUNGE
[09:49:49] IMAP4< 657 OK Expunge completed.
[09:49:49] IMAP4> 658 UID STORE 134795 +FLAGS.SILENT (\Deleted)
[09:49:49] IMAP4< 658 OK Store completed.
[09:49:49] IMAP4> 659 EXPUNGE
[09:49:52] IMAP4< * 20 EXPUNGE
[09:49:52] IMAP4< 659 OK Expunge completed.
[09:49:52] IMAP4> 660 UID STORE 135352 +FLAGS.SILENT (\Deleted)
[09:49:52] IMAP4< 660 OK Store completed.
[09:49:53] IMAP4> 661 EXPUNGE
[09:49:53] IMAP4< * 575 EXPUNGE
[09:49:53] IMAP4< 661 OK Expunge completed.
[...]
(and further thousands of separate expunges)

I guess deleting may suffer the same. Would be nice to have a setting: "Update
imap box every N messages", and if I put 100 there it does 100 WHATEVER _then_
one EXPUNGE. And 0 should mean "EXPUNGE at the very end, no matter what".

You should see that expunge (or any complete mailbox rewrite commands, if
there's any more) is very expensive on the server, especially on large inboxes.
Above 100MB it pretty much chokes the imap server.
Comment 2 Martin (calim) 2005-05-20 14:45:39 UTC
I speak about the IMAP case:
the problem i think is that when you ask sylpheed to empty trash, the program
freezes during all the time period needed to expunge ...
Maybe it would be great if the "Empty trash" command was threaded for example ?
( like in Thunderbird/Mozilla ).
Comment 3 Colin Leroy 2005-06-13 21:39:50 UTC
Fixed in 1.9.11cvs64

Note You need to log in before you can comment on or make changes to this bug.