Version: (using KDE KDE 3.2.92) Installed from: Gentoo Packages Compiler: gcc (GCC) 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6) OS: Linux This is very similar to bug 66025. Basically, while viewing messages in thread view and the head of a thread is deleted, kmail appears to perform the following actions in order (assuming "mark selected message as read after 0 sec" is set): 1) Mark thread for delete 2) Move to next message in tree 3) Delete thread head 4) Display now selected message 5) Mark message as read 6) Resort message list if required (ie: due to date sorting) 7) Reposition message selector at new 'top' of unread messages 8) Display now selected message 9) Mark message as read The problem happens at item 5. This ends up with messages being marked as read before someone has a change to really see them. The obvious work around is to set 'view messages as read after 1 second' (or some other non-zero value). This, however, is probably not the correct long term solution.
I wanted to test with KDE 4.3, but I'm already stuck with step 1. What do you mean with "Mark thread for delete" ? You can either delete the thread or mark it as something, but not mark as delete. Please try with a current KDE version or explain in more detail. Thanks.
No response - closing. If it is still reproducible, please reopen.