How to manage mail autodiscover in Plesk Obsidian?

Anastasia Zyrianova

Updated October 05, 2021 20:29

kb: bug ABT: Group B Plesk Obsidian for Linux

Applicable to:

Plesk Obsidian for Linux

Question

How to manage mail autodiscover in Plesk?

Answer

Autodiscover is enabled by default on all new Plesk Obsidian installations for all domains.

For Plesk upgraded to Obsidian from previous versions

Log in to Plesk GUI.
Go to Tools & Settings > Mail Server Settings > Settings tab > General options > Enable the Enable mail autodiscover option.
Next, enable it for the particular domain:
- - Enable it under Domains > example.com > Mail Settings. Activate option Enable mail autodiscover
  - If you need to enable autodiscover for all domains follow the article #360012848199
A valid SSL certificate is required. Make sure you have one assigned under Mail Settings tab or issue it using "SSL It" including option "Assign the certificate to mail domain".

This step is required only if you create DNS records directly under registrar and not in Plesk. Create SRV records manually under DNS registrar:

Record type	Domain name	Service	Protocol	Port	Target
SRV	example.com	_smtps	tcp	465	example.com
SRV	example.com	_imaps	tcp	993	example.com
SRV	example.com	_pop3s	tcp	995	example.com

Limitations

Currently, autodiscover is not compatible with the latest Outlook version 2019 and O365. These mail clients use Microsoft proxy servers for autodiscover requests, and this configuration is not is supported in Plesk.
When a custom mail server is configured in Tools & Settings > Mail Server Settings, settings may not be obtained by some applications on Android devices. It depends on the method used by an application to fetch mail settings using autodiscover.

The corresponding request https://jira.plesk.ru/browse/PPPM-13140 was created to address this.
Not available for domains without hosting
Domain should be secured with valid SSL/TLS certificate.
Plesk does not use "mail.example.com" or "imap.example.com". It uses domain name itself like "example.com" as SMTP/IMAP hostname for automatic configuration.
Plesk Premium Email has its own features for automatic configuration, it disables autodiscover by Plesk if installed.

Troubleshooting

Verify that server generates correctly configuration for mail clients

Open tool to run curl commands online
Insert the below string, replace "example.com" with your domain name and "admin@example.com" with mailbox name which exists, then click "Run".

# curl https://example.com/mail/config-v1.1.xml?emailaddress=admin@example.com
If content section is not empty and contains hostnames, ports means that server generates configuration correctly.

Verify that SSL certificates are correct

Open online SSL Checker tool.
Test SMTPs specifying your website name and smtps port:

CONFIG_TEXT: example.com:465
Next test IMAPs using website name and imaps port:

CONFIG_TEXT: example.com:993
If there is an error about invalid certificate is shown double check domain mail settings using article #115001446174

Comments

64 comments

Alexander Koch November 07, 2019 16:11

Ok that sounds pretty nice, but what i have to change in DNS or so if the plesk server isnt my DNS Server.

Do i have to make subdomains like autodiscover.domain.tld and autoconfig.domain.tld and give them a A-Record to my Plesk Server, or how that all work?

greetz Alex

1

Comment actions Permalink
Anton Maslov November 08, 2019 00:06

Hi Alexander, should work right away after you enable it basically, because Outlook and Thunderbird do requests to URLs like https://<domain>/autodiscover/autodiscover.xml and https://<domain>/mail/config-v1.1.xml?emailaddress=<address. Means you don't need record autodiscover.domain.tld, you just need your A record for domain.tld

0

Comment actions Permalink
TomBob November 27, 2019 21:46

Obsidian 18.021 #3

Thunderbird works perfect

Outlook 2016 doesn't

Android 5.1.1 doesn't

Will test further in the next few days. Running the tests as above to verify show the correct result. Done some research, but couldn't find a reason. Any pointers?

0

Comment actions Permalink
Ivan Postnikov November 29, 2019 12:33

Hello,

Parahoster / Thibaut Robert

Could you, please, provide more information about what you're trying to achieve so that we could make sure that the answer is precise?

TomBob

Are there any errors displayed in Outlook or Android mail client? Also, it's worth checking /var/log/maillog

0

Comment actions Permalink
Parahoster / Thibaut Robert December 02, 2019 15:59

Hey Ivan Postnikov,

Yeah no problem.

For exemple.

One of my client use his domaine : www.exemple.com and when he try to configure by his mail software (like outlook). The discover show info like this

Input : exemple.com:993

Output : exemple.com:465

But I need to customize this data for using my correct server certificat as : myserver.com:465 ans myserver.com:993

Where Can I change this parameter of the autodiscover ?

Thanks

0

Comment actions Permalink

Michael December 05, 2019 09:16

Hi Ivan,

