This feature is more then cruical for us! Please listen too the users and add this feature already...

This holds great importance for us as this particular configuration is utilized by numerous domains belonging to our SAAS CMS Customers. Additionally, we also host mail-only packages from Plesk. However, we have encountered an issue where Let's Encrypt is not available for the mail.example.com domain since no website is provisioned for it. While Let's Encrypt is available for webmail.example.com, using it with imaps/smtps as the hostname results in a mismatched certificate warning for end users. This discrepancy seems to be a bug in the SSL IT extension, rather than a simple feature request.

This is a must functionality.

I can't believe it either. This is a must functionality.

I can't believe why this is still not implemented in Plesk. The days when all services ran on the same server are long gone. With the boom of website builders like Wix, Squarespace, Jimdo, etc., the services are distributed on multiple servers, which does not fit the path Plesk has taken: that Let's Encrypt certificates should be verified on domain.com.

I have to move large quantities of users off legacy platforms like Hsphere and even Cpanel where mail.domain.tld is set as incoming and outgoing server.

At the very least Plesk you could generate a clear article on how to properly script an event to add this subdomain as a new domain is added.

Lady Linux

We have hundreds domains with mail service on several Plesk servers with the main domain pointing to an external server/service. Having email with SSL in 2023 is extremely important!

I can't belive this has not been addressed yet, this is not even a question of votes, this is basic common sense.

I have too many clients who leave DNS and email management with us, but move Website elsewhere

It would be very desirable for Plesk to have an option, besides the "include www.domain.name" and "Secure webmail.domain.name" options to "Include mail.domain.name" on issuing a Let's Encrypt SSL certificate. If the DNS service is hosted on a 3rd-party service, the mail.domain.name is not secured and the wildcard certificate will not be automatically renewed.

Hi,

We are hosting also mail only packages from plesk. Letsencrypt is not available for mail.example.com since no website is provisioned. It is available for webmail.example.com but that does not work with imaps / smtps as hostname (service will provide wrong certificate and enduser gets warning hostname not matching). In mycase A record can be pointing to plesk but letsencr not available for other domains. I consider this a Bug on SSL IT extension rather than feature request.

Similiar Feature Requests:
- https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/39378850-add-possibility-issue-let-s-encrypt-ssl-certificat
- https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/45565207-issuing-let-s-encrypt-certificates-for-mail-domain

@Plesk - can they be merged so the Votes count together?

Similiar Feature Requests:
- https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/39378850-add-possibility-issue-let-s-encrypt-ssl-certificat
- https://plesk.uservoice.com/forums/184549/suggestions/39328840

@Plesk - can they be merged so the Votes count together?

Should be available already, not every customer wants to pay for o365

This would be cruical for us as excactly this configuration is used by thousands of Domains of our SAAS CMS Customers ...

https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/45565207-issuing-let-s-encrypt-certificates-for-mail-domain

I think we are basically talking about the same issue on this suggestion and that they could be merged them to count the votes?

https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/39328840-use-let-s-encrypt-to-secure-imap-pop-smtp-connec

I think we are basically talking about the same issue on this suggestion and that they could be merged them to count the votes?

We need this feature in an era of secure communications, where having a certificate is ubiquitous, customers demand for it and improves the security of the services.

This is also a very need feature for us.
We hope this will be implemented as soon as possible.

Thanks

We have clients that only have email service.
A good workaround was PLESK add webmail.customerdomain.tld as a server name indication (SNI).

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.