• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Plesk AutoDiscover working but Outlook does not recognize the settings

vaelu

Basic Pleskian
Hello Pleskians

We are already into this AutoDiscover topic for a long time. Two years ago we created our own AutoDiscover config for our customers because they were in need of it and Plesk did not have this feature back then.
Then we have worked with the Plesk developers side a side when the feature was developed and I'm really happy to see that the feature is now stable and working, since it was not properly working in the first version of Plesk AutoDiscover.

We have set up 3 different VMs to test the behavior:
  • Outlook 2013
  • Outlook 2016
  • Outlook 2019/365
Since all our customers are using the same domain as mailserver and not their own domain, we had to change the incoming and outgoing server for AutoDiscover. We did this first with a script which replaces the template files in /opt/psa/admin/htdocs/mailconfig after every update. Now it is possible to change these settings via Panel.ini (explained here) and that's pretty cool.

Unfortunately there is still not everything working, but I personally think that the problem is on Microsoft's side. I'm posting this that we can start a discussion about the AutoDiscover behavior with IMAP servers in Outlook hosted with Plesk.

How I've already written above, our customers are using a unified domain for the mailserver. That means when customer XYZ with domain customer.xyz has the email [email protected] the correct mail settings for him would be the following in our case:
  • Incoming mailserver: mail.ourdomain.tld
  • Incoming port: 993
  • Incoming protocol: SSL/TLS
  • Outgoing mailserver: mail.ourdomain.tld
  • Outgoing port: 465
  • Outgoing protocol: SSL/TLS
  • Username: [email protected]
Now we noticed the following behaviour:
On Outlook 2016 and newer (with the new account setup prompt - this one: Screenshot), Outlook does not even try to retrieve the settings. So no request is made to https://customer.xyz/autodiscover/autodiscover.xml and Outlook directly asks what type of mailbox it is. After selecting "IMAP" it asks for the mailserver, port and protocol.
Screenshot_2.png
This behavior is not really cool for our customers, since they then need to type all server settings in manually.

When checking the AutoDiscover settings for this domain, it does work perfectly. We have checked it with a POST request here and also with the Outlook AutoDiscover testing tool.
Screenshot_1.png
(Translation: Successful)

Does anyone know more about this? I hope I can start a good discussion here about AutoDiscover.
 
Last edited:
I do bump this, because I think it would be very interesting for everyone to discuss.
 
Back
Top