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
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.
—
IG
-
Anonymous
commented
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
-
Fragiskos
commented
A much needed feature.
Please add this. -
YM
commented
That would be a great implementation..
Thanks. -
WN
commented
This is a MUST.
cPanel has it since YEARS. -
Torsten
commented
I absolutely need this opportunity. We have two servers to separate web and mail space. The only-mail-server with over 100 customers.
-
Frank
commented
+1
-
Jeroen
commented
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...
-
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).
