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.
Alexey Lapshin
shared this idea
Hello, everyone.
We are glad to inform you that since SSL It! 1.16.0/Let's Encrypt 3.2.9 with the "no web hosting" subscription type you can issue and SSL certificate for mail.domain.com.
Thank you for your contribution in making Plesk better.
-- SH
-
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...
-
Anonymous
commented
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.
-
Anonymous
commented
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:
Secure
mail.customerdomain.tld
webmail.customerdomain.tld
with Let´s Encrypt certificate without having to set the DNS A Record for
customerdomain.tld
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).