Evolution accounts listed always show 0 unread.

On Tue, 2009-10-27 at 17:14 +0000, Isaiah Heyer wrote:
> I am using 9.10 rc, and I noticed that the indicator applet now shows a
> list of all my email accounts in evolution. Is the number in parenthesis
> to the right of each email address supposed to show the number of
> unread? Because for me there is always a zero next to every email
> address, even when I have unread messages.

No, it is supposed to show the number unviewed. So when evolution is
running behind other applications and downloads e-mail while you're
doing something else, then that number will increment. For many people
unread isn't useful as the number is always very high :) Thanks!

  status invalid

Well, it doesn't seem to do that for me either. When I amusing a different program and a "New Message" notification pops up, shouldn't that increment the number of unviewed? For me it doesn't.

On Tue, 2009-10-27 at 19:14 +0000, Isaiah Heyer wrote:
> Well, it doesn't seem to do that for me either. When I amusing a
> different program and a "New Message" notification pops up, shouldn't
> that increment the number of unviewed? For me it doesn't.

Hmm, that's probably a different issue then. Please look for a similar
bug or file one under the evolution-indicator.

  http://launchpad.net/ubuntu/+source/evolution-indicator/

im affected by this bug too

evolution fetches emails from gmail via pop, shows a toaster notification for unread emails but notification-applet does not show any indication nor lists the correct number of unread messages (instead always 0).

I also tried to reset my evolution settings by deleting ~/.evolution and ~/.gconf/apps/evolution and logging out and in again.
But that did not change anything. As soon as i reconfigured my email accounts in the now fresh evolution i have exactly the same buggy behaviour as before.

I've changed the status back to New as this is definitely a bug. Further to comment #2, the indicator applet always shows zero even when unviewed emails exist in Evolution.

OK, this is actually a duplicate of bug #436755 and possibly bug #378986.