Facebook
Twitter
futureweb
Regular Pleskian
- Server operating system version
- not applicable
- Plesk version and microupdate number
- Plesk Obsidian Version 18.0.46 Update #2
Hello,
currently there is the problem that the following scenario cannot really be mapped in a practical way:
- (www).dom.tld - is NOT pointing to Plesk Server
- mail.dom.tld - is pointing to Plesk Server
There is the problem that the certificate for mail.dom.tld has to be manually assigned to "dom.tld" for the mail services after each renew. With hundreds / thousands of domains in this configuration, this is an unreasonable effort. (See: https://support.plesk.com/hc/en-us/articles/360011198339)
There are already 3 feature requests regarding this issue:
- Add possibility issue Let's Encrypt SSL certificate for mail server when the "A" DNS record for domain is pointing to another server
- Use "Let's encrypt" to secure IMAP/POP/SMTP connections
- Issuing Let's Encrypt certificates for mail.domain.tld (to secure SMTP POP IMAP) without web-hosting enabled on the main domain.
Say there are many Plesk admins who are facing the same scenario ...
1) Can the problem be escalated to one of your PMs please? Possibly does he recognize the underlying problem and can force a solution?
2) Can the feature requests be combined? Currently the votes are split into 3 requests and will probably never get so high that Plesk does something here...
Thank you, best regards from Tyrol
Amdreas
currently there is the problem that the following scenario cannot really be mapped in a practical way:
- (www).dom.tld - is NOT pointing to Plesk Server
- mail.dom.tld - is pointing to Plesk Server
There is the problem that the certificate for mail.dom.tld has to be manually assigned to "dom.tld" for the mail services after each renew. With hundreds / thousands of domains in this configuration, this is an unreasonable effort. (See: https://support.plesk.com/hc/en-us/articles/360011198339)
There are already 3 feature requests regarding this issue:
- Add possibility issue Let's Encrypt SSL certificate for mail server when the "A" DNS record for domain is pointing to another server
- Use "Let's encrypt" to secure IMAP/POP/SMTP connections
- Issuing Let's Encrypt certificates for mail.domain.tld (to secure SMTP POP IMAP) without web-hosting enabled on the main domain.
Say there are many Plesk admins who are facing the same scenario ...
1) Can the problem be escalated to one of your PMs please? Possibly does he recognize the underlying problem and can force a solution?
2) Can the feature requests be combined? Currently the votes are split into 3 requests and will probably never get so high that Plesk does something here...
Thank you, best regards from Tyrol
Amdreas
