Add management of webmail SSL certificates
I would like to propose the management of SSL certificates for webmail in plesk panel.
Now, unless you use a wildcard certificate, you cannot secure your webmail with a valid SSL certificate.
Please make the SSL certificate used for webmail.<domain> .
Please also add a configurable central url for webmail, with SSL support, and add a redirect option to that url for webmail.<domain>
E.G. visitors for http://webmail.<customerdomain> will be redirected to https://<configuredwebmailurl>
We’re happy to announce that this feature is now available in Plesk Onyx, which was released recently for early adopters. You can try Plesk Onyx here: https://www.plesk.com/onyx/
If you have any feedback on the implementation of this feature, please let us know on the forum: https://talk.plesk.com/forums/plesk-onyx.744/
Thank you!
—AK
-
Marco Marsala commented
You should place a redirect from http://webmail.domain.tld to https. Even the option "Hosting Settings > Permanent SEO-safe 301 redirect from HTTP to HTTPS" won't redirect the webmail; in any case these should be two separate options as the website may not support HTTPS yet.
There is an UI bug under Domains > example.com > SSL Certificates: selecting a certificate already used for securing webmail and hitting button "Secure Webmail" will freeze the interface.
-
Anonymous commented
We need it in PleskPanel also...
-
darkdragon commented
Please also add a checkbox to "Secure Mailing Lists Webinterface":
https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/10759350-request-to-add-ssl-tls-support-for-mailman-webinte -
Joe_Crash commented
Great if Let's encrypt will be integrated for webmail as well..... :D
-
Anonymous commented
Please let us know when this has been implemented in the main branch.
-
Anonymous commented
Great suggestion. Something like this has to be automated.
https://www.lloyd-day.me/secure-plesk-webmails/ -
Panel-User commented
We need this future too.
Maybe Plesk can create let´s encrypt ssl-certificates for webmail.<customerdomain> at the time a new domain is created for an useraccount. Lets encrypt is implemented in Plesk and works finde. So no need for redirect from webmail.<customerdomain> to webmail.<configuredwebmailurl> -
Jason H. commented
We need this feature too.
-
UFHH01 commented
"Planned" now for over a year, which is really ... let's say "sad". Work-arounds and suggestions in the Plesk - forum should give the developpers enough informations, how to implement this suggestion into Plesk, so pls. Plesk - Team, get back to work and start the integration for this feature.
-
Heiko commented
I need this as well
-
Peter commented
Letsencrypt Extension can provide valid SSL for domain.tld, I would like to use the same certificate for Webmail with URL https://domain.tld/webmail (without additional subdomain)
-
Alex Devon commented
I use WILDCARD CERTS with IMAP but they are IP based and the procedure is very awkward and outside of PLESK
a. Also no SNI – so cannot do TLC_CF.domain.tld for all virtual hosts for COURIER-IMAP
2. No straightforward way to use WILDCARD cert for Webmail – Horde or Roundcube
3. How do I set up multiple domains with wildcard Certs – I have 3 IPs and each IP has multiple domains and each TLD has multiple subdomains so I want to configure Postfix to send mail for zebra@sub.dom1.tld from smtp.sub.dom1.tld etc -
Alex Devon commented
There are numerous servers on the web using multiple domains and subdomains on few IP addresses. Please implement wildcard SSL Certs and SNI built into Plesk user interface.
-
Dimitris G commented
I solved this problem using Cloudflare. You just need to enable CF SSL on your webmail subdomain.
-
Patrick commented
Please also allow letsencrypt Extension to do this job
-
Elompenta commented
Please add a configuration, that the Plesk-Hostname or Hostname/webmail are will display the webmailer
-
brainforge commented
Similar to adding the following lines to /usr/share/psa-horde/login.php (which of course gets overwritten on Plesk upgrade):
if($_SERVER['SERVER_PORT'] != 443) { // Forces SSL
header("HTTP/1.1 301 Moved Permanently");
header("Location: https://".$_SERVER['HTTP_HOST']. $_SERVER['REQUEST_URI']);
exit();
} -
Barth commented
very important for customers and security
-
Joerg commented
same wish, thx
-
Cody commented
I am also looking for this feature.