After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 658669 - unread messages count is wrong
unread messages count is wrong
Status: RESOLVED DUPLICATE of bug 559391
Product: evolution-mapi
Classification: Applications
Component: Mail
3.0.x
Other Linux
: Normal minor
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-09 17:40 UTC by rmeador
Modified: 2011-09-12 08:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description rmeador 2011-09-09 17:40:51 UTC
If I read a message in my Exchange mail account through a client other than Evolution (such as via a cell phone or through OWA), the message is marked as read in Evolution, but the count of unread messages listed next to the folder (inbox, in this case) remains unchanged.  The only way to get the count to reset is to restart Evolution (refreshing the folder does not help, nor does disconnecting and reconnecting Evolution).  I don't know if it's significant or not,  but the "unread mail" icon works correctly, in that it doesn't show any unread messages, even though the unread count for the inbox is non-zero.

I have seen many bugs about this behavior for IMAP (where I guess it is being intentionally ignored?), but I didn't find this issue reported with MAPI.
Comment 1 rmeador 2011-09-09 17:42:43 UTC
I forgot to mention I'm using Exchange 2010 on Evolution 3.0.3 with evolution-mapi 3.0.3-2 on Fedora 15.
Comment 2 Milan Crha 2011-09-12 08:12:54 UTC
Thanks for a bug report. I'm not sure if I would call those bugs "ignored", it's just sometimes not that easy to reproduce. Nonetheless, I think those bugs are all the same, as users can reproduce them with various providers (as you mentioned IMAP, now MAPI and some users even under On This Computer). That's the reason why I'm marking this as a duplicate of one of them.

*** This bug has been marked as a duplicate of bug 559391 ***