It would also be useful to be able to create a certificate for mail.example.com when the "Hosting Type" option is set to "No Hosting" (whereas the domain points or not to the server)

It would be just as creating a certificate for "webmail.example.com" works now, I guess ?

Lets do it! CRITICAL

Can you please qualify "popular" please? This is an old feature, reported in 2019, and still BADLY required today in 2024. I have had this problem with the mail server using a subdomain like "mail.somedomain.com" and LE can not cope with it. Halfway through my email stops working.

This is a CRITICAL requirement, and should not be treated as a would be nice feature request. You are providing SSL certificates support through LE for securing the website and other components, but this functionality is incomplete because it is not designed to cope with subdomains in zones managed externally.

CRITICAL!

I echo the comments below. Like with Hover and OpenSRS who also provide mail hosting, they DO NOT require A records for example.com to point to their servers hosting mail.example.com

Unacceptable that this isn't a feature yet. Not only is it completely necessary, as is clear by the comments and votes, this shouldn't be a popularity competition for a feature that is so essential to the normal functioning of a server. Anyone with more than 2 hosting clients will have clients that just want mail while their root A record is pointed elsewhere. I'm incredibly disappointed with Plesk's lukewarm response to this crucial security feature.

How is this not a thing yet ...

yes, yes, yes, PLEASE

+3

A must-have feature, as Plesk did with the separated certificate for webmail long time ago, but for "mail" is more crucial.

This feature needs to be prioritized. It fills a crucial gap in functionality and aligns perfectly with user needs and industry trends, as mails are commonly hosted on different servers. The status quo renders plesk difficult to use for mails.

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.