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!
Florian
shared this idea
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— rk
-
Benjamin Rodriguez commented
This is urgent!
-
Frank
commented
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
-
Patrick
commented
I guess nothing is planned, as Plesk will kick mailman support at all...
-
Abd El Hamid commented
Is there anything planned? How many Votes are needed to get any attention?
-
Alexis Garcia commented
Urgent!
-
Frank
commented
Does anyone know if Mailman SSL works on other control panel platforms?
-
concedra
commented
Please implement this important feature
-
Jürgen
commented
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 -
Conrad Noack commented
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
-
Nick Pronin commented
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.
-
Paul
commented
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?
-
Peter Miller commented
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)
-
Paul
commented
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.
-
Tammy Mitchell
commented
I also would like this feature added. Thank you
-
Anonymous
commented
It's incredibly frustrating to not have appropriate SSL certificate support for Mailman in Plesk. Please add the ability.
-
Anonymous
commented
I've not been able to get mine to work, either. Mailman does not create individual configuration files for each virtual host.
-
Anonymous
commented
+1. It should also be possible to run Mailman under a subdomain other than lists.example.com
-
Darren
commented
Has this been added to updates yet for Plesk?
-
Anonymous
commented
Mailman should create individual configuration files for each virtual host. Thus, each instance can have its own SSL certificate.
-
Anonymous
commented
Absolutely necessary and essential!