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 537650 - Evolution Mail and Calendar: A message sitting in my ...
Evolution Mail and Calendar: A message sitting in my ...
Status: RESOLVED DUPLICATE of bug 581908
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-06-10 18:48 UTC by mathew.mathai
Modified: 2009-08-26 10:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description mathew.mathai 2008-06-10 18:48:44 UTC 
A message sitting in my Exchange account Inbox is visible using Outlook but is not visible in Evolution. Here are details:
On Friday, I received an email message from Charlie which was in reply to a message from Hunter. Though I saw Charlie's reply, I never did see Hunter's original message.  When I use Outlook under Windows XP I do see the message in the Inbox (so it's not a Junk filter issue) but I don't see the same message in the Inbox of Evolution. 


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.2 2008-06-03 (Ubuntu)
BugBuddy Version: 2.22.0
Comment 1 mathew.mathai 2008-06-10 19:29:36 UTC 
I forgot to mention that I did try "View > Show Hidden Message" to confirm that Hunter's original message wasn't inadvertently hidden. It wasn't i.e. it didn't show up when I asked Evolution to show me hidden messages.
Comment 2 Akhil Laddha 2009-08-26 10:31:16 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
we are happy to tell you that the problem has already been fixed. It should be
solved in the next software version. You may want to check for a software
upgrade.

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