Bug 281704 - Mails were deleted after moving folder
Summary: Mails were deleted after moving folder
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: Arch Linux Linux
: NOR critical
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-09 17:52 UTC by Jonathan
Modified: 2017-01-07 22:35 UTC (History)
6 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 Jonathan 2011-09-09 17:52:39 UTC
Version:           4.7 (using KDE 4.7.0) 
OS:                Linux

I moved the Inbox of IMAP account A to IMAP account B by accident. The Inbox contained about 100 mails. When I realized that I've dragged the wrong folder I immediately moved it back - approx. 5 seconds between the to moves via drag&drop.
I checked the mails back on the IMAP account A and everything looked alright. Then some time later I restarted kmail and akonadi (which I have to do a couple of times a day because of bug #260647). After the restart all mails in the Inbox of IMAP account A (the one which was moved back and forth) were gone.

Fortunately I could call the expensive service hotline and get all mails restored.

Reproducible: Sometimes

Steps to Reproduce:
I tried to reproduce it a couple of times and sometimes I had the same behaviour, sometimes everything was correctly moved back and forth. There seems to be several reasons why it didn't work:
*) The reason for the original failed behaviour might have been that the Inbox folder was too large (I'd guess it were approx 100 mails = 100mb as I had some bigger mails in there)
*) I could always reproduce it with moving the folder to a specific IMAP account C (one which wasn't involved in the original operation). Maybe this IMAP server does not support some required operations.
*) Once when trying to reproduce the steps kmail crashed. Unfortunately I didn't note down if this resulted in deleted mails or not, so I can't say it for sure, but I think this crash ended in a data loss.
*) I got a "There have been repeated failed attempts to gain access to a wallet. An application may be misbehaving." error from KDE Wallet while trying to reproduce the misbehaviour. So kmail was offline but still let me move the folder which ended up in the folder being nowhere after a restart.


Actual Results:  
All mails in the moved folder were deleted after restart.

Expected Results:  
Obviously the mails should be never disappear without further notice.
Comment 1 Matthias Kretz 2012-01-30 12:17:04 UTC
I also experienced this bug (well, it seems to be the same) yesterday. Here's what I did:
* open a folder with 900 mails (~200 MB)
* move all contained mails to a different folder on the same IMAP account

There was no feedback about an ongoing transfer of mails. After I closed Kontact and opened it up again only 137 mails (13 MB) were in the destination folder. The source folder was empty. I checked the maildir on the mailserver (dovecot) and saw that the IMAP server was in sync with what KMail showed.

Additional details:
* The account is accessed via a 1 Mbit uplink (~1/2h required for upload)
* The account is set to go offline when KMail closes.
* KDE SC / KMail 4.8.0 (Kubuntu packages)

changing severity to grave because of "loss of data"
Comment 2 David 2012-03-08 23:27:49 UTC
Happens on latest stable Fedora packages too (4.7.4).
Comment 3 András Manţia 2012-08-21 18:15:36 UTC
Is it reproducible with 4.9?
Comment 4 Volker Krause 2012-08-21 18:27:12 UTC
Cross-resource folder moves should be fixed in 4.9, comment #1 seems to be about mail moves only though.
Comment 5 Denis Kurz 2016-09-24 18:16:38 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 6 Denis Kurz 2017-01-07 22:35:14 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.