https://bugs.kde.org/show_bug.cgi?id=338238
--- Comment #7 from Martin Steigerwald <[email protected]> --- Thanks, Giuseppe, if I get this right you are not comfortable with that Akonadi temporarily stores moved mails in database or file_db_data (depending on payload size) instead of moving them directly to the destination folder and that by copying and deleting you instead get an instant move? Well, currently this Akonadi works as designed. Its in the design that Akonadi will also cache *writes* for some amount of time. I don´t know why according to how I understand you it doesn´t do that on copy/delete instead of move, but I know that basically its currently how its working. For some usecases this is may even be needed, i.e. when a backend, like IMAP server, is unreachable and KMail would like to store a sent mail into sent folder of it. If its this, then I suggest I set the report to confirmed but also make it a wishlist item. I also would like Akonadi to *only* be a read cache for all use cases, so that you can safely remove the cache at any time. But currently this is not how Akonadi is designed to work. And for some workloads it may not even be possible to do it this way (like storing mail on IMAP server). So please tell me, whether I got your concern correctly and I will make the suggested changes to the bug report. As far as I got during KDE Randa Meetings the team is aware of this behavior. And there are ideas to change it at least partly. Feel free to discuss on IRC #kontact or mailinglist. (I think the bug should just track the request / wish as such.) -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
