GNOME Bugzilla – Bug 312212
Mails lose flag status when copied from local folders to exchange folders
Last modified: 2013-07-23 14:34:31 UTC
Please describe the problem: Steps to reproduce: 1. Move or copy a mail with important flag set, from local folder to any exchange folder. 2. In the exchange folder, the important flag won't be set. Actual results: The flags are not preserved. Expected results: It should preserve the flags. Does this happen every time? yes Other information:
The copy/move from local folders, save messsage operations use append message to create the message in the exchange folder. The problem is because in append_message in mail-stub-exchange.c, the message is created in the server and the flag CAMEL_MESSAGE_SEEN alone is taken care of. To take care of the rest of the flags, like mark_one_read, the other flags also should be set right there. But it involves a lot of duplication of code. Instead the entry for that message in "messages by uid" hash for that folder can be created, process_flags can be used to set them, and then the entry can be deleted. Or a special entry with flags to be set, can be made in "messages by uid" hash and the flags can be set when refresh_folder is called on that folder. Please add your views.
In my view, it is a WONTFIX. Becuase, it is a too much ask to have a hash-table maintained with ALL uids across all folders just for the sake of maintaining flags across Evolution accounts. It will Instead, the right way to do this will be based on the IMAP model. We should try and sync up the custom flags with the server. The WebDAV protocol does not support custom flags. so we cant(shouldnt) fix this.
*It will increase the memory usage manifold.
Bumping version to a stable release.
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.