AquaMail Forum

English - Android => General Discussion => Topic started by: guybrush23 on February 22, 2016, 03:48:57 pm

Title: Exchange EWS Integration not to Autodiscover?
Post by: guybrush23 on February 22, 2016, 03:48:57 pm

Hi,

i just tried out exchange autodiscovery. Unfortunately it seems it is not fully integrated. Due to MS there are several entry points for discovery.

Aquamail possibly just tries to connect to mail@domain.com/autodiscover/autodiscover.xml. But in a lot of companys domain.com is the http webserver. Therefore, mostly used is autodiscover.company.com/autodiscover/autodiscover.xml as reference.

I can just conclude this from the behaviour as there is no real documentation how aquamail is using ews autodiscovery? Is there a workaround? E.g. to define the path manually?

Regards guybrush

Title: Re: Exchange EWS Integration not to Autodiscover?
Post by: Kostya Vasilyev on February 22, 2016, 10:12:17 pm

Yes, the AutoDiscover spec is very confusing (at least to my pea sized brain), so in the "official" 1.6.0 it only does what you wrote, "autodiscover.domain.com".

The newer 1.6.1 does this too:

Quote

autodiscover.company.com/autodiscover/autodiscover.xml

which works with Office 365 quite well and also Amazon Work Mail.

Title: Re: Exchange EWS Integration not to Autodiscover?
Post by: guybrush23 on April 05, 2016, 12:39:43 pm

bHi Kostya,

thanks for your answer. Basically I use for testing my EWS connectivity also the "Microsoft Remote Connectivity Analyser" and it says everything ok.

I now fixed it by adding manually autodiscover . company . com as a server. So it seems it not yet works automatically and/or tries only one method. Unfortunately I did not find a logging way.

Regards Martin

Title: Re: Exchange EWS Integration not to Autodiscover?
Post by: Kostya Vasilyev on April 05, 2016, 11:17:29 pm

What it does (new in 1.6.1) is this:

GET (using HTTP, not HTTPS) to:

http://autodiscover.company.com/autodiscover/autodiscover.xml

No authentication (login / password) at this point.

The server is supposed to do a redirect (HTTP code 301 or 302) to your real autodiscover server, and this has to be an https:// URL.

At this point, the app would execute an HTTPS POST, now WITH authentication, to:

https://your.real.autodiscover.server.com/autodiscover/autodiscover.xml

( e.g. for an Office 365 account using a custom domain, this would be something like s-autodiscover.outlook.com )

And now finally this should return the actual server settings.

That's in MS documentation, maybe there are more autodiscover methods, but this one is very popular (used by Office 365 and Amazon Work Mail both).

So no, it should not be necessary to run your actual EWS server under autodiscover.company.com.