Add "mail.example.com" (mail subdomain) in Subject Alternative Names when option "Assign the certificate to mail domain" is selected
Currently almost all mail clients (I used) need the server address to be in the Subject Alternative Names on the certificate, meaning if the configured address is "mail.example.com" instead of "example.com", that first subdomain is not present in the certificate, even when the option "Assign the certificate to mail domain" is selected when issuing the certificate.
b.pedini
shared this idea
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG
-
barry
commented
I had suggested that Plesk really needs to support a mail domain name of mail.domain.*** instead of domain.***, since if a the website itself is hosted outside of Plesk and only mail is hosted on Plex, the management of the emails becomes very cumbersome.
Plesk just notified me that they had consolidated my idea (mangled but described as coming from Plesk Tech Support) into this suggestion, even though it really has very little to do with it. And when I look and see that this and other suggestions have been sitting around for years without being acted on, then I wonder what is the point of this.
-
Plesk Tech Support
commented
Websites are hosted elsewhere. When email accounts are created, the mail server name is the root domain name, which is not on the server. get plesk to recognize by default a mail server name of user1@mail.example.ext instead of user1@example.ext
-
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 do not contain the mail subdomain as a SAN!
Please fully implement this feature asap. Thanks...
-
b.pedini
commented
Igor, sorry to be honest, but 1 hour of even an entry-level engineer, is in my opinion worth a security issue that bugs every Plesk server in existance.
How many votes would you need to consider using a tini tity bit of your team time, to implement something that you can touch with your own hands? Because the Plesk UserVoice is full of things well-voted but never even taken into not even remote consideration
- https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/5284370-synchronize-plesk-servers-failover
- https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/4078720-add-clamav-as-module-in-plesk-to-protect-better-th
- https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/4565504-block-the-ip-of-the-selected-country-in-firewall
respectively, one with more than one thousand paying customers asking for, and two relatively easy-to-implement tasks with more than 9 hundred and 5 hundred respectively, yet not even remotely taken into account.
Are those enough proof that your copypaste default reply just irritates people and serves nothing?