I moved several a few ten thousands of mails that mailfilter agent was filtering to a wrong folder due to a wrong filter rule to the right folder. I did it in several steps and made the following observations: Reproducible: Always Steps to Reproduce: 1. Have a local maildir folder with about 60000 mails as source 2. Have a local maildir folder with about 12000 mails as destination. 3. Move about 20000 or 30000 of mails from source to destinations in three or four steps - Select first mail - Select last mail you want to move with shift click - Drag to other folder and select move. Do it in these three different ways: 1. Have source folder in usual threading view by activity. 2. Have source folder in flat date view. 3. Immediately switch to another folder after you started the move operation. Actual Results: The results of the three different ways as I got them: 1. First akonadiserver and maildir agent are very active, as well as mysql. Bursts of mysql activity (with recent Akonadi 1.13 branch git with MySQL optimizazions as of today – didn´t change in last time). Then kmail at 100%. Displaying progress. Taking several seconds for each 10 mails according to progress report. Takes ages! 2. Similar. Maybe a bit better. 3. Akonadiserver and maildir agent active. Akonadiserver writing, maildir agent reading. Then strong bursts of MySQL up to 250% of CPU usage for a minute or more. Then move done. No significant CPU activity of KMail. Move is *way* faster. Expected Results: Even with source folder open move is *fast*. Maybe be KMail using some kind of delayed updates while clearly showing folder message list view is in process of changing. Don´t update for every since mail that is being moved. Using kmail 4.14.2 but self compiled kdepimlibs, kdepim-runtime and akonadi server as 24 February (with akonadi server having had no changes since then.
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.
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 more recent), please open a new one unless it already exists. Thank you for all your input.