GNOME Bugzilla – Bug 318004
Not able to change the properties of mails, if we start evolution in offline
Last modified: 2013-07-23 14:33:57 UTC
Steps to reproduce the problem: 1.Start evolution in offline 2.Try to mark a mail as read/unread, important etc.. or try to delete a mail. Nothing works.
This is happening with the devel snaps dated, 3rd Oct 2005.
*** Bug 327410 has been marked as a duplicate of this bug. ***
*** Bug 328587 has been marked as a duplicate of this bug. ***
It is not merely when we start evolution in offline mode. If we start it in online mode - then switch to offline, Do something , come-back-online even then the changes are not synced properly.
possible duplicates: 318006, 312433 better but still not ok in 2.5.91: 1) starting "evolution --offline" with no evo process running -> messages cannot be deleted, moved or marked as read 2) switching to online and back to offline -> everything works fine Try terminating and restarting evolution also by using --force-shutdown and --offline But switching from offline when update/delete doesn't work to online and back to offline fixes the situation: delete and update work.
still not working with 2.6.0. simplest way to reproduce: make sure no evo component is running (--force-shutdown), disconnect network cable and other network connections (like a disconnected laptop), start evolution, try to move/delete mails in the exch inbox. Dozent werk... any news about how to aproach this major bug ? can the developers or others reproduce it ? this behaviour is the only reason for me not yet to use evolution in my corporate environment (although I'd like to very much)
*** Bug 318006 has been marked as a duplicate of this bug. ***
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.