Hi,

I'm trying to connect to our corporate exchange server using the latest Ximian connector (2.2.2), but without any luck. The error message only states that the connect to the server failed.
I can however, reach the Outlook Webfrontend through the browser, using the identical URL.

All of this has been working with an earlier Evolution release, however since I had to reinstall my machine and used the newer version, I have this problem.

ebrowse (comes with the ximian connector) reports an 'SSL Handshake failed' when run against the same URL. The E2K_DEBUG option, which is supposed to provide additional info does not seem to work either. It is set in the environment, but I can not see any additional info in the terminal where I start the connector.

The packaged I installed together with evolution are :

evolution-2.2.1.1.tar.gz
evolution-data-server-1.2.1.tar.gz
ximian-connector-2.2.2.tar.gz
evo-openldap-2.0.27-1.ximian.8.1.i586.tgz
krb5-1.3.5.tar.gz
libgtkhtml-2.6.3-i486-1.tgz
libsoup-2.2.3.tar.gz
pango-1.8.1.tar.gz

The machine runs slackware 10.1 (kernel 2.4.29).

I'm running out of ideas on how to trace down the issue and would appreciate any pointers into the right direction.

Thanks,
Peter

I don't have much to offer, except that I had been having similar (and other) problems for the past few weeks, and can now confirm that Evolution and Connector *do* work under Slackware 10.1, at least under some circumstances.

First thing I would recommend is to try without SSL; I *am* still having issues using the https:// version of our exchange server, though I can use Connector fine without SSL. Can you connect via normal http?

Thanks for the suggestion, but unfortunately only the SSL connection is available. So I don't have any possibility to try a connect via http.

But makes this issue particular annoying is that the tracing function does not seem to work (or I just can't figure out how to use it). So the idea that this issue has to do with the SSL Handshake comes only from the ebrowse tool and not evolution directly. Evolution (or rather the connector) still refuses to issue any error info in the terminal screen from which is was started, regardless of the the variable setting for E2K_DEBUG.

Cheers,
Peter