• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/

Question SSL domains Mailman

raematrix

New Pleskian
Server operating system version
AlmaLinux 8.10 (this also applies to all OS versions)
Plesk version and microupdate number
Obsidian 18.0.74
There has been a long time issue with Mailman and the Let's Encrypt SSL in that it doesn't cover the "https://lists.domain.com" address. Honestly, why not? The certificate is able to cover "www", "webmail", "mail", and any CNAME that we assign to the domain and add it to the Domains section. Why is it not capable to recognize that there are Mailman lists in the customer's account and allocate the "lists." into the SSL coverage? If you try to add "lists.domain" to the Domains section, it won't allow it stating that it is already used. So if that is recognized, why not also for the SSL? I would imagine that it shouldn't be that difficult for Plesk to add this to the code. Can anyone, preferably at Plesk, explain why this is not being done?
 
Back
Top