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 572668 - Mail folders not synchronized when accessed from multiple clients
Mail folders not synchronized when accessed from multiple clients
Status: RESOLVED DUPLICATE of bug 583490
Product: evolution-mapi
Classification: Applications
Component: Mail
0.25.x
Other All
: Normal minor
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2009-02-21 17:28 UTC by Vincent Bossier
Modified: 2009-06-10 10:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vincent Bossier 2009-02-21 17:28:40 UTC
Please describe the problem:
When accessing my mailbox both with an Evolution/MAPI and a native Outlook client, all operations made through Outlook are not detected by Evolution. For example, if a delete a mail with Outlook, Evolution will still show it in the summary list. Evolution will though fail to display the mail summary (telling that it cannot retrieve the message from the server). This behavior remains even if I restart Evo (with a --force-shutdown).

Steps to reproduce:
1. Launch Evo and retrieve mail summaries
2. Shutdown Evo
3. Delete one of messages with Outlook
4. Launch Evo: the deleted message still appears in the list


Actual results:
The deleted message still appears in the summary list although the message has been deleted from the server.

Expected results:
The message summary should have been removed from the list.

Does this happen every time?
Yes.

Other information:
This behavior is not linked to Outlook, the use of the web client leads to the same problem.
Comment 1 Johnny Jacob 2009-06-10 10:21:34 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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