• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue LE Certs for mail.dom.tld when Plesk is only serving Mail Only Services

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
 
We actually have this on our roadmap with features we'd like to release. Development hasn't started yet and there is no ETA on this (it might be a while).
 
@TRILOS new media you may want to have a look at the script we are using to overcome this massive problem until Plesk fixes it in about 15 years ...
 
Back
Top