Version: 1.6.2 (using KDE 3.2.3, compiled sources) Compiler: gcc version 3.3.3 [FreeBSD] 20031106 OS: FreeBSD (i386) release 5.2-CURRENT As I write this, KMail shows, there is one unread message in my IMAP inbox (and 1500 read ones). I can confirm the presence of the new message by ssh-ing into the server. However, the repeated requests to "Check mail in this folder" claim "No new messages" and clicking on the "Next unread messages" leaves the focus, where it is -- on the already read message. Why is the list of messages not automaticly updated, when the count changes? Why are the new messages not added and the lie "No new messages" displayed, when there are, in fact, new message(s) in the mailbox? The only workaround, I found for this is to kill the corresponding kio_imap4 process and have kmail start a new one... Yack...
> Why is the list of messages not automaticly updated, when the > count changes? Why are the new messages not added and the lie > "No new messages" displayed, when there are, in fact, new message(s) > in the mailbox? Because we are bad people and like to be cruel to strangers. I've seen this as well, will look into it.
Any chance to test this with kdepim 3.3 (aka kdepim HEAD)?
I am seeing something like this in HEAD right now and I saw similar things many times before. Right now the kicker icon shows one unread message in a folder, even though there are no more unread messages. When I right-click on the kicker notification and select "New messages in -> folder" it jumps to the message and the notification goes away. If I check the account for new messages, the last message is again marked as unread. Even killing the imap ioslave does not get rid of it.
The problem still exists. Right now it shows 2 new messages in a folder, but there aren't any. Everytime it checks for new mail, it shows 2 new messages again. It only disappears if a new message is posted to that folder. Right now its always the same IMAP folder. KMail's debug output doesn't look useful, nothing unusuall in there.
In general KMail's interaction with kio_imap processes needs fixing. If I had a dime for every time a KMail oddity was fixed by killing the kio_imap process (and having KMail restart it), I'd be stinky rich now. Mozilla's IMAP seems a lot more robust to me, although they lack some nice feature KMail offers.
I think I figured out when the new message counter gets messed up. It seems to happen if someone edits the message in the IMAP folder. For example, we have a news folder here where university news are announced. The folder is read-only for me. If a message in the folder gets edited, KMail gets confused and marks the message as new (see my comment above).
On Monday 18 October 2004 18:04, Ralf Holzer wrote: > I think I figured out when the new message counter gets messed up. > It seems to happen if someone edits the message in the IMAP folder. For > example, we have a news folder here where university news are announced. > The folder is read-only for me. If a message in the folder gets edited, > KMail gets confused and marks the message as new (see my comment above). Well, if the message is changed, maybe (likely) it gets a new uid on the server, which means it _is_ a new mail.
Some bugs about wrong unread count in the system tray icon: bug 75583 bug 83893 bug 87738 bug 119350 bug 131917
I can no longer reproduce this bug on trunk r855160. Steps I took to reproduce (dIMAP account): - Activate system tray icon. It shows 0 unread mails. - Login to my webmailer, mark 10 mails as unread. - Refresh the folder - System tray icon shows 10 unread mails. Please check if you can still reproduce this bug with a recent version of kmail.
This seems to be fixed. Please reopen if problems persist.