[horde] outlook 2019 need "imap autodiscover.xml" and outlook 2013 need "active-sync autodiscover.xml"

[Michael J Rubinsky]

Quoting Ralf Lang <lang at b1-systems.de>:

> Hi Michael,
>
> Am 10.10.20 um 21:42 schrieb Michael J Rubinsky:
>>
>> Quoting Arnold | Universität Bremen <horde at bugs.uni-bremen.de>:
>>
>>> Moin!
>>> Horde serves the autoconfigure requests of many clients in the
>>> university of bremen.
>>> There are many different Outlook versions. Not all of them can
>>> connect via activ-sync with horde.
>>>
>>> Outlook/16.0 (16.0.4266.1001; MSI; x64)
>>> Outlook/16.0 (16.0.5023.1000; MSI; x86)
>>> Microsoft Office/16.0 (Windows NT 10.0; Microsoft Outlook 16.0.10359;
>>> Pro)
>>> Microsoft Office/16.0 (Windows NT 10.0; Microsoft Outlook 16.0.4266;
>>> Pro)
>>> Microsoft Office/16.0 (Windows NT 10.0; Microsoft Outlook 16.0.5056;
>>> Pro)
>>> Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
>>> Thunderbird/78.2.2
>>> AppleExchangeWebServices/309 accountsd/113
>>> Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.7257; Pro)
>>> MacOutlook/16.41.20091302 (Intelx64 Mac OS X 10.15.6 (Build 19G2021))
>>>
>>> Can I activate a blacklist and outlook 2019 receives a imap
>>> configuration and outlook 14 receives a active-sync configuration.
>>>
>>> If $GLOBALS['conf']['activesync']['outlookdiscovery'] is true, all
>>> outlook clients receive a imap configuration?
>>
>> The request and response schemas are different for the 'mobilesync'
>> and 'outlook' - sending the response schema for 'outlook' when the
>> client requested the 'mobilesync' schema would not work.
>>
> Is there any way to discern who wants what? A header or an url param?


The client sends a request with the appropriate schema based on what  
kind of account is trying to be configured. In our EAS code, we use  
the schema to determine if they client is asking for an ActiveSync  
("mobilesync") configuration or an "outlook" configuration - which can  
be used to configure IMAP mailboxes.


Of course, this only applies to the original AutoDiscovery protocol.  
In the last few years Microsoft has started using AutoDiscovery v2  
which is not fully documented in relation to EAS anywhere I can find.  
This protocol involves the EAS client actually hitting a Office 365  
endpoint, which in turn tries to get the Autodiscovery data from the  
appropriate server. We do have some support for the new JSON format of  
this protocol, but while I've seen successful responses to Microsoft's  
request, I've never gotten the autodiscovery data back to the client.   
The only place so far that this really works is with Office 365  
services. Any recent-ish version of Outlook will almost certainly be  
using v2.

>>
>>
> --
> Ralf Lang
> Linux Consultant / Developer
> Tel.: +49-170-6381563
> Mail: lang at b1-systems.de
> B1 Systems GmbH
> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 9272 bytes
Desc: PGP Public Key
URL: <https://lists.horde.org/archives/horde/attachments/20201011/9b45254c/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 851 bytes
Desc: PGP Digital Signature
URL: <https://lists.horde.org/archives/horde/attachments/20201011/9b45254c/attachment.sig>