Add possibility issue Let's Encrypt SSL certificate for mail server when the "A" DNS record for domain is pointing to another server
This feature is required for users with the configuration when on the Plesk only mail server for domain is used.
"A" DNS record for mail.example.com is pointing to Plesk server, when when "A" record for example.com is pointing to another server.
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular. Everyone, please continue voting for this feature if you consider it important.
This is also a very need feature for us.
We hope this will be implemented as soon as possible.
We have clients that only have email service.
A good workaround was PLESK add webmail.customerdomain.tld as a server name indication (SNI).
Tessa Vermeulen commented
Indeed! In the begin people used pop3.domain.tld for incoming and smtp.domain.tld for outgoing. Now people are more and more using mail.domain.tld for incoming and outgoing mailserver. (with the correct ports). But the only way to have it on SSL is to create a subdomain for each subscription called mail.domain.tld and point the certificate to it. Just add another checkbox like the webmail for mail. will help alot.
We need to be able to use mail.domain.tld to secure SMTP, POP, IMAP without needing to use a Let's Encrypt Wildcard SSL/TLS certificate and without needing to create a subdomain for mail.domain.tld. Perhaps mail.domain.tld should always be added as an alias to the webmail.domain.tld vhost. That way a HTTP-01 challenge can be done.
Plesk Tech Support commented
Issuing Let's Encrypt certificates for mail.domain.tld (to secure SMTP POP IMAP) without web-hosting enabled on the main domain. At this way, Plesk can provide only mail services.
Salvatore Fresta commented
Please add this support asap
A much needed feature.
Please add this.
That would be a great implementation..
This is a MUST.
cPanel has it since YEARS.
I absolutely need this opportunity. We have two servers to separate web and mail space. The only-mail-server with over 100 customers.
Not having this function basically makes it impossible to provide email-hosting service to customers.
Oleg Burca commented
Very important and absolutely unclear why this doesn't work already.
Actually you cannot provide just email hosting for someone that needs his own subdomain to be used.
Also you have problems if the domain is configured to use some CDN like CloudFlare.
Sean Cardus commented
The latest version of Plesk seems to half-implement this feature. For example, dovecot contains config files for the "mail" subdomain of each subscription, but the certificates those configs use have not been issued for those subdomains.
Please fully implement this feature asap. Thanks...
Good idea even if you can create a subdomain mail.domain.xx and secure that as a workaround. Then use that certificate in mail settings on the main domain.
I think this is very important
TRILOS new media commented
No suggestion, but a critical, urgent, overdue feature request, as described in many "suggestions" since years:
with Let´s Encrypt certificate without having to set the DNS A Record for
to the mailserver IP.
And withouth having WAF disabled (SSL It 1.20 is being blocked bei Comodo (free) and Atomic (free) rules, other not tested yet).