SSL for Mailman Admin/User Logins

Now that SSL is the standard for accessing webpages, especially login pages, when is cPanel going to allow Mailman to FULLY allow secure access? I continually have clients coming to me asking for SSL connections to their Mailman admin pages. No matter what I try, I can't seem to find a permanent fix. I have done the following:

1. Added a redirect to direct all non-ssl traffic to /mailman/ to https. That works great.

RewriteEngine on
RewriteCond %{HTTPS} off [NC]
RewriteRule ^/mailman(/.*) https://%{HTTP_HOST}/mailman$1 [L,R=permanent

2. Added the following to the mm_cfg.py file for new lists:

DEFAULT_URL_PATTERN = 'https://%s/mailman/'

3. Ran the following for an older list that was unable to make changes to members' attributes on the membership management page due to the above changes:

$prefix/bin/withlist -l -r fix_url listname -u list_web_domain

I confirmed that fixed the issue only to see the fix revert itself less than 24 hours later. So even though web traffic is coming through via SSL, it seems certain form elements are not fully secure. This really needs to be fixed cPanel and that asap.

Thank you,
Brian

 

The problem is not all users particularly list members uses https so there should be some sort of force redirect in place. But the real problem is that for virtual host certificates, some of the form elements do not work properly. I confirmed this on the membership management page when you try to go make some adjustments to a list member settings including adding a real name. It works fine if https is over the hostname of the server but not over the virtual host's certificate.

 

I think this appears when you try to disable a non-ssl access to a mailman list. The issues do not show up if I allow both SSL and non-SSL access to a list's admin pages. However when I try to force SSL only access to list admin pages, these issues show up. I believe some of these form elements are using a non-SSL connection to function and when you try to force SSL only access, then something is not working right.

 

Then how come there are non-SSL resources being called when viewing the source html even though the main connection is via SSL?

The original need for the redirect is to prevent users from using a non-SSL connection to access Mailman, this includes the list info page.

Brian