Hi there, i do have a problem with outlook autodiscover. I am using ISPAutomail https://schaal-24.de/ispconfig-automail/ and i have activated the proper alias domain and the CNAME and SRV DNS Records and the Plugin itself. It Works for Windows 10 Mail, Thunderbird etc. but not for Outlook 365. The CTRL + Autoconfugre Test Setting in Outlook itself correctly discover the XML Information though the automatic configuration doesnt work. The XML Information is: XML <?xml version="1.0" encoding="UTF-8"?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <SSL>on</SSL> <Type>IMAP</Type> <LoginName>***@****.de</LoginName> <Server>server1.***.de</Server> <Port>993</Port> <SPA>on</SPA> <AuthRequired>on</AuthRequired> <DomainRequired>on</DomainRequired> </Protocol> <Protocol> <SSL>on</SSL> <Type>POP3</Type> <LoginName>***@***.de</LoginName> <Server>server1.***.de</Server> <Port>995</Port> <SPA>on</SPA> <AuthRequired>on</AuthRequired> <DomainRequired>on</DomainRequired> </Protocol> <Protocol> <UsePOPAuth>on</UsePOPAuth> <SSL>off</SSL> <Encryption>TLS</Encryption> <Type>SMTP</Type> <LoginName>***@***.de</LoginName> <Server>server1.***.de</Server> <Port>587</Port> <SPA>on</SPA> <AuthRequired>on</AuthRequired> <DomainRequired>on</DomainRequired> </Protocol> </Account> </Response> </Autodiscover> but automatic configuration doenst work for Outlook on PC and Mac. It does work for the main domain in the App (iOS) though but not for the customer domain. https://testconnectivity.microsoft.com says: AutoDiscoverer Settings found BUT No AccountSettings where given. The DNS Records as excpected by RFC 6186 are also set. https://docs.microsoft.com/de-…ted-autodiscover-behavior doesnt help as well cause I basically do not have any subkeys in the Registry. Could you help me? Outlook 365 ISPCONFIG 3.2.3 Apache, Debian 10 Windows 10
Please post in english on this forum, or use the forum on howtoforge.de. From my limited knowledge of German, I think I understand the problem. Outlook changed their mechanism to autodiscover settings. It was quite some work for Florian to change the automail module, so this has not been done so far. The module is not developed by us and therefore I can't tell you much more.
@Th0m sorry i tried to translate the post. So I guess the basic answer is: The Automail plugin is currently just not rdy for the new discovery of Outlook 365? Do you have any idea what i could do now?
Yes, that's the case. Users will have to set up their accounts manually. Maybe @florian030 can tell you more - he is the maintainer of this plugin.
Ok thank you for the quick response. I hope there is another solution than manual setup cause this is honestly exactly what i do not want.
There will always be email clients that don't support the automatic setup, so some people will have to set it up manually.
I already tried to find some information about the changes without success. maybe you or other people here in the forum could help me to fix this problem, cause outlook is still more or less a popular client, so it might be a useful fix for others as well
If the specs for Outlook autodiscover are published or someone who knows how it works is willing to contribute then autodiscover plugin could be updated. It is frustrating to code against a hidden API. Easier and more pleasant work is readily available.
might be helpful.... Autodiscover: Some quick methods to get it working - HowTo-Outlook (howto-outlook.com) Outlook 2016 implementation of Autodiscover (microsoft.com) another possibility, if anyone has outlook 2019, or an outlook365 account and have autodiscover working with that, if they can provide a copy of their working autodiscover.xml file (the links above contain info on finding this file) then we can compare it to the xml file returned by the automail plugin, see if they're any differences and work back from there.
It was wrong when i wrote i do not see any log for desktop. I was just irritated by the "OutlookMobileCloudService" thought its only the mobile one I get the following acess logs for desktop and mobile. This is the Desktop client logged by my apache autodiscovery server! Using a micorosft discovery network and a foreign IP to discover the email settings set in my desktop outlook client [24/Mar/2021:01:55:13 +0100] "GET /autodiscover/autodiscover.json?Email=**%40***.de&Protocol=ActiveSync&RedirectCount=1 HTTP/1.1" 404 5910 "-" "OutlookMobileCloudService-Autodetect/1.0.0" mobile [23/Mar/2021:22:05:46 +0100] "GET /autodiscover/autodiscover.js on?Email=***%40***.de&Protocol=ActiveSync&RedirectCount=1 HTTP/1.1" 404 5 884 "-" "OutlookMobileCloudService-Autodetect/1.0.0" ** - - [23/Mar/2021:22:05:46 +0100] "POST /autodiscover/autodiscover.x ml HTTP/1.1" 200 4323 "-" "-" The mobile app main domain do get the right mail settings at the end, the dekstop app doesnt.
I found some other users with basically the same problem https://www.reddit.com/r/exchangese...r_outlook_fails_to_retrieve_account/?sort=top I found out by using fiddler that outlook is talking to prod-global-autodetect.acompli.net:443 so maybe this is an explantion: https://masterandcmdr.com/2018/08/15/outlook-autodiscover-weirdness/ https://social.technet.microsoft.co...detectacomplinet?forum=onlineservicesexchange by enabling this registry key DisableOffice365SimplifiedAccountCreation the problem is ayctually gone. doesnt help me in the end though cannot force any user to put this key here some autodiscover functions of O365 and it differences to old version in german https://www.msxfaq.de/exchange/autodiscover/autodiscover_v2.htm
So what I think is actually happening please correct me if im wrong: Outlook 365 Simple Login doesnt autodiscover by itself it actually talks to prod-global-autodetect.acompli.net:443 which then tries to autodiscover. and either it fails cause of wrong cached records or the records are fine and it pops up as OutlookMobileCloudService-Autodetect in the server acesslog. it then gets the correct xml (as you can see with testconnectivity microsoft i.e.) but is not able to use this information by whatever reason. The only error you can see in the connectivity test is what is display in the linked reddit post " testresult status="Error" errorid="65e7befa-34fb-4039-9e2a-31e5fe2fcfe8" contentUrl="" testdescription="Autodiscover settings for Outlook connectivity are being validated." resultdescription="The Microsoft Connectivity Analyzer wasn't able to validate Outlook Autodiscover settings." additionaldetails="No account settings were returned from the Autodiscover response." elapsedMilliseconds="0">" not that helpful. and if you then just disable O365 Simple Login with this registry key it falls back to the old logic probably not using the outlook Mobile discovery and finds the configs correctly (proof pending)
i think that's only for outlook365 / microsoft hosted exchange. if outlook made connections/queries like that direct to microsoft to validate for autodiscover configuration for every self hosted exchange server and self-hosted/configured autodiscover workaround/equivalent then privacy activists and law_yers (can't believe the forum won't allow a post with that word in it) would be all over it.
what it looks like to me is that autodiscover v1 uses xml, and autodiscover v2 uses json so if we edit the automail script to return the data in json format instead of xml maybe it will just work... i don't know it older versions of outlook have been updated that they can also use autodiscover v2, probably the script will need to check the protocol version being used and use the current xml creation script for that, and a new json creation script for v2.
Does anyone know if a domain where the new autodiscovery works? Maybe on an Exchange server or other panel? Getting a working sample would be quite useful; maybe even necessary.
unfortunately, if soeone's using an exchange server, it doesn't look like their config will be helpful, the account types and protocol types are all completely diffferent: Code: <?xml version="1.0" encoding="utf-8"?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <User> <DisplayName>Info - Centre Maps</DisplayName> <LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (<-random->)/cn=Recipients/cn=<-random->-info_edf9b6</LegacyDN> <AutoDiscoverSMTPAddress>[email protected]</AutoDiscoverSMTPAddress> <DeploymentId><-random-></DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <MicrosoftOnline>True</MicrosoftOnline> <ConsumerMailbox>False</ConsumerMailbox> <Protocol Type="mapiHttp" Version="1"> <MailStore> <ExternalUrl>https://outlook.office365.com/mapi/emsmdb/?MailboxId=<-random->-<-random->-<-random->-<-random->@exampledomain.com</ExternalUrl> </MailStore> <AddressBook> <ExternalUrl>https://outlook.office365.com/mapi/nspi/?MailboxId=<-random->-<-random->-<-random->-<-random->@exampledomain.com</ExternalUrl> </AddressBook> </Protocol> <Protocol> <Type>WEB</Type> <Internal> <OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl> </Protocol> </Internal> <External> <OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/exampledomain.com/</OWAUrl> <Protocol> <Type>EXPR</Type> <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl> </Protocol> </External> </Protocol> <Protocol> <Type>EXHTTP</Type> <Server>outlook.office365.com</Server> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl> <EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl> <EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl> <SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl> <EcpUrl>https://outlook.office365.com/owa/</EcpUrl> <EcpUrl-um>?path=/options/callanswering</EcpUrl-um> <EcpUrl-aggr>?path=/options/connectedaccounts</EcpUrl-aggr> <EcpUrl-mt>options/ecp/PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=exampledomain.com</EcpUrl-mt> <EcpUrl-ret>?path=/options/retentionpolicies</EcpUrl-ret> <EcpUrl-sms>?path=/options/textmessaging</EcpUrl-sms> <EcpUrl-publish>?path=/options/calendarpublishing/id/<FldID></EcpUrl-publish> <EcpUrl-photo>?path=/options/myaccount/action/photo</EcpUrl-photo> <EcpUrl-connect>?path=/options/socialnetworks&ignore1=<Action>&ignore2=<Provider></EcpUrl-connect> <EcpUrl-tm>options/ecp/?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=exampledomain.com</EcpUrl-tm> <EcpUrl-tmCreating>options/ecp/?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=exampledomain.com</EcpUrl-tmCreating> <EcpUrl-tmEditing>options/ecp/?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=exampledomain.com</EcpUrl-tmEditing> <EcpUrl-extinstall>?path=/options/manageapps</EcpUrl-extinstall> <OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl> <UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl> <OABUrl>https://outlook.office365.com/OAB/<-random->-<-random->-<-random->-<-random->/</OABUrl> <ServerExclusiveConnect>On</ServerExclusiveConnect> </Protocol> </Account> </Response> </Autodiscover> i don't think any of the id's were dangerous to make public, but just in case i've changed all of them to <-random-> and changed the domain name as well. that said, whilst looking around, i did find this, Autodiscover information for mail clients to setup pop/imap/smtp settings automatically which was updated early last year, i've not tried it yet, or had a chance to compare it's autodiscover output to what @florian030's script creates, so it might be worth taking a closer look at.
another find suggests that additional srv records are (maybe all that's) needed: Code: _imap._tcp IN SRV 10 0 143 imap.my.server. _imaps._tcp IN SRV 0 0 993 imap.my.server. _pop3._tcp IN SRV 20 0 110 pop.my.server. _pop3s._tcp IN SRV 10 0 995 pop.my.server. _smtp._tcp IN SRV 10 0 25 smtp.my.server. _smtps._tcp IN SRV 0 0 465 smtp.my.server. _submission._tcp IN SRV 0 0 587 smtp.my.server. although that's untested so i can't confirm it works, i don't currently have access to outlook2019 or newer microsoft client to test with.
.htaccess automail plugin: <IfModule mod_rewrite.c> RewriteEngine on RewriteRule autodiscover\.xml$ /index.php [L] RewriteRule Autodiscover\.xml$ /index.php [L] RewriteRule config-v1\.1\.xml$ /index.php [L] </IfModule> <Files config.php> Deny from All </Files> .htaccess of your link RewriteEngine On RewriteCond %{REQUEST_FILENAME} -s [OR] RewriteCond %{REQUEST_FILENAME} -l [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^.*$ - [NC,L] RewriteRule ^.*$ autodiscover.php [NC,L] XML of automailplugin <?xml version="1.0" encoding="UTF-8"?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <SSL>on</SSL> <Type>IMAP</Type> <LoginName>***@**.de</LoginName> <Server>fqh***</Server> <Port>993</Port> <SPA>on</SPA> <AuthRequired>on</AuthRequired> <DomainRequired>on</DomainRequired> </Protocol> <Protocol> <SSL>on</SSL> <Type>POP3</Type> <LoginName>***</LoginName> <Server>FQH**</Server> <Port>995</Port> <SPA>on</SPA> <AuthRequired>on</AuthRequired> <DomainRequired>on</DomainRequired> </Protocol> <Protocol> <UsePOPAuth>on</UsePOPAuth> <SSL>off</SSL> <Encryption>TLS</Encryption> <Type>SMTP</Type> <LoginName>***</LoginName> <Server>***</Server> <Port>587</Port> <SPA>on</SPA> <AuthRequired>on</AuthRequired> <DomainRequired>on</DomainRequired> </Protocol> </Account> </Response> </Autodiscover> Differences to you link: SPA off vs on AND Domain Required off vs on
