I'm using Plesk Obsidian and the mailman support is pretty useless if my clients get a certificate warning. Please add support for valid CA-issued (LE) cerificate for the lists subdomain. Thanks!

Need this...

Please make it possible to generate a standalone LE certificate for lists.(domain) as you did for webmail.<domain>
This is critical for our transitioning to hosting Mailman 3 on Plesk Debian 12.

Thank you!

If somebody is able to write a terminal script to automate the process mentioned in my previous comment, that would be awesome! We could run it as a cron job and would have a self-made implementation. If the plesk-team does not provide us with a solution we could make it ourselves.

So, another try since my first comment is not available anymore...

The following workaround works for me and I can secure the subdomain from mailman 'lists.my-domain.com' with my Lets-Encrypt certificate from my main domain.
This workaound might only work in single domain setups.

1. Secure your domain with a Let's Encrypt certificate (or any other of your choice, should also work). Make sure, it is a wildcard certificate (securing *.my-domain.com)
2. Open the details of your certificate. In my German plesk variant it is under 'Websites and Domains' - 'SSL and TSL certificates' - 'Erweiterte Einstellungen' (Advanced Settings maybe?) - click on your certificate - You'll see the page with your private key, the crt and the ca-crt
3. Open a new tab and goto 'Tools and Settings' - 'SSL and TSL certificates' - click on '+ Add' and paste the private key, the crt and ca-crt in the corresponding inputs
4. make the newly added cert the default

That is it.

The caveat is that you have to repeat this process whenever your domain certificate expires...

Hello Plesk Staff Admins! What happened to my comment? I posted a workaround for this issue...
Why did it disappear?

Is Plesk actually going to do anything about this or is this just a placeholder to make us think that maybe you might? This is critical and web services are being affected by it not meeting security compliance.

This is urgent!

Does anyone know if a work-around can be implemented based on this page: https://support.cpanel.net/hc/en-us/articles/4403947036439-How-to-force-Mailman-to-use-SSL

I guess nothing is planned, as Plesk will kick mailman support at all...

Is there anything planned? How many Votes are needed to get any attention?

Urgent!

Does anyone know if Mailman SSL works on other control panel platforms?

Please implement this important feature

After more than 4.5 years nothing has happened, I find it sad that such a fundamentally important feature is not implemented.
SO PLEASE, implement this important feature

I'd also vote for this. For someone who knows the plesk vhost / server config templating language this cannot take more than an afternoon to implement.

For someone without a test environment and without a good knowledge about the plesk config system, this takes much longer...

SO PLEASE, implement this

I use only SSL certificates from Let's Encrypt. This solution is installed on all my sites. I use monitoring https://www.host-tracker.com/en/ to quickly track domain and SSL lease terms so I don't forget to renew them.

Is there an exception somewhere in the code to not allow https for the mailing list URL? I've installed a wildcard Let's Encrypt certificate which should work but it doesn't.

It would be great if someone would actually come up with a solution instead of this dumb voting. BTW, if 253 votes is not enough to get this done, what number is enough?

Sorry guys! But this is a pain ********** - or is it a nagging to force buying a wildcard cert (or migration external DNS to Plesk DNS which is in some configurations the worst solution to do)

How many years do we have to beg for this? It seems like it is just a coding issue that Plesk should easily be able to handle. Since wildcard certificates are issued and working for people, then the lists.domain URL should be included in that.