Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please Help? Doesnt work on Office(Outlook) 365 #2

Open
wolvyreen opened this issue Mar 17, 2022 · 3 comments
Open

Please Help? Doesnt work on Office(Outlook) 365 #2

wolvyreen opened this issue Mar 17, 2022 · 3 comments

Comments

@wolvyreen
Copy link

Firstly, thank you for your effort but as the title says, It isn't working on Office(Outlook) 365.

I have create the DNS records as instructed in your guide as shown here:

https://mxtoolbox.com/SuperTool.aspx?action=srv%3a_autodiscover._tcp.theconfidenceco.co.za&run=toolpage

I have also placed the necessary xml file(index.php) in the correct location as seen in this screenshot below:
xml_file_output

However, Outlook still doesn't manage to autodiscover the settings correctly as shown here:
outlook_step_1
outlook_step_2
outlook_step_3

Is this not meant to work with modern outlook versions?

@axoroll7
Copy link

axoroll7 commented Apr 21, 2022

Edit : I am not affiliated with the creator of this repository.

Outlook 2016+ PC/MAC doesn't work, but the "test email autoconfiguration" in Outlook works.

Have you installed Outlook 2016+ PC/MAC from Office 365 ? The simplified account creation of the newer version of Outlook could not work with some email providers in certain circumstances. To use Outlook 2016+ PC/MAC downloaded from Office 365, you must disable the "Office 365 Simplified Account Creation", thanks to this .reg script:

Windows Registry Editor Version 5.00

; REMOVE Office 365 Simplified Account Creation

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Setup]
"DisableOffice365SimplifiedAccountCreation"=dword:00000001

And this .reg to script to revert the change made from the previous script:

Windows Registry Editor Version 5.00

; ADD Office 365 Simplified Account Creation

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Setup]
"DisableOffice365SimplifiedAccountCreation"=dword:00000000

If you don't want to frighten your customer, you can hide the .reg scripts in a .exe file (but don't forget to add in the "Compatibility" tab: "Run As Administrator"). You can elaborate and say that Outlook is at fault, and show him the google search about how to uninstall the simplified account creation.

Ressources:

https://docs.deeztek.com/books/hosted/page/configure-outlook-for-hosted-mail-using-activesync

⚠️ If you installed Outlook 2016, Outlook 2019 or Outlook for Office 365 from Office 365 (i.e. downloaded and installed from Office 365), please be advised that those versions of Outlook have an issue with autodiscover. Because of this, you must first disable the Simplified Account Creation wizard in order to setup your mailbox with our Hosted Mail.

Alternatively, you can download and import the disable_simplified_account_creation_wizard.reg to your computer.

@axoroll7
Copy link

axoroll7 commented Apr 22, 2022

@wolvyreen

I didn't quoted your username in my last comment. I don't know how Github works, but maybe this will trigger a notification.

Edit:

Some explications : The "Office 365 Simplified Account Creation" "doesn't perform autodiscover look-ups". The server "acompli.net" looks up your MX records to get the IP addresses, guess your configuration from them (reverse-DNS), store the configuration in a cache, and serve everytime the same cache at the "Office 365 Simplified Account Creation". This configuration can fail in numerous situations. This guy explains the problem, and how you can resolve it (spy the outgoing connection of the Outlook App, use the acquired schema to show the cache yourself anytime you want, disable the Office365SAC locally, clear your DNS zone, ask gently Microsoft to clear the cache, and wait for the cache to be cleared) : https://masterandcmdr.com/2018/08/15/outlook-autodiscover-weirdness/

If you use a mutualized email provider with multiple possible configurations, your chances are small. Some examples :

OVH : ssl0.ovh.net / pro1.mail.ovh.net
Zoho Mail : imap.zoho.eu / imappro.zoho.eu

williamdes added a commit to wdes/mail-autodiscover-autoconfig that referenced this issue Aug 20, 2022
@williamdes
Copy link

Thank you @axoroll7 !!!
You made my end of day happy, the regedit patch works !
I was now able to add Outlook 2021 to my auto-discovery project referencing this issue: https://github.com/wdes/mail-autodiscover-autoconfig

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants