Discussion in 'Plugins/Modules/Addons' started by Trimilur, Mar 22, 2021.
they are already set in my case
One of my problems is also that with outlook simple login on desktop and sara and fiddler i only see a log for prod-global-autodetect.acompli.net:443. not my server directly.
AND YES another client NOT my personal computer or network is then trying to autodiscover with the ID "OutlookMobileCloudService-Autodetect/1.0.0 and this is NOT my IP
this is my log entry tried with the email [email protected]*** from my desktop!
220.127.116.11 - - [24/Mar/2021:17:28:25 +0100] "GET /autodiscover/autodiscover.json?Email=tes2%40***.de&Protocol=ActiveSync&RedirectCount=1 HTTP/1.1" 200 3992 "-" "OutlookMobileCloudService-Autodetect/1.0.0"
as soon as i disable the simple login i get the follwing log:
"POST /autodiscover/autodiscover.xml HTTP/2.0" 200 1447 "-" "Microsoft Office/16.0 (Windows NT 10.0; Microsoft Outlook 16.0.13801; Pro)" with my private IP
the mobile client tries to discover a .json file
"GET /autodiscover/autodiscover.json?Email=***%40**.de&Protocol=ActiveSync&RedirectCount=1 HTTP/1.1" 200 3992 "-" "OutlookMobileCloudService-Autodetect/1.0.0"
i think the simple login setting is an hangover from a previous config. it's supposed to be for connecting to an outlook365 account.
and prod-global-autodetect.acompli.net:443 is microsofts server, used for mobile activesync
what do you mean with hangover? ive never had installed outlook before and got the problems from the first install. i actually think that microsofts simple login natively tries to do all the autodiscovery using their servers. but this is only a secondary problem cause even if the autodiscovery is not done directly by outlook but by the Microsft OutlookMobileService on prod-global-autodetect.acompli.net:443 it doesnt help about the propblem with autodiscovery itself. i think it will work if we just create a valid json answer based on
what will now circle us back to the situation of really actually needing a working config from some mailserver/autodiscovery
That DA article is based on my two threads https://forum.directadmin.com/threads/guide-for-autodiscover.58483/ and https://forum.directadmin.com/threads/thunderbird-autoconfiguration.58378/ and the auto discover solution there is a dead end.
I experience a similar issue. But discovered that my installation worked if I manually replace the Email parameter with email.
Have you tried doing such a request manually with a small e in email?
I know it does not solve the issue completely but it perhaps clarifies one of the problems.
@Timilur the "Outlook Mobile Hybrid Modern Authentication Test" from testconnectivity.microsoft.com confirms your shown request
I would like to have a working solution, too. However, as far as I understood, autodiscover v2 does not support imap as protocol. So, this only makes sense if your server can talk activesync..
Somehow the mailcow people got something running, but again only for activesync protocol: https://github.com/mailcow/mailcow-dockerized/blob/master/data/web/autodiscover-json.php
(see https://github.com/mailcow/mailcow-dockerized/blob/master/data/web/inc/vars.inc.php for autodiscover settings)
That means you would probably have to run z-push which also brings autodiscover functionality. However, I have no users that really require this and the effort is much more than the time saved
If someone got z-push working, let me know. We kind of need this for our customers...
it's old, and i've never tried it....
The Perfect Push Mail Server - Debian Squeeze (Debian 6.0) With ISPConfig 3 & Z-push (howtoforge.com)
Separate names with a comma.