Hey guys,

We're still waiting for this issue to be fixed. Manual configuration is extremely inconvenient to inexperienced customers. Customers need productivity, not technical ability.

I'm surprised this isn't implemented yet.
Please, add it to Plesk.

@ChrisH: You could take a look at ActiveSync in Horde. There is an option to use Autodiscover for IMAP/POP/SMTP even if you don't use ActiveSync (but it must be activated). I don't know which clients use it, I tried it with Outlook 2016 and it worked.

@Simon E.: Ok, then I won't wait :-) Sorry for this newbie question...

@ChrisH: Don't be silly. Plesk team never ever solved any feature request within weeks, except it was a security issue everybody on the internet had read about

Hello Plesk Staff, do you see any chance for an autodiscover solution in Plesk soon? E.g. In the next weeks? Otherwise we have to create an solution by foot before migrating thousands of mail accounts to Plesk. Thanks a lot in advance!

I would like to have all possibilities nicely supported from the GUI (e.g. which settings should be favored over which). As long as there is no SNI for POP3/IMAP/SMTP (thus all clients receive the same SSL certificate), this feature is a must!

For one client where it is really important, I enabled autodiscover for Outlook, by using "autodiscover.php" and ".htaccess" from https://github.com/cfoellmann/ISPC-resources/tree/master/guides/autodiscover and adapting it to my needs.

It's really needed... please add.

It's really needed... please add.

Please add this much needed "feature"

Need this feature!

I have written an autodiscovery mechanism for my clients which works.
It works for Outlook and for Thunderbird.
I know of 3 mechanisms to autodiscover mail settings.
As far as I discovered, these are:

* Microsoft's autodiscover (used by Outlook)
* Thunderbird's autoconfig (used by Thunderbird)
* rfc6186 (afaik not used by any mail client)

I have written scripts that are running on the DNS-server (mine is a seperate Plesk server) that create the DNS-records for each domain that has an MX-record pointing to a server of mine. It will delete those records if the MX goes foreign.

On the mailservers I have a wildcard certificate of the company I work for.
Each domain will connect to a subdomain of my company's domain where the subdomain is the FQDN of the client's domain with its dot replaced by a dash (wildcard certificates go only 1 level deep).

The SRV records (rfc6186 and outlook) and the CNAME (thunderbird) will be created in the client's domain.
The target of these records are pointing to a CNAME in my company's domain.
The CNAME in the company's domain will point to mail.<clientdomain>.

It's explained (partly) here: https://talk.plesk.com/threads/ssl-certificates-for-mail-server.342531/
I don't have a full write-up.
The main reason is time and it's also very customized to my situation

We want this autoconfig thing to have Thunderbird, Outlook and IOS Devices detect automatically PORTS and SERVER and USERNAME when setting up a new Email in Email Clients.
At the moment Client has to change and insert everthing manually.

https://dokuwiki.nausch.org/doku.php/centos:mail_c6:autoconfig_3

https://dokuwiki.nausch.org/doku.php/centos:mail_c6:autoconfig_2

https://developer.mozilla.org/de/docs/Mozilla/Thunderbird/Autokonfiguration

I request this too

This feature would be very helpful, as we too much time configuring email clients.

Just adding my name to the list here. I've done several hours of work on this, and was not able to get a good result in testing with Thunderbird client. If there was at the very least some good step-by-step documentation on 1) DNS settings (for configuring multiple client domains to connect to a single mailserver ie. mail.example.com 2) A way to automatically generate autoconfig.xml file with the correct server names, port numbers, etc. 3) Documentation on where those files should be placed. Please and thanks!

With the increasing need for improved security including more complex email addresses its important to cater for the end user - those typically with much less confidence in technology. Allowing them to have a pleasant experience with configuring their email accounts, SSL settings etc will reduce time for service teams but also help encourage them to explore technology more. We are in the business of making things easier

Yes please, this would be great!

yes for me also...
we always use ssl/tls with the servername

When this is implemented, it will also need to have the domain name fully customizable for those of us that use Plesk for an email-only server.

I have the email domains as root domains (domain.tld) on the server, but I have remote DNS handled so that mail.domain.tld is the MX pointing to the server.

So, if the autodiscover output says that the mail server is at "domain.tld" it will fail. Don't make it fully automatic without the ability to define the server domain manually.