Description of problem:
Evolution rarely has the right information on the Summary page for the
mailboxes. Right now it's showing 0/6 when I have 2 messages.
Yesterday it seemed to be taking a running total through the whole
day, 0/69 by the end when nothing was there. Etc.
Version-Release number of selected component (if applicable):
Use Evolution for a few hours, checking the Summary page every so often.
Steps to Reproduce:
What sorts of mail spools? Quickly looking this seems fine to me, but
I'll grant that I don't have a large sample at the moment :)
In this particular case it's POP3 off another server, so local
mbox-style folders for Evolution.
BTW, I'm not sure if it helps, but this seems to happen for ~all~ the
folders and just not Inbox. Any folder I add to the Summary page.. I
would think the type of spool wouldn't matter in that case because the
other folders are completely Evo stored... wait, that's not neccesary
true in the case of IMAP. In any case. *scratches head*
Hmm, all of mine are imap. Might be related. Will try to whip up
something to play with some remote pop as well.
You might try to just create a few local folders and move things in,
delete them, out, mark them read/unread. You don't have to setup POP
to replicate this, I just did it without POP at all.... a bogus local
user w/ local mail did the same thing for me. Cheers, -Ali
Ah ha! Something that might be useful.
I got home, 39 messages in my Inbox. Tons of spam I haven't trained on
yet. Well, I moved it to a training folder and wanted to train the
remaining of the Inbox as 'ham'. So I did that and it said it learned
39.... no no no.. Evo. doesn't show 39 in the inbox but the ~summary~
shows that and then some. It looks like the mbox file is ~not~
reflective of the Inbox in realtime. Make sense? Cat-ing the file
confirms it. Cheers, -Ali
Hmm... perhaps. If you expunge, does it reflect things?
Yep, expunge does it.
It happens all in Outbox - send message in offline mode, delete one
from outbox - Evolution is still trying to send previous number of
Closing this bug as newer Evo doesn't have the same structure to even have this
bug per se. Upgrade to RHEL 4. Cheers, -Ali
Thanks for the feedback.