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 338856 - ximian-connector-setup - still needed?
ximian-connector-setup - still needed?
Status: RESOLVED WONTFIX
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.6.0
Other opensolaris
: Normal normal
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2006-04-18 05:57 UTC by Glynn Foster
Modified: 2013-07-23 14:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Glynn Foster 2006-04-18 05:57:40 UTC
Given the new accounts wizard in evolution, is ximian-connector-setup still needed? It doesn't seem to get called from the user interface, nor given the current name very obvious that you can run it from the commandline. Should it either be removed, or renamed to something like evolution-exchange-setup? [ideally the first option would be better I think].
Comment 1 Sarfraaz Ahmed 2006-04-21 12:28:26 UTC
Yeah, all the functionalities present in the command line tool have been merged into the evolution account setup framework. It does make sense to stop shipping this tool for further releases now.
Comment 2 Sushma Rai 2006-04-21 13:06:31 UTC
Yes we still need it.
x-c-s has autoconfiguration support, which is helpful in 
case of mass deployment.
Until, we make our plugins to support autoconfiguration
(where OWA URL, GC server are read from a configuration file)
we need to rename x-c-s and keep it.
Comment 3 Sushma Rai 2006-05-24 06:54:52 UTC
*** Bug 341803 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2012-09-20 14:50:06 UTC
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".
Comment 5 André Klapper 2013-07-23 14:30:15 UTC
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.