I have the same problem. I installed Plesk yesterday using the one-click-installer on a Ubuntu 18.04 server. The problem is the Preferred domain setting. I added my domain e.g. "example.com" and set the preferred domain to: www.example.com. When executing the GET request like Thunderbird does, I noticed the following response chain:

Redirect (0.090s) - https://example.com/mail/config-v1.1.xml?emailaddress=info@example.com

Server: nginx
Date: Thu, 05 Dec 2019 09:03:04 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://www.example.com/mail/config-v1.1.xml?emailaddress=info@example.com
X-Powered-By: PleskLin

-------------------------------------

Response (0.077s, total time 0.126s) - https://www.example.com/mail/config-v1.1.xml?emailaddress=info@example.com

<clientConfig version="1.1">
    <emailProvider id="example.com">
....
    </emailProvider>
</clientConfig>

When I execute the POST request, my first response is again the redirect to "www.example.com" but the second response is: 400 - Bad Request.

If I change the preferred domain to "none" it's working.

Ivan Postnikov December 10, 2019 10:13
Hello Parahoster / Thibaut Robert

As I can see, you've already submitted a ticket to us to check this in detail.

Here's the reply from our agent:

In order to change default parameters, you should edit the file which the mail client requests during the process.

The file is different for thunderbird or Outlook.
- Outlook sends a POST HTTP request (example) to https://<domain>/autodiscover/autodiscover.xml
- Thunderbird sends a GET HTTP request to https://<domain>/mail/config-v1.1.xml?emailaddress=<address> or https://<domain>/.well-known/autoconfig/mail/config-v1.1.xml?emailaddress=<address>
On this page you have examples containing the same information: How to manage mail autodiscover in Plesk Obsidian?

In case of additional issues/questions, feel free to reply back to the ticket.
0

Comment actions Permalink
Dennis Scheidner December 13, 2019 11:30

I've got the same problem, but the answer from the agent is not the solution:

The autodiscover will send <domainname> as mailserver to the emailclient.
But, in our case <domainname> is not the correct mailserver.
For all domains on this plesk-installation it has to be mailserver.mycompany.de

How can I change the mailserver send to the mailclient using autodiscover?

1

Comment actions Permalink
Alexey Lapshin December 19, 2019 01:54

Hello, @Michael. To avoid any misunderstandings and to reproduce the the exact issue you reported, please submit a ticket to Plesk Support https://support.plesk.com/hc/en-us and provide POST requests you are perform to reach "400 - Bad Request" as the output in the response.

0

Comment actions Permalink
Alexey Lapshin December 19, 2019 03:28

Hello @Dennis, I have to inform you that Plesk Mail autodiscovery feature relies on domain name and not to server hostname, and this is cannot be changed.
Since in Plesk Obsidian SNI support is available now, it is possible to assign different SSL certificates to domains on a local mail servers. So if the certificate will be installed, there will be no warnings about insecure connection during setting up mail-client. https://support.plesk.com/hc/en-us/articles/115001446174-How-to-secure-a-Plesk-mail-server-with-different-SSL-certificates-SNI-support-

0

Comment actions Permalink
Anton Maslov December 19, 2019 20:02

Dennis Scheidner Michael ability to specify a custom name as mail server for Mail autodiscovery has been implemented, and should become available in 18.0.23 update, scheduled for January-Feb, 2020.

0

Comment actions Permalink
Dennis Scheidner December 20, 2019 08:33

@Anton Maslov Thats great. Thank you very much.

0

Comment actions Permalink
Andre Lisbert December 21, 2019 14:01 (Edited December 21, 2019 14:16)

I was in the other post, sorry, here it belongs:

Hi,

I have tried it manually and then I found this thread about the configuration on board.

For me its lacking some infos probably. But I can not get the right MX domain picked from thunderbird.

ANd also it doesnt create any new folder under .well-known as I expected.

mail.mydomain.com is the host for incoming and outgoing Email, and the auto process only sees domain.com

My scenario is: The client domain has wildcard SSL installed and email is running fine. The domain is hosted on inwx.de and so with an external provider. On Plesk (latest, updated) no DNS running. When in Plesk I have performed all steps above, I had no success, only the domain.com is considered not mail.domain.com and also I would like to know how I can roll out after I made it work , to all existing email boxes??

All the best.

Andre

EDIT: Here are my DNS settings , where the MX in mail.domain.com is the same like in SRV and in the spif also, it has also everything green in the test I made.
Though the hosting panel runs on host.short.com

Screener attached and here.

0

Comment actions Permalink
Alexey Lapshin December 25, 2019 08:22 (Edited December 25, 2019 08:23)

Hello, @Andre.

