Question Letsencrypt and mailman

[WielM]

I added mailman to one of my domains. Doing so creates a url called lists.my.domain. This url does not show up in the domain's subdomain overview. The domain uses a LetsEncrypt certificate to get https support. The certificate has wildcard set, but 'lists.my.domain' does not use it. The Digicert Certificate Installation checker shows that lists uses "Subject: E=[email protected], CN=Plesk" in stead of my subdomain name. When I try to access lists.my.domain/mailman/admindb/<listname> the browsers says:

Your connection is not private​

and the https is not valid. It doesn't even let me enter the mailman site.

How can I secure the Mailman pages with the Letsencrypt certificate of the main domain?

Plesk Obsidian on Ubuntu 18.04.4 LTS

 

[Alex Presland]

There is an existing feature request in for this... I suggest that you up-vote this:

Add Mailman support to Let's Encrypt

Please add Mailman support to Let's Encrypt. Ideally, one could issue either a certificate directly for lists.domain.com or a wildcard certificate for *.domain.com. Furthermore, a secure connection should be enforceable. Thanks!

plesk.uservoice.com

There's an existing user solution, but I'd much rather that Plesk implement something that works for all and is supported. This is a level or two of messing about with server configuration above where I'm prepared to play.

Resolved - SSL Certificate for Mailman

Situation: I want to embed a SSL certificate for mailman permanently in the server.conf file. For Roundcube i've found a manual: https://struband.net/ssl-zertifikat-fuer-roundcube-in-plesk-12/ (in German), but not for Mailman.

talk.plesk.com