Version: 1.5.2 (using KDE 3.1.2) Installed from: (3.0) Compiler: gcc version 2.95.4 20011002 (Debian prerelease) OS: Linux (i686) release 2.4.19 Hi! When walking through the list of mails by constantly pressing 'n' (next message) marking mails as read sometimes works and most of the time it does not. With older version of KDE (I'am not fully sure about the exact version, but I remember that it worked with early 3.0.x woody packages) I did not notice that behaviour. Probably it came up with the 3.1.x version. On the server side I'm using the standard Debian woody uw-imapd-ssl package. Which I did not change since installation. Stephan
I just checked this, and current CVS still has this behaviour. But I must say that just holding down "n" or NKP+ skips through all unread messages very fast, und KMail seems to mark the messages as read only *after* it has completely displayed them once, thus with the fast skipping KMail never gets to display the message and thus it is not marked as read. In my eyes this is a feature, not a bug. KMail should not mark messages as read if it never actually displayed them, because they cannot have been read. If one needs to clear a folder of unread messages, one can either mark all messages one wants to be "read" and use the menu to mark them as such, or use the function "Mark all messages as read" from the folder menu. If one needs to do this very often, one can assign a keyboard shortcut to "Mark all messages as read" and use that. Does this "fix" or invalidate the bug? Patrick
Patrick, this does not really fix it because kmail doesn't mark the mails explicitly as read. If you fetch a message from an imap server it is marked as read by the server for the logged in user. So it doesn?t really matter if the message is displayed completely because the server should mark it as soon as it?s downloaded.
I just checked, what happens on the link: I marked some messages as unread and pressed and held NKP+. KMail quickly cycles through the unread messages, without marking them as read. On the network I can see, that every message actually *is* fetched everytime KMail goes past the message, but it is not marked as read. I assumed the delay in KMail was from downloading the message, but this obviously was not the case. I did not check immediately, because all IMAP traffic here is encrypted, and so I couldn't see the Application Level Data. I could supply a complete dump of such a "cycling session", but I assume that it is easily reproducible... Sorry for stirring it up... Patrick
Stephan, could you have a look at http://bugs.kde.org/show_bug.cgi?id=59625 and check if the changes gmx made helped with your issue as well? If so, please close this bug report.
This seems to work now (CVS as of 19082003) Patrick
Closing, appears to be resolved according to the reporter.
It helps to actually change the status. :)