Assign separate SSL certificates for multiple mail servers
Allow the ability to assign separate SSL certificates for multiple mail servers.
Available since Plesk Obsidian RC3. Windows: modern version of MailEnable required (shipped with Plesk), Linux: modern versions of Postfix (shipped with Plesk) and Dovecot (shipped by most OS vendors) required.
Please read the docs: https://docs.plesk.com/en-US/obsidian/customer-guide/websites-and-domains/securing-connections-with-ssltls-certificates/protecting-webmail-and-mail-with-ssltls-certificates.76531/
— rk
-
ArtProject commented
WE ABSOLUTELY NEED THIS FEATURE
-
Flo Knapp commented
Please add this enhancement to plesk. It's such a good server administration tool but the lack of this feature is annoying. Especially if it comes to explaining an iOS user why setting up the mail account on his smartphone won't work. I'm aware of the fact that you can install a multi-domain certificate but who can pay up to 5.000$ if you aren't doing it in a professional manner.
-
Ingo commented
In my opinion this is a must have feature.
-
Anonymous commented
With the introduction of ios 11.3 on apple devices all mail from plesk installations in rejected without possibility to manually accept the certificate. This renders the mail functionality in plesk useless for apple users. Unless you implement this whitin a week or two we will be forced to switch to a usable platform.
-
Anonymous commented
With the introduction of ios 11.2 on apple devices all mail from plesk installations in rejected without possibility to manually accept the certificate. This renders the mail functionality in plesk useless for apple users. Unless you implement this whitin a week or two we will be forced to switch to a usable platform.
-
Anonymous commented
Unless they will allow hundreds of domains per SSL certificate, that would be a useless option for us as we have over 400 domains hosted.
-
Sergio Manzi commented
For incoming (SMTP and/or IMAP/POP3) connections I think this is nonsense: *UNLESS A DEDICATED IP ADDRESS IS ASSIGNED TO THAT PARTICULAR DOMAIN*: When the server receive an incoming connection it can't know in advance "for what domain" this connection will be. This is different from HTTP "connections" where Apache (or Nginx) can derive the destination endpoint (domain) from the HTTP header.
What we need, I think, is support for "multi-domain" certificates, the same way it is done for HTTP when you have a domain with several domain aliases and you can get a Let's Encrypt certificate valid for all those domains
For webmail I think we already have what we need...
-
Mannie commented
Please
-
J.B. commented
We need this function too, it is very important! :)
-
Anonymous commented
We need this function :)
-
Leon Cuzzilla commented
Would be incredibly useful
-
Anonymous commented
Definitely needed! We are a hosting provider with 400 odd domains and it's frustrating for our clients when they can't use mail.domainname for their incoming and outgoing due to an ssl hostname mismatch error.
-
Ali commented
Would be very useful!..It's also pretty urgent!
-
Francois commented
Would be very useful!
-
Anonymous commented
Yes PLEASE, very urgent!!