GNOME Bugzilla – Bug 481006
Deleted mail in offline mode not reflected on Exchange server, then not downloaded again
Last modified: 2013-07-23 14:35:12 UTC
Please describe the problem: When I delete mail in Evolution using Exchange in offline mode, upon reconnecting to the internet, my new mail is received, but any mail I deleted in offline mode is not told to be deleted on the Exchange server, nor is it re-downloaded into Evolution. When I Send/Receive mail, it shows for a moment the number of 'unread' messages on the server, but then switches to the number of unread on my computer. I've tried restarting Evolution and even so much as deleting and re-making the account. Neither options updated my inbox. The only thing that worked was to delete the .evolution folder. However, I had to re-download all ~1500 emails. Steps to reproduce: 1. Enable Exchange folder to 'copy folder content locally for offline operation'. 2. Remove internet connection / Click work offline. 3. Delete messages from inbox. 4. Reconnect internet / Click work online. 5. Send / Receive messages. Actual results: My Evolution inbox still has the same messages on it plus any new messages that have arrived since being disconnected minus any messages I tried deleting while offline. The total number of unread messages flashes all the unread messages still on the server (including the messages I tried to delete while offline). The server still holds all the messages I tried deleting while offline. Expected results: I would expect Evolution to send a notice with all the deleted emails to the server deleting the emails off of the server. Does this happen every time? Every time. Every Exchange account. Other information: I'm using Evolution 2.12 in Ubuntu Gutsy (development).
I tried same steps and it is valid in 2.22.2. You can see deleted mails in outlook but evolution misguides that it has deleted mails in offline.
The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers. If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible). There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX. Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago. evolution-exchange is now deprecated and not under active development anymore. It is unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again. Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported. Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.