Applicable to:
- Plesk Obsidian for Linux
Question
How to enable / manage / verify mail autodiscover functionality in Plesk Obsidian?
Answer
Warning: Outlook 2016/2019/Office 365 supports autodiscover for IMAP/SMTP protocols starting with Plesk Obsidian 18.0.25.
-
Go to Tools & Settings > Mail Server Settings > Settings tab > General options > Enable the Enable mail autodiscover option:
Note: if the option is not visible it means that Plesk Premium Email is installed, which has its own autodiscovery mechanism [BUG] Mail autodiscover option is not visible in Mail Server Settings
-
If Nginx is not installed on the server, go to Tools & Settings > Apache Web server > Enable the proxy_http module > Click OK to apply the changes
-
(Optional) in Plesk > Tools & Settings > Mail Server Settings enter domain name in "Specify a custom domain name for mail autodiscover" field.
-
Manage the mail autodiscover at Domain or Service Plan level:
5.1- Go to Domains > example.com > Mail Settings tab > Enable the option Enable mail autodiscover > Click OK to enable the mail autodiscover for the domain:
5.1- Go to Service Plans > Service Plan Name > Permissions tab > click Show more permissions > Enable the Mail autodiscover management option > Click on Update & Sync to grant permissions to a subscription owner to enable or disable the mail autodiscover:
5.2- Go to Service Plans > Service Plan Name > Mail tab > Enable the option Enable mail autodiscover > Click on Update & Sync to enable the mail autodiscover for all the subscriptions synchronized with the service plan:
6. Install a valid SSL certificate in the domain
7. (Optional) Verify if the mail autodiscover is available for the different mail clients:
7.1- Create XML file customizing the EMailAddress parameter:
# cat request.xml
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/mobilesync/requestschema/2006">
<Request>
<EMailAddress>jdoe@example.com</EMailAddress>
<AcceptableResponseSchema>
http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006
</AcceptableResponseSchema>
</Request>
</Autodiscover>
7.2- Perform a POST request with the file request.xml to the URL https://<domain-name>/autodiscover/autodiscover.xml and the sever will return the following response:
Warning: If the following command fails with certificate subject name
does not match target host name make sure to install a valid SSL on the domain
# curl -d @request.xml -u jdoe@example.com https://example.com/autodiscover/autodiscover.xml
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>jdoe@example.com</DisplayName>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>IMAP</Type>
<Server>example.com</Server>
<Port>993</Port>
<DomainRequired>off</DomainRequired>
<SPA>off</SPA>
<SSL>on</SSL>
<AuthRequired>on</AuthRequired>
<LoginName>jdoe@example.com</LoginName>
</Protocol>
<Protocol>
...
</Protocol>
</Account>
</Response>
</Autodiscover>
7.1 - Perform a GET request customizing the emailaddress parameter to the URL https://<domain-name>/mail/config-v1.1.xml?emailaddress=<email-address> and the sever will return the following response:
Warning: If the following command fails with certificate subject name
does not match target host name make sure to install a valid SSL on the domain
# curl https://example.com/mail/config-v1.1.xml?emailaddress=jdoe@example.com
<clientConfig version="1.1">
<emailProvider id="example.com">
<domain>example.com</domain>
<displayName>jdoe@example.com</displayName>
<displayShortName>jdoe@example.com</displayShortName>
<incomingServer type="imap">
<hostname>example.com</hostname>
<port>993</port>
<socketType>SSL</socketType>
<authentication>password-cleartext</authentication>
<username>jdoe@example.com</username>
</incomingServer>
<outgoingServer type="smtp">
<hostname>example.com</hostname>
<port>465</port>
<socketType>SSL</socketType>
<authentication>password-cleartext</authentication>
<username>jdoe@example.com</username>
</outgoingServer>
<incomingServer type="pop3">
<hostname>example.com</hostname>
<port>995</port>
<socketType>SSL</socketType>
<authentication>password-cleartext</authentication>
<username>jdoe@example.com</username>
</incomingServer>
</emailProvider>
</clientConfig>
Note: If DNS is managed externally it will be needed to create SRV records manually there:
CONFIG_TEXT: _imaps._tcp.example.com. SRV 10 10 993 mail.example.com.
_pop3s._tcp.example.com. SRV 10 10 995 mail.example.com.
_smtps._tcp.example.com. SRV 10 10 465 mail.example.com.
Additional information
Check the following table for details on how the feature works depending on the checkboxes enabled/disabled:
| Permissions > Mail autodiscover management | Mail > Enable mail autodiscover | For new domains | For existing domains |
|---|---|---|---|
| Enabled | Disabled |
|
|
| Disabled | Enabled |
|
|
| Disabled | Disabled |
|
|
Comments
64 comments
I agree with Dennis Scheidner 100%. You should be able to set a the mailserver (server hostname) name for the customers by default.
In our case we would use: ns1.servername.tld. That is the easiest for all customers.
Anyways, I am now testing various auto solutions; which actually do work with iOS, Outlook and Thunderbird. Hopefully it will work.
"Warning: Outlook 2016/2019/Office 365 does not support autodiscover for IMAP/SMTP protocols."
LOL. That means that the autodiscover function is worthless in general.
I think it's best that we will start forwarding all support tickets we receive directly to Plesk for email settings instead.
Let's see how Plesk likes that. Maybe it "push" them to come up with a working solution like DirectAdmin.
@Andre, this case is too complex to investigate by comments in article. Since key purchased from partner, you should reach them for a support. Thought you can get a support subscription, which is free for first month to reach us directly: https://support.plesk.com/hc/en-us/articles/213953025
Hello,
I read this technical report but I don't understand if is necessary to change the DNS for "autodiscover" and "autoconfig" records or just "enable mail autodiscover" for each domain in the Plesk control panel.
Is necessary to add manually these two new records "A"?
autodiscover A IP-server
autoconfig A IP-server
Also, how can I change the parameters that the email clients set automatically?
E.g. How can I change the "autodiscover" instruction sent to the email client for the port 25 with 587?
I think that is the file "config-v1.1.xml" to edit but where can I found this xml file?
https://<domain>/mail/config-v1.1.xml?emailaddress=<email>
If I open it on the browser I can see the configuration details about the single email, but if I connect by ftp, in the <domain> folder I can't see/found the folder "mail/".
Where is this file? Is possibile change the values?
Thanks!
Hi Michele,
Autodiscover does not make use of DNS such records (autodiscover or autoconfig) because the mail client does an HTTP request on the webserver to get the autodiscover.xml.
For now it's not possible to modify the autodiscover answer from Plesk, and if done directly in the file it's highly possible that the changes will be reverted back on further Plesk updates.
For that, we have this feature request: Change settings for mail autodiscover
Thanks Francisco for the answer.
At least is possibile to change the values for "ports" and "authentication" in the xml file generated automatically for every domain?
https://<domain>/mail/config-v1.1.xml?emailaddress=<email>
Now autodiscover is meaningless because it provides wrong values.
See this post on the forum for more information about what I mean:
https://talk.plesk.com/threads/how-can-i-change-the-default-mail-autodiscover-parameters.355252/
Can anybody point me in the right direction to have this working ? The autoconfigure on each domain points to something like this:
https://<yourdomain>.be/email.mobileconfig?emailaddress=<name>@<yourdomain>.be
But it links to a 404 page on my domain, which has wordpress installed. I use nginx whithout Apache . How can we fix this so it works.. I need to take care of this for my Clients (and me...), they are super confused with email setup..
I have a paid plesk obsidian unlimited account..
@all
Thanks for all your kind answers. I need only two more answer now.
FIRST: in the panel-ini setting a domain can be set and in the general mailserver settings (due to my hoster set it in panel.ini ONLY for One domain of ONE client on the server, I wonder something) so, two spots are available.
In case I SOLELY want to use the application settings mask in plesk under: ...:8443/plesk/server/mail/ then I need to put in panel.ini back to <domain> placeholder (is IT a Placeholder at all?) yes or no?
SECOND: And my main problem exists still, although the general setup should work now, I want to NOT use only ONE domain for all autodiscover in one server.... I set each account up on inwx.de domain provider to use their own domain, customer domain, to be the MX- record, like Customer1 has domain dom1.com, then the mx will be mail.dom1.com and further customer 2 has domain name: dom2.de, so MX will be mail.dom2.de and customer 3 likewise will have dom3.biz as domain and needs mail.dom3.biz as MX .... then I will need any placeholder stuff to reflect the autodiscover to take only the connected CUSTOMER domain used in domain under a customer account, anything like mail.CHOSEN-CUSTOMER-DOMAIN.com
How can I set this "Wildcard" domain name up as autodiscover functionality.... ? I imagine anything like: "...Specify a custom domain name for mail autodiscover": mail.<wildcard>.*
:D
Please, and if not existing, then please activate, cause for many guys, NOT running all in one, DNS, custom hosting and NOT only ONE client pr VPS or some and not wanting to use the panel.ini , where description is also lacking.
Hello Michele
These settings are also to be available for change only after functionality from https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/38914795-change-settings-for-mail-autodiscover will be added.
Thank you for your feedback. Our RnD team will continue working on improving this functionality.
Hello Koray Snoray
Could you submit a request to Plesk Support? Additional testing and investigation will be required.
Depending on where the license was purchased, the request is to be submitted to us or to our reseller: https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-
"Warning: Outlook 2016/2019/Office 365 does not support autodiscover for IMAP/SMTP protocols."
According to the following Technet article, Outlook *does* support autodiscover. Just not the way it was implemented by Plesk so far but follows an RFC instead.
Just back from holiday so didn't have time to test myself yet.
https://social.technet.microsoft.com/Forums/office/en-US/daa5fd1f-883e-4ca9-8ebc-3b25576ced28/autodiscover-for-imap-account-on-outlook-20162019
Hello Andre,
The questions addressed require additional details and further investigation. Articles comments are not the place to checking such complicated issues due to this, please, submit request to support team. We will be more then glad to guide you through:
https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-
TomBob
100% true. Even in DirectAdmin autodiscover works flawlessly.
Similar thing with the latest Roundcube version along with the Elastic skin. With Plesk it's only supported when you "purchase" Kolab.
Then you can use the newest Roundcube version with Elastic skin. Luckily someone (Reboot) on the forums posted an alternative method to get this working.
It saddens me really that Plesk is going a little downhill the past year. Oh well. We will see where it ends and let's hope they / things improve! ;-)
Hi, thanks for this great feature
Is there any command line for the per-domain GUI setting "Enable mail autodiscover" ?
I've been searching for it using "plesk bin subscription" but didn't found it
Thank you
--
Edit : Found it !
plesk bin subscription --update <domain> -mail_autodiscover <true|false>
Hello @Benoit Oua
Glad to hear the command is found.
Info: Outlook has switched off autodiscover for IMAP and POP3 after the release of 16.0.6741.2017, so it does not look for errors on the server, it only looks at Outlook.
Hello Gjimi
Indeed since the version 16.0.6741.2017 Outlook connects Outlook directly to Office 365 if Autodiscover is not working.
More information may be found here:
https://www.gothamweb.com/portal/index.php/knowledgebase/8/Outlook-bypasses-AutoDiscover-and-connects-directly-to-Office-365-mailbox.html?language=german
https://help.bittitan.com/hc/en-us/articles/360005041333
In general, the instruction from this article is actual.
I have no option "Enable mail autodiscover" on one Plesk Server. Version of Plesk is latest 18.0.27.
What can I do to enable autodiscover?
Regards,D.
Hello Davor Guttierrez
Please, check this article: https://support.plesk.com/hc/en-us/articles/360011212119
Hello. How to disable via CLI for server ?
Hello Boss it can be done as below:
Still waiting to see auto-configuration working on Microsoft Outlook 365 with the latest Plesk.
So far each time I am told it works I have not seen it happen.
Manually works fine, in most cases.
In some cases, there is a client-side issue where I have seen 1 computer on a network have no issue with a customer's domain name as the SMTP and IMAP Server Hostname, while a 2nd computer on the same network will only work with the domain from the host of the server itself.
Autodiscover does not work for iOS and Apple Mail (macOS), only when using a profile via Plesk (scan QR code or click link). Are there any plans to implement Autodiscover for iOS and Apple Mail in future? The release notes said "Support for Apple Mail coming soon!" https://docs.plesk.com/release-notes/obsidian/whats-new/
Did anyone manage to get Autodiscover working with the latest Outlook version and the new "Simplified Account Creation"? For me it only works when using the "classic" account setup. Some people say it was changed by Microsoft and won't work with IMAP accounts anymore, others say it still works with DirectAdmin for example.
Hello Richard Anthony Secor
Additional investigation is required.
So, you did it right to submit a support request.
Please, expect an update in a ticket.
Autodiscover is compatible with iOS devices ? I don't find any doc that specify compatible clients. I've test with outlook (desktop and app), thunderbird, successfully.
I just enabled Autodiscover. However I detected that the response I get is lacking the <xml ...> that other providers send first in the response. Can it be that this causes issues?
Details:
curl -i https://<mydomain>/autodiscover/autodiscover.xml --data @- -H "Content-Type: text/xml" <<-EOF
<?xml version="1.0" encoding="utf-8" ?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
<Request>
<EMailAddress>test@<mydomain></EMailAddress>
<AcceptableResponseSchema>
http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a
</AcceptableResponseSchema>
</Request>
</Autodiscover>
EOF
Outlook 365 is NOT accepting the auto discover but is asking the details of the connection.
Also checking at Microsoft https://testconnectivity.microsoft.com failed, it reported "NULL response received from auto discover request"
Simon Autodiscover for Apply Mail currently works. If it still does not work in your case, please create a support request.
Stefan Schallenberg response is required for mail server to be able to configure account. Please double check using article steps all is enabled. If still does not work please create a support request.
Autodiscover for Apple Mail works, but only via Profile download in Plesk. It does not automatically find the settings if you add an account manually in Apple Mail. You can also check on https://support.apple.com/mail-settings-lookup - Apple seems to be using its own autodiscover list, which only works for big providers like Gmail, Hotmail, etc.
Another question: When I enable the option "Enable mail autodiscover" in a service plan and then synchronize with "Update & Sync", it does not enable Autodiscover for existing domains which had the option disabled before (updated from Plesk Onyx). Why is this?
"Enable mail autodiscover" should be disabled when the mail service of a domain gets disabled, right?
Please sign in to leave a comment.