Clear cache for autodiscover endpoint acompli.net for domains

Question

Hello,

I am part of a hosting company, we are trying to troubleshoot an issue regarding auto configuration of Outlook when certain domains are used. We've seen similar forum posts like the situation we have, and have narrowed it down to Outlook using its own server to pull settings for the email account being configured (prod-global-autodetect.accompli.net).

We currently have two domains that has this issue, but it could potentially be more than just these two, as this issue was reported by the clients trying to use their mail service with their hosting.

Domains are turbologic.ro and yoursoftalternative.com

Recreating the issue is very simple, open an Outlook and try to configure an email for any of these two. When using turbologic.ro, if you use any@turbologic.ro in Outlook, it asks you to login to Gmail to sync/configure, but their email service is not with Gmail (autoconfiguration settings being pulled are not from the hosting server, but from prod-global-autodetect.accompli.net).

If you use any@yoursoftalternative.com, then the configuration pulls some imap.1und1.de which again is not the actual server settings (settings being pulled from prod-global-autodetect.accompli.net).

We confirmed this by using Fiddler and watching the requests being made to prod-global-autodetect.accompli.net, screenshot attached.

This can also be verified using curl from command line, like this:

curl "https://prod-global-autodetect.acompli.net/autodetect/detect?services=office365,outlook,yahoo,google,icloud&protocols=eas,imap,smtp,rest-cloud" -H "X-Email: any@turbologic.ro"

Reply was:

{"email":"any@turbologic.ro","services":[{"service":"google"}],"protocols":[{"protocol":"imap","hostname":"imap.gmail.com","port":993,"encryption":"ssl","username":"any@turbologic.ro","validated":false},{"protocol":"smtp","hostname":"smtp.gmail.com","port":465,"encryption":"ssl","username":"any@turbologic.ro","validated":false}]}

How can we clear or refresh the settings acompli.net offers? We do not have control over client devices to be able to fix it from their side.

Answer 1

Dear @Valentin Iulian
I'm seeing this issue all the times for years (!!!) now. And it just happened to me again the last week. And as far as I can see there still is no real resolution to it or explanation on how this happens in the first place. I have an existing customer with Exchange 2019 on-premise, utilizing Android Smartphones for accessing their mailboxes via Outlook App. All of a sudden it stopped working and setting up the Outlook App with a new account isn't possible any more. Autodiscover completely broke. This really is a pain in the a$$.
@Microsoft: do something! This is definitely not an DNS issue. It's all down to this maleficent acompli.net cache crap. Opening a support ticket with Microsoft will result in an endless stream of stupid questions and a lot of precious time lost on both sides. Not to mention customers who don't understand such issues from a technical point of view and get really pissed at us consultants for "not being competent" though it isn't our fault at all. It's called "Autodetect" feature, you can read more about it all over the internet.

Answer 2

I'm afraid this will not clear the cache. Can often be solved in Outlook client， There are several common methods that can be solved in the Outlook client: log out several times, repair office, SaRA, and create a new configuration file. I think it is necessary to make out an invoice to solve complicated problems.

Answer 3

I have a fix.

This is a long-standing issue with the acompli.net outlookmobile.com Mobile Outlook acquisition years ago. Microsoft has never fixed it. It overrides Autodetect because it's a holdover from that acquisition creating frustrating issues, especially if you have migrated from Google Workspace or some other platform to Microsoft Exchange or 365.

You can confirm that this is happening easily. Just put in the following command into Powershell, and substitute your own domain name where indicated:

Invoke-WebRequest -Uri 'https://prod-autodetect.outlookmobile.com/detect?services=office365,outlook,google,icloud,yahoo&protocols=rest-cloud,rest-outlook,rest-office365,eas,imap,smtp' -Headers @{'x-email'="EMAIL@DOMAIN.COM"} | ConvertFrom-Json

It will report back what Outlook will by default try to use--either the Autodiscovered system, or the cached entry from acompli.net.

The only ways to resolve it that I have found are the following:

• First option, wait it out. The caches at acompli.net will eventually clear. Weeks later. Not cool, Microsoft.
• Second option, immediate gratification: Edit the hosts file on the computer in c:\windows\system32\drivers\etc and add 127.0.0.1 prod-global-autodetect-acompli.net to the end of the text file. (Do this in an elevated command prompt.) This will prevent Outlook from being able to contact this out-of-date cache on this server. Autodiscover will do the rest. (NOTE: You can also put this into your DNS server if you use one!)
• Third option, immediate gratification: For mobile devices running the Outlook app, go ahead let the Google sign in come up while adding the account, but immediately click "DONE" at the top left and you will then see the option to do a manual setup. Choose Office 365 for the type of account and put in the credentials. (You may be prompted to authenticate so put the Microsoft Authenticator onto the phone ahead of time.)

Answer 4

Any updates? Can we reach someone that can talk with anyone managing acompli.net?

Answer 5

It has nothing to do with Gmail/Google, my client does not have anything to do with them, they are hosted on a Linux server with cPanel.

Yes, there are more domains with this problem, we have listed two we know of (turbologic.ro, yoursoftalternative.com).

No, if google login pops up, details dont work, obviously, because they dont have any service with them.

I believe you're not seeing the entire picture here. The problem is not on my clients side, but on outlook software side when they fetch info from acompli.net.