Version: (using KDE KDE 3.4.2) Installed from: Debian testing/unstable Packages OS: Linux I had the unfortunate task of merging two big (17000 and 9000 mails) folders. My naive aproach (select all in one and drag them to the other) failed miserably, kmail started to eat all the cpu and I had to kill it after waiting for minutes. Looking at the folders at the server revealed that nothing happened to them. Next I tried to select a few hundred messages and move only them. It worked, but it also used a lot of cpu and was very slow. When opened the "detailed progress window", I saw the every single message got it's own progressbar. I don't know if this means every messaga got it's own thread, trying to talk to the imap server or not, but either way it seems very unefficient and dangerous.
Confirmed. At least trying to copy 1000 mails doesn't work, I didn't look at the detailed progress window, I've run into this also.
the progress infos are seperate, but they are queued
Update: it didn't crash any more (1.9.5/3.5.5), and if I didn't open the detailed progress window, then it went reasonably OK. But if I did open in, then the constant refreshing ate all available CPU, made my mouse pointer jerky and generally degenerated my system's performance a lot.
In version 1.11.1 (KDE 4.2.1), this is still present. If I open "detailed progress window", the operation takes a lot more time than without it, which pretty much defeats the purpose of the progress window, I think it is necessary to have some optimalization there.
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding.
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.