Use "Let's encrypt" to secure IMAP/POP/SMTP connections
Use "Let's encrypt" to secure IMAP/POP/SMTP connections to avoid "non valid certificate" messages with self signed certs.
We have detected a fraud attempt for this suggestion. If person who initiated it reads this, please contact us to explain your need.
Otherwise, this suggestion will be declined as incorrect because we can’t determine the real demand for this feature.
UPD: “Fraud” means an attempt to boost votes from fake accounts. 2 of every 3 votes here were fake accounts. That will later be cleaned up and we will work on changing authentication to prevent this issue repeated.
We don’t question validity of this request, but we question how many people would benefit from it. Please continue sharing your stories in comments, it is very helpful
ensure mail with certificate would have to be resolved by Plesk either with Lets Encrypt or with any other provider from the Panel itself as users claim for years and automate mail autoresponders for the start and end , and be able to send backup copies to Google Drive, Onedrive in an easy way, although I believe that the latter has already been implemented.
AmaZili Communication commented
Definitly, definitly needed in 2018.
Middle age of unsecured comunications ended last year :-)
Everyone would benefit greatly from it even if they don't know because it looks much more professional towards all your customers. I am absolutely surprised that this feature does not exist already and my only dissapointment for plesk so far
Yes, it is a vital demand for plesk ! Thank you
G J Piper commented
While this would be a great feature, my understanding is that postfix is incapable of serving certs on multiple hosted domains. Admin: is this incorrect? Would the implementation of this require a migration from postfix to something else?
No fraud attempt, this is the real deal and most of our clients are asking.
I like to reaffirm the aspect of migrating mail domains: Providers and Users should be free in choosing the mail server name and shouldn´t be forced to change mail client configuration. Otherwise it would cause unnecessary trouble and effort, multiplied by every single mail account in a domain.
I also like to give another important aspect. Plesk Servers give you the ability to run a mail-only server and it is an important factor for security and reliability when separating mail and web servers for customers. But today, the ACME process to activate a LE certificate depends on activated web service on a domain, because the LE API checks the MX record of the domain and tries to request a file from the domain via http. In my opinion, latter check is absolutely unnecessary for securing mail transport encryption. Everything the Certificate Authority needs to know wether the DNS authority acknowledges on which IP the mail service is running - and nothing more. Then the Plesk admin don´t have to bring in unnecessary effort for configuring the web service on every domain and loose server´s performance ressources only to provide http request of only one file, when the certificate installation or renew is running. Think about separating the certificate service from the webhosting section!
Konstantinos Spiliakos commented
Even though I'm not the OP, I would assume that it's somewhat implemented already in current Plesk editions. Another point, which I'm not sure if it's the OP's point of view, would be the SNI part which currently the mail servers (postfix/dovecot/mailenable) are lacking.
Mirko M. commented
Good explanation of Anonymous! Thats exactly why we need this feature asap. Plesk has it since years.
It seems, some of the people do not understand what we exactly need this feature for. At least from my side I would like to take the opportunity in order to give you a better understanding.
Yes, currently it is is possible, secure the mailserver with a certificate. However, this would mean, that every user has to use my.servername.abc or mail.coolprovider.xyz
At least we have multiple plesk servers and when migrating users between the machines, we do not want to force people changing their configuration. In many environments changing the email client settings is not that easy as it seems, f.e. in hospitals. Some customers even have their own exchaneg server with a small tool fetching the mails.
So it would be a requirement to find a solution using let's encrypt for securing mail.domainname.xyz - however for all domains on the plesk server.
Yes, it might be, that postfix does not support this feature because of SNI. But some people in forums are also discussing, that a mailserver proxy providing the certificate, and then forwarding the request in plain to the local postfix on another port could work.
valid feature request, I am interested in using Let's encrypt to secure IMAP/POP/SMTP
@Plesk Staff: fraud attempt?!? where do you see fraud? how do you explain fraud attempt here?
little less conversation, little more action as Elvis would say
In my opinion this is a valid feature request. I had hosts screwing up the certificate renewals for email services. Let's encrypt would be a perfect fit for that.
@Plesk Staff: Are you serious about the fraud attempt? What does this even have to do with the feature request?
John A. shiells commented
Lets get this done!
spend less time creating extensions (that cost to use) and lets get some of these wanted feature requests implemented into the plesk core (with having to pay more via an extension).
Reply to Marco Marsala´s comment on April 20, 2018 11:09:
This works only with hosting service enabled and does not work for mail-only Servers, besides it would be a huge effort to do this manually.
@PleskHelps, May 18th via Twitter:
"Mail services used by Plesk do not provide that functionality, so there is going to be no such feature in Let's Encrypt as well."
one more vote from my side. So needed to avoid this messages.
Please implement this as soon as possible
At least until LE support multidomain certificates.
And I know most MTAs support multiple SSL certificates! So, itf mail server is secured with LE, it is just matter of generating a new LE certificate every time a domain is created, and adding such certificate to the mail server configuration. Certificate should be generated for domain: example.com and their popular mail subdomains like: mail.example.com, imap.example.com, smtp.example.com)
Actually you can automatically secure with Let's Encrypt example.com, www.example.com and webmail.example.com. Why don't add mail.example.com, imap.example.com, smtp.example.com, that are tried as default from most e-mail clients and cloud mail services when you insert an email address?
They're just 5 popular subdomains (the number is matching current LE restrictions).