GNOME Bugzilla – Bug 311362
ximian/evolution connector does not take a port number in the url field
Last modified: 2013-07-23 14:28:47 UTC
Version details: Patched Fedora Core 4 Distribution/Version: Fedora Core 4 (0) Port redirect to be able to access the corp. exchange server (imc.mycompany.com) behind the firewall, for example: ssh -X -L2005:imc.mycompany.com:443 me@ssh-box.mycompany.com (1) Launch evolution (2) Add an exchange account (3) for the url enter https://localhost:2005 (4) hit "authenticate" (5) observe evolution hang Workaround - be root and redirect 443 (the https port) if one is root one could ssh -X -L443:imc.mycompany.com:443 me@ssh-box.mycompany.com and enter https://localhost and connector works fine. That is if you are comfortable running as root (I'm not) and want to use 443 that way (I don't) The fix would be to parse the port in step 3 above and direct the socket to use it.
I tried working around it by setting the http_proxy and ssl_proxy variables to point to the corperate proxy server ... after all, if I set firefox to go to localhost:2003 for proxy it successfully redirects to gatekeeper:80 and I can log into owa using firefox. No joy setting up an evolution-exchange account doing that, even when setting the http and https proxy settings using Desktop->Preferances->Network Proxy. *sigh*
Sorry that this report has not received attention earlier. Note that the package "evolution-exchange" is deprecated nowadays. Similar functionality is now provided by "evolution-mapi" and "evolution-ews" packages. This bug was reported against a version that is now not supported anymore. Could you please check if the problem that you reported here still happens with a recent version of Evolution (like 3.2 or 3.0) AND with either evolution-mapi or evolution-ews? Thanks in advance!
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.