make SSL Certificates for mail services manageable from Plesk
To change SSL certs for mail services one has to manually change at least three files: (depending on system e.g.)
/etc/postfix/postfix_default.pem
/usr/share/imapd.pem
/usr/share/pop3d.pem
This is very confusion and not very usable, esp. as there are already a number of SSL ways to set certificates in Plesk (per domain, per ID, for the panel, as std. for all domains, ...)
This could be streamlined and a simple tickbox, like 'Set this certificate for mail services' would make the life of administrators much easier!
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
-
Anonymous commented
Please don't forget /etc/dovecot
-
AmaZili Communication commented
Is there any kind of planning for the release ?
-
Anonymous commented
Yeah an update would be really nice. I have 30 customers on my server running with more than 40 different domains. I need to use a different certificate for every customer I have or some mails will not arrive appropriately.
-
tobias buschor commented
any news?
-
[Deleted User] commented
I switched 1 week ago for Let's Encrypt. It's absolutely really good, the plesk module is nice and well integrated. Thank you for this development. I agree with other people, the webmail could benefit from the SSL Certificate.
+1 for Let's Encrypt !
-
Elompenta commented
Thank you!!!
-
Physicus commented
Please also consider to implement a simple instrumentation of certificates for webmail (other, than the default certificate).
-
Hostasaurus commented
Why does everyone keep posting about the Lets Encrypt project? The two can happily coexist but that doesn't preclude the need to manage the certs for the mail (and ftp) servers. We have customers who, for PCI reasons, or corporate policy reasons, need an EV cert from a 'name brand' provider, and they need it present on any accessible secure port, whether that be for mail, ftp, https, etc. Thus, this feature request is still important, and Lets Encrypt wouldn't solve it.
-
Anonymous commented
stop working on this project and focus on
http://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/7067777-free-ssl-project-let-s-encryptas wikrie said before
-
Dragan commented
I bought Plesk only because of POP3 email and now it's not working. It should be working out of the box. This is the most important thing for Control panels like Plesk and others so that users can manage their emails withut using command lines.
-
wikrie commented
if we would get this:
https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/7067777-free-ssl-project-let-s-encrypt
we could create certs for mail.domain.tld and a different one for www.domain.tld
let’s encrypt would provide FREE certs and also a routine for update certs, all we need would be let’s encrypt.
Here is a small text from the website:Anyone who has gone through the trouble of setting up a secure website knows what a hassle getting and maintaining a certificate can be. Let’s Encrypt automates away the pain and lets site operators turn on and manage HTTPS with simple com-mands.
No validation emails, no complicated configuration editing, no expired certificates breaking your website. And of course, because Let’s Encrypt provides certificates for free, no need to arrange payment.
Please check let’s encrypt and do not waste manpower for this, this is my point of view.SO please vote for Let's Encrypt.
-
Jason commented
There is already a great extension that does this from Admin-Ahead. We got tired of waiting and along with others, requested they make an extension and they did within a matter of weeks. For critical needs like this, we cannot wait two years for functionality evaluation by Odin. The hosting world move too quickly.
-
Joerg Uhlmann commented
..this is great! Thanks
-
Andreas Schnederle-Wagner commented
+3
-
Anonymous commented
Need it!
-
Lukasz Rutkowski commented
Yes.
Need it.managable independly for each domain + master SSL for each webmail
-
Nikhil Thomas commented
We just released an extension for this: http://goo.gl/4bgDxX
Hope this helps.
-
AmaZili Communication commented
Solution could be for shared host with one Ip to have per domain or per subscription mail servers.
May be plesk could think about this ?
It will create overhead to the whole server, but could be a simple solution to make sure right certificate is delivered by shares hosts. -
Sebastian commented
please add
-
Jason commented
Whoever posted this, can you show us the link where you actually got it to work?)
Anonymous commented · April 21, 2015 08:25
Yes, that shit cost me a lot of time to figure it out the first time I installed a certificate and a since then every year to remember when the certificate expires and has the get replaced.