I'm sorry, but I'm not a Plesk employee.Testing new Mailman3 integration on Plesk Obsidian Version 18.0.60, on Debian 12:
Dear @IgorG Please improve Plesk and Mailman/Let's encrypt integration.
We manage DNS on another server and can not use wildcard LetsEncrypt certificates:
make it so lists.<domain> can have have its own LE TLS certificate like webmail.<domain> does.
You can issue a separate Let's Encrypt certificate for any subdomain that is routed to the server. What exactly does not work for you here?We manage DNS on another server and can not use wildcard LetsEncrypt certificates:
make it so lists.<domain> can have have its own LE TLS certificate like webmail.<domain> does.
If not can I add that as an feature request?
I tried that, and then on my server the list name becomes [email protected].You must name your domain correctly from the start. If your domain is hosted elsewhere, you would not add the domain to the Plesk installation. If you know that you name your domain lists.<domain>, then you add lists.<domain> as your domain name, not your main domain name that is hosted elsewhere, because only lists.<domain> is hosted locally. Then you can issue a cert for that lists.<domain>.