Version: 1.9.7 (using KDE 3.5.7, Kubuntu (feisty) 4:3.5.7-0ubuntu1~feisty2) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.20-16-lowlatency New bugs and crashes for 1.9.7: * Various crashes while trying to manually apply filters to multiple selected messages * Incoming message filtering only works on the first message * Manual application of filter(s) to individual or selected messages does not filter every message. Some messages are visually tagged as deleted (strike-through text) but not actually processed. Refresh of the IMAP folder reveals these message still exist. Bugs and crashes still existing from 1.9.6: * Random crashes while manually applying filters to individual messages in succession. * Incoming message filtering works sporatically, especially after initial IMAP login / folder check. (this is much worse in 1.9.7) * Filtering is extremely slow. There seems to be an IMAP folder refresh after each message filtered, including update of the on-disk index. Most IMAP clients have filters that efficiently operate on multiple messages at once. These could probably be broken down into multiple bug reports, but it would not be worthwhile. It is clear that the filtering code at fault is sloppy and needs a major overhaul. This insane "whack a mole" bug fixing does not work and needs to end. IMAP filtering was supposed to be improved with KMail 1.9.7 from KDE 3.5.7. I have found the exact opposite to be true. For each bug listed as fixed in each KMail release, it seems several more are created. A re-write of the filter code (and perhaps some IMAP code) is desperately needed. Honestly, KMail is an embarassing quality control problem for KDE right now. As one of the most popular and important pieces of KDE software, there is no excuse for release code with such obvious bugs. 10 minutes of casual testing would have caused any of these issues show up. I propose that once these issues are resolved, a KDE 3.5.8 bugfix release be made quickly. Thankfully, most stable distros are currently using 3.5.6.
Closing for the following reason: 1) No more than one bug in each bug report. You say it's not worthwile, but it is. Also look if it has been reported earlier. 2) If you report crashes, also include backtraces. Please read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports on how to proceed. 3) Criticism like: it's broken, rewrite it is not what I consider constructive.