As I see you have wildcard subdomains in DNS settings (with * symbol).
To enable mail autodiscover via HTTPS for these domains, create a wildcard subdomain in Plesk, get a wildcard SSL/TLS certificate, and secure the following with this certificate: the domain itself, the mail server, and the created wildcard subdomain. To secure the wildcard subdomain, go to its Hosting Settings and choose the wildcard certificate (the one that has the asterisk prefix *). Choosing the wildcard certificate for the wildcard subdomain is necessary because it will otherwise use the self-signed Plesk SSL/TLS certificate by default (even if a wildcard certificate was issued). Please refer to https://docs.plesk.com/en-US/obsidian/administrator-guide/65691/#limitations for more details. If this suggestion will not help you - please submit a ticket to Plesk Support https://support.plesk.com/hc/en-us

0

Comment actions Permalink
Andre Lisbert December 25, 2019 20:29 (Edited December 25, 2019 20:37)

Hi @Alexey Lapshin, thanks for your kind reply. I only use and will use Let'sEncrypt Certs which are considered working fine in Plesk as the article youve linked me to implies.

So, and I have NO DNS running and wont make it run on plesk managed server as well.

Do I get you right, that I create a subdomain in plesk, taht is *.mydomain.com and directly related to the wildcard setting on the domain providers set up?

That would be like a "ghost subdomain" cause the mailboxes and the website and all is running under the webspace of mydomain.com with the MX setting of mail.mydomain.com...

Not quite sure if I got you right.
and in the mail settings of mydomain.com it was long time already selected as the securing cert.
Andre

EDIT: Interesting, I have not known about this option in sub-domains, cause I havent read the text above. But AM NOT ABLE to pick the lets encrypt radio button then when I have submitted an asterisk there

0

Comment actions Permalink
Andre Lisbert December 25, 2019 20:49 (Edited December 25, 2019 22:24)

Hi @..., this seems to be correct now, as the domain and wildcard was already secured before. Now I set up the missing sub domain in Plesk, cant pick the cert again, but is anyway already issued.

EDIT:
Cool stuff, that these settings exist, but it still doesnt work. I guess it is due to what will be corrected in version 18.0.22 like told here https://talk.plesk.com/threads/mail-setup-in-outlook.354556/

While I still have to care for the issue that my hostname is host.MAINDOMAIN.com and my mail server name is mail.CLIENTdomain.com

So, in fact I probably need to use all mail server setups with the hostname on which plesk is running, right?

And then, if that all works, for NEW boxes then... How can I roll it out beneath all existing boxes?

0

Comment actions Permalink
Alexey Lapshin December 26, 2019 03:14

Hello, Andre.

Please find below answer on the questions:
> So, in fact I probably need to use all mail server setups with the hostname on which plesk is running, right?
Since in Plesk Obsidian SNI support is available now, it is possible to assign different SSL certificates to domains on a local mail servers. You can specify domain name as mail server.

> And then, if that all works, for NEW boxes then... How can I roll it out beneath all existing boxes?
For existing mailboxes it is not required to reconnect mailclient, because the Plesk process all autodiscover request sends by mail client https://support.microsoft.com/en-in/help/3211279/outlook-2016-implementation-of-autodiscover.

0

Comment actions Permalink
Andre Lisbert December 26, 2019 08:16 (Edited December 26, 2019 09:54)

Hi,

this sounds like great news.

And the settings in Panel.ini for [mail]?

I dont want it to display wrong vaalues in case one user reads the note.

Now, it simply takes te hostname which is host.MYdomain.com, but the placeholder shall display mail.CLIENTdomain.com

cause that is set in inwx ...

I had tried with mail.<domain> but it had no effect.

EDIT: Okay, this I found out and works, the extension Panel.ini doesnt do its job and its not saved, must be done by hand. Then it works in the labels about Email setup.

0

Comment actions Permalink
Andre Lisbert December 26, 2019 09:55 (Edited December 26, 2019 10:36)

The autodiscover still dont work sadly, @...

0

Comment actions Permalink
Vladimir Chernikov December 31, 2019 14:05

Hello @Andre Lisbert,

Could you please clarify what was added to [mail] section in panel.ini?

This is settings from the test server:
[mail]
autoconfig.enabled = true
autoconfig.url = http://127.0.0.1:8880

Also, does the autodiscovery did not work in Thunderbird only or in Microsoft Outlook as well?

0

Comment actions Permalink
Andre Lisbert December 31, 2019 14:35

Well, on both it didnt work. I checked with windows 10 outlook (also subscribed to office 365)

And i didnt know that this panel setting was needed at all. The description of plesk in this matter lacks utmost all. I ve told them already, that its maybe better to have a instruction ready available at the time of rolling out a feature.

So, what to do?

0

Comment actions Permalink
Anton Maslov January 03, 2020 20:32

