GNOME Bugzilla – Bug 332711
Sent items and drafts folders should have Exchange accounts folders by default
Last modified: 2013-07-23 14:27:36 UTC
As of now, we are setting it to local sent and drafts folders, by default, during the account creation. For this we need to know a mechanism to find the account creation and Evolution invoke, as same signal account_added is emitted in both the cases.
I dont think there is any way by which you can identify if an account is enabled or created and disabled or deleted. This is the reason why we delete the ESources everytime. We need to have account_created signal too in addition to account_added. Something to note when the account-setup is re-written.
In my view, it is not a common scenario for an user to disable an account. So I will suggest overriding the sent/drafts URI with Exchange's URI whenever account_added is fired. Any thoughts?
I did not understand your question properly. But what if user wants them to be set to local sent and drafts folders? Proper solution is, While creating account, settin it to Exchange accounts draft and sent folders and then every time we restart we need to set it based on what user wishes it to be.
account_added signal will be fired when an account is created or enabled. We cant differentiate between them. So we can set the sent-items and drafts-folder URI to Exchange account's sent/draft folders. The little annoyance that it gives to the user is: When the user has changed the sent/drafts folders and disabled the account, the next time when the user re-enables the account, the sent/drafts folders will be set to the exchange account's folders and not his local things.
Not sure why this is needinfo. can not differentiating between the signals itself is the bug. that needs to be fixed or code has to handle it in some other way.
account_added will be fired when we enable or create an account and not when we startup evolution. So, when the user changes the Sent-draft folders and disables the account and re-enables it, it will reset it to the server's folders. I am not sure if this is a desirable thing. Srag/Sush: Suggest if I can implement this or not.
BTW, it is not just for Exchange, we are planning to implement the Drafts support for GW too in the next release. So the behavior that we design here will be used for all the providers until we re-write the account setup to introduce account_enabled signal.
srag/sush: *ping* (comment 6)
*** Bug 358266 has been marked as a duplicate of this bug. ***
Opening as per comment #5.
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.