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
-
Martin Schenk commented
very important, please do it.
-
Anonymous commented
Absolutely vital requirement. I thought the letsencrypt wildcard certificate would solve this problem. did not realise that Plesk would not implement it with priority - very disappointed
-
Daniel Omine commented
very important, please.
-
Andrey commented
very important feature
-
Markus commented
yes. Important feature.
-
Anonymous commented
ALL our client with Outlook 2016 And new IOS have problems beacause this feature is missing
-
EmmanuelP5 commented
Plesk do not respect the best pratice for a good email deliverability best, the develoopers are probably lazy to make this changes ?
Plesk is an old company already and maybe started to think that's not necessary to follow thebest pratice and new options.
It must be fixed as soon as possible, as a priority task, without a good email deliverability and respect best practices, Plesk doesn't make sense to be used.
-
System Admin commented
Google recently forced their users with restricted SSL for POPS/IMAPS, this is no longer a feature. it is a requirement. even if you secure your customer domain with a wildcard, you'll get the CT error.
Plesk needs a virtual mail server sharing the same IP as virtual hosts do. -
Anonymous commented
vote also here, the new office 365 only configurable via email name and after that i get certifacte errors...
-
Anonymous commented
Customers with Apple devices have a lot of cert problems, this would be the fix.
Would be great to include mail.domain.xyz to the Lets Encrypt certificates, like webmail, by default and use this certificate in the mailserver config.
-
Anonymous commented
Apple devices are now rejecting certificate
-
Anonymous commented
Really needed
Using
mail.cistomer1.tdl
mail.cistomer2.tdl
mail.cistomer3.tdl
mail.cistomer4.tdlInstead of
sameforall.server.tldWould be a serious good improvement
-
Armin commented
Definitely needed!
-
[Deleted User] commented
I don't know if this is the right Place, but for those who keep searching for that feature "AdminAhead" has a nice Plugin for this which gets the job done (Again no Advertisment here, just wanted to share). I really really hope it won't take long to integrate this in Plesk!
-
Anonymous commented
Really missing it
-
[Deleted User] commented
Yes, i don't know why this is not implemented yet!
-
TRILOS new media commented
Great. But keep an eye on other suggestions here, regarding similar requests, referring to develop Let´s Encrypt Extension to be able to secure customer´s mail domains (and without being forced to have web service enabled only for this).
-
Anonymous commented
We need it !
-
Anonymous commented
Definitely needed! As a hosting provider it's frustrating that we can not provide the appropriate e-mail service to our clients (we need email support for multiple customer-domains on a single Server / 1 IP-Adress incl. SSL)
-
Robert Harrington commented
Please add this enhancement to Plesk! I would be a great improvement.