Bug 281100 - IMAP downloads+uploads message instead of moving on the server
Summary: IMAP downloads+uploads message instead of moving on the server
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-31 10:53 UTC by S. Burmeister
Modified: 2017-01-07 21:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description S. Burmeister 2011-08-31 10:53:46 UTC
Version:           1.6.0 (using KDE 4.7.0) 
OS:                Linux

If one has a file in an IMAP's "sent" folder and deletes it, akonadi/kmail2 downloads it from the sent folder and then uploads it to the IMAP's trash folder.

This is slow and wasting bandwith.

Reproducible: Always

Steps to Reproduce:
Put a large message in your IMAP'S draft folder
Delete it, i.e. let kmail move it to the IMAP's trash and watch your network-traffic

Actual Results:  
A lot of network-traffic that downloads/uploads the email from the server to the server

Expected Results:  
Use IMAP commands to move message on the server without down/uploading it.

Something like select source
copy trash
mark copied message as deleted
expunge

OR with UIDPLUS expunge only the one deleted message.
Comment 1 Kevin Ottens 2011-09-17 16:11:59 UTC
Should be specific to KMail, the resource has all the wiring to do the move server side.
Comment 2 Denis Kurz 2016-09-24 17:55:18 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 21:41:39 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.