GNOME Bugzilla – Bug 561549
Evo does not update the unread count
Last modified: 2009-06-20 18:11:44 UTC
Evo does not update the unread count on one of my IMAP accounts. I did work before in 2.22. I don't really know what part of the camel debug log I should provide.
Hubert, always reproducible? ANy steps to reproduce?
always, for only one account. so I guess it is also related to the server behind. Or maybe it is a coincidence.
Created attachment 123121 [details] bzipped log This is the log of Evolution with only the concerned account. I let it load, read a mail and then quit. The unread message count hasn't been updated. Also, Evolution ask for the password twice. (ignore the keyring error, it is a known issue) FWIW, no such problem in 2.22 (from openSUSE 11.0)
I migrated my other machine to 2.24 (openSUSE 11.1) and the problem exist too.
I used 2.24 a few weeks ago, and then switched back to 2.22, and now returned to 2.24, and I see this problem too, along with folders never expunging
Rodrigo, counts not updating with IMAP account right? Even though you mark read/unread, the counts dont update on the folder tree... right? If so I'm working on it. On Expunge, IMAP or other provider? Rodrigo, for expunge, can you set export CAMEL_DEBUG=all and get the console log for expunge? [Clear your console before you expunge, so that the log is clean] Thanks. Hub, onyour memory leak, I just figured out that new mails are leaked, Im on vacation, but should be back and fix it right away.
*** Bug 563124 has been marked as a duplicate of this bug. ***
Hub, I had setup a courier IMAP server and I dont know it works for me :( [Counts update right, if I mark as read/unread] on the foldetree. Anything different I must do?
if I knew what, I'd have put the information here. But what I'm sure of is: 1/ it does it on the other machine, same account 2/ it does not do it on the other courier imap account, the one which I control the server 3/ it does not do it on the Groupwise/IMAP.
*** Bug 568193 has been marked as a duplicate of this bug. ***
2.24.3 seems to fix it.