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.
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.
I've not been able to get mine to work, either. Mailman does not create individual configuration files for each virtual host.
+1. It should also be possible to run Mailman under a subdomain other than lists.example.com
Has this been added to updates yet for Plesk?
Mailman should create individual configuration files for each virtual host. Thus, each instance can have its own SSL certificate.
Absolutely necessary and essential!
Fresh install - Let's see what shakes out. Previous attempts were close, but some of the admin pages still spit out errors for SSL. Shake a leg - I will submit an update.
Here are the settings that I've set but this does not work to have secure webpages.
In Plesk, go here: Tools & Settings / Mail / Mail Server Settings
In the Settings tab, go midway down to Mailman settings and check the box called "Use secure links in maillists"
With Let's Encrypt, you will need to use the wildcard certificate.
In the Customer, go to Host Settings / Mail Settings
In the Mail Settings tab, set both SSL/TLS fields to the domain's certificate.
Has anyone gotten this to work yet?
I found the check box. From the "Tools and Parameters" main menu, in the "Mail boxes" list then "Mail server parameters" there is a "Mailman parameter" with this checkbox. (because this is English translation, the menu labels could be a little bit different).
However, this function is not really useful, what we want is Let's Encrypt support.
Best Regards AR
I am also not understanding how the 18.0.31 update changes anything. I don't see an extra checkbox in Mail Settings for HTTPS links.
This only works if the Mailman lists are using the primary server domain. All other domains on the server using Mailman will fault because this solution does not pull the individual domain's SSL certificate into use. It only pulls the primary domain SSL certificate. If there is something that I am missing, please do let me know. Also is there documentation on how this should work.
I am happy to see progress on this issue.
Alexander Yamshanov commented
Previously all emails generated by Mailman contain HTTP links to a Mailman web interface. Now it could be configured in Plesk. If you tick a new checkbox in the domain mail settings in Plesk, Mailman will create emails with HTTPS links inside.
With the 18.0.31 Obsidian Plesk release, we can see in the Changelog description the following "Mailman links are now served via HTTPS." I don't understand what this means because I can't see any change. Has someone known the meaning?
Thanks you, AR
User of Mailman commented
I also use mailman, and obviously as on all of my pages I want to enforce https. I would really apprechiate, if that could be possible soon. It causes me a lot of trouble with my mail list users, who now think that mailman is not save to use.
Edward Hasbrouck commented
Yes. This is essential for any Web service.
Does anyone know if CPanel encrypts their implementation of Mailman? If so, then Plesk will follow suit.
Here's to hoping that Plesk will someday become the leader rather than the follower.
Alex Presland commented
Let's Encrypt now supports wildcard certificates on Plesk, so there is no good reason why the mailman interface shouldn't be able to be secure too.
You offer a Webpage Tool without https?
How can this be a discussion? Properly protecting webtraffic is standard nowadays!
Users are trained to only access secure pages and mailman isn't one?!
When enabling HSTS with the new SSL It! Extension (https://www.plesk.com/extensions/sslit/), this is also applied to mailman interface, but since it uses an invalid certificate this site is no longer reachable!
>We will consider this functionality in upcoming releases if it will be popular.
How can this be a question at all?
GDPR/DSGVO requires https if there is any exchange of personal data via the web.