Re: [Evolution] Connecting Evolution to an Exchange 2010 server

[Milan Crha <mcrha redhat com>]

On Wed, 2022-03-23 at 17:57 +0700, Frederic Muller wrote:
> Thank you. Did that. Webmail URL now gives 404 on http and on https
> says:
> mail.domain.com uses an unsupported protocol 
> ERR_SSL_VERSION_OR_CIPHER_MISMATCH

        Hi,
makes sense, the Exchange server "forces" https:// usage this way. It's
for good.

> I tried the default one ie exchange.domain.com/EWS/Exchange.asmx , 
> mail.domain.com/EWS/Exchange.asmx and the same without Exchange.asmx.

Use: https://mail.domain.com/EWS/Exchange.asmx
Nothing else will work.

> They all gave me this error:
> The reported error was "6 peer failed to perform TLS handshake. A
> packet with illegal or unsupported version was received."

It's the same error as in the web browser. The server tries to use too
old crypto algorithms, which you've disabled by the crypto policies.

The "Did that" at the beginning of the mail was for changing the crypto
settings. What precisely did you do?

I can successfully connect to an Exchange 2007 server on an ancient
Microsoft Server with the LEGACY crypto policy on an up-to-date
Fedora 35. I verified it claims the same error with the DEFAULT policy.
Condensed steps, just open a terminal and run these commands:

   $ sudo echo LEGACY >/etc/crypto-policies/config
   $ sudo update-crypto-policies
   $ evolution --force-shutdown

The update-crypto-policies should say: "Setting system policy to
LEGACY", with a note about restarting the system.

Then run Evolution and it'll work. When you restart the browser it
should work as well. Unless your Exchange 2010 server uses something
even more ancient than the Exchange 2007 I have.

        Bye,
        Milan