Hi Andre, please create a support ticket to check the issue, your case not trivial and article comments is not quite good for troubleshooting:

https://support.plesk.com/hc

0

Comment actions Permalink
Carlos Marchi January 06, 2020 20:14

When I go to "2.1- Go to Tools & Settings > Mail Server Settings > Settings tab > General options > Enable the Enable mail autodiscover option:" I can't find the "Enable mail autodiscover option". I've just updated to 18.0.21, rebooted the server but it's still not showing.

Maybe removing all mail services and reinstalling?

0

Comment actions Permalink
Andre Lisbert January 07, 2020 02:30

Hi Anton Maslov Am confused of the why. Nearly all settings are done. Cannot be much, can it

Gonna ask at plesk (but am using a hosted license) and also my provider (who in the past already had once sent me away to plesk directly. Hope it works.

Gonna date up.

Vladimir Chernikov Hi, what is the COrrect setting then? of this:

[mail]
autoconfig.enabled = true
autoconfig.url = http://127.0.0.1:8880

----

Alll the best and thanks,

Andre.

0

Comment actions Permalink
Julian Bonpland January 07, 2020 18:21

Hi Carlos Marchi Could you please open a support ticket with us so we can take a look at the logs?: https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-

0

Comment actions Permalink
Sascha Schlüter January 08, 2020 12:22 (Edited January 08, 2020 17:07)

I am facing the same problem as Carlos Marchi: when reaching point 2.1. of instructions above, there is no option 'Enable mail autodiscover' on Plesk Obsidian 18.0.21 Update #5 on Debian 9.11

EDIT: i found the solution by myself... modifying the panel.ini via Panel.ini Editor makes the option available. "autoconfig.enabled = 1"

0

Comment actions Permalink
Julian Bonpland January 08, 2020 19:39

Sascha Schlüter We have encountered some scenarios where Plesk Premium Email would set "autoconfig-enabled = 0" which in turns removes Autodiscover from the UI.

If this was your case thanks for sharing the resolution. If not please open a support ticket with us so we can troubleshoot: https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-

1

Comment actions Permalink
Andre Lisbert January 09, 2020 18:13 (Edited January 09, 2020 18:16)

Hi,
I was short before solving the problem.

My plesk subsrciption is part of a my hosting providers' license.

And I could (!) solve it over their subscription key, they have no issue.

But as I was SHORT before solving it here, why is my solution interrupted? This is a support desk, or not? Kindly follow up with my question:

Hi, what is the correct setting then? of this:

[mail]
autoconfig.enabled = true
autoconfig.url = http://127.0.0.1:8880
Julian Bonpland
and Vladimir Chernikov

0

Comment actions Permalink
Robert Asilbekov January 13, 2020 13:41

@Andre Lisbert

> So, in fact I probably need to use all mail server setups with the hostname on which plesk is running, right?

Plesk Mail autodiscovery feature relies on domain name and not to the server hostname, and this is cannot be changed.
Outlook first does a DNS lookup for "SRV" record at _autodiscover._tcp.example.com to find the address of the autodiscover server, and then it tries to fetch XML file with all the required configuration over HTTPS from there.
But you have two autodiscover._tcp hosts with 465 and 993 ports specified. You need to remove extra autodiscover._tcp host and set the port to 443

> My plesk subsrciption is part of a my hosting providers' license.
As the license was purchased from a partner, you should contact them for support or purchase a support subscription to get support directly from Plesk.

Complex technical issues are better to be checked in scope of support tickets as it allows us to take a deeper look at the issue, involving server access if required.
For technical support questions please consider creating a technical support request.

How to submit a request to Plesk support?

How to get support directly from Plesk?

0

Comment actions Permalink
Andre Lisbert January 20, 2020 12:49

Hi, thank you a lot for your kind answer.

> Plesk Mail autodiscovery feature relies on domain name and not to the server hostname, and this is cannot be changed.

I dont want to connect it to the hostname of the server at all. It is my intention to have it working according the webhosting account users domain. In the DNS setting on inwx.de or any domain providers DNS I will set MX record to mail.userdomain.com and this should be used. But right now it only recognizes userdomain.com in the Incoming- and Outgoing mail server setup.

I will try this change on DNS becase the SRV record.

I opened a ticket using the installation key, which was denied by plesk. THat is making things EXTRA complicated in my eyes.

When I have the key I also pay so Plesk earns on this pay, maybe not in direct way, but this should be enough for me to get a little support. Especially when this support comes because a lack in documentation about one of their features.

And when the solution would be posted here, many others with similar setups would get help in public.

This way Plesk is using now makes me wanna move away, although this is the first issue, but heavy enough.

All the best.

Andre

1

Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Articles in this section

Applicable to:

Question

Answer

Troubleshooting

Related articles