Bug 343619 - moving mails makes them reappear in origin location
Summary: moving mails makes them reappear in origin location
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.13
Platform: Ubuntu Linux
: NOR critical
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-31 10:29 UTC by ultrabla
Modified: 2018-02-01 09:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description ultrabla 2015-01-31 10:29:24 UTC 
more details about a bug

Reproducible: Always

Steps to Reproduce:
1. move mails to a different folder


Actual Results:  
mails are moved and than reappearing 

Expected Results:  
mails moved without reappearing in origin folder

is there even any developement done with kmail2?

kmail1 was so much more reliable... :(
Comment 1 Laurent Montel 2015-01-31 13:51:42 UTC 
There is development done but you still use an old version.
Last version is 4.14.5...

And this bug is not a kmail2 bug but a akonadi bug.
Comment 2 ultrabla 2015-02-08 09:11:21 UTC 
upgraded kubuntu to 14.10
now i have this:
Plattform-Version 4.14.1

the issue is still present.
Comment 3 Denis Kurz 2017-06-23 20:00:08 UTC 
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 4 Denis Kurz 2018-02-01 09:46:24 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.