Ability to completely and permanently remove Mailman [Case 30562]

[FreedomNet]

We have unchecked "Mailman" in WHM's Tweak Settings but mailman still appears to be active. For instance, if you go to http://www.domainname.com/mailman/admin/YourListName you will get a mailman greeting screen that indicates "YourListName" is not a valid mailman list and links to how to create a list and the version of mailman running/installed.

Does anyone know what the mailman check in WHM really does and more to the point does anyone know how to really disable mailman?

[shashank]

If you uncheck that , I guess /mailman alias from httpd.conf still remains. To totally disable mailman, I think you should remove /mailman alias from httpd.conf and chmod /usr/local/cpanel/3rdparty/mailman/lists to 000 to prevent creation of new lists.

[FreedomNet]

remove /mailman alias from httpd.conf

Works great, thanks!

[pavemen]

If you uncheck that , I guess /mailman alias from httpd.conf still remains. To totally disable mailman, I think you should remove /mailman alias from httpd.conf and chmod /usr/local/cpanel/3rdparty/mailman/lists to 000 to prevent creation of new lists.

I know this is really old, but in the current and stable version of WHM at this time (11.15.0) doing the chmod mentioned above breaks inbound mail. Leaving it chmod 755 lets inbound come in and Exim is checking senders from the mailman lists, even though its turned off in WHM and removed from httpd.conf. This is the default Exim configuration on a new box with Spamassassin enabled. No MailScanner

Since I found this thread trying to disable mailman, thought I'd update it

[Vatoloco]

Is there any way to keep mailman disabled? I've unchecked it in WHM under tweak settings, removed all the mailman lines in httpd.conf and removed the mailman crontab entries.

It will stay disabled for awhile but, more often than not, the cPanel update every night will re-enable it all, adding back the httpd and cron entries.

[cPanelDavidG]

Is there any way to keep mailman disabled? I've unchecked it in WHM under tweak settings, removed all the mailman lines in httpd.conf and removed the mailman crontab entries.

It will stay disabled for awhile but, more often than not, the cPanel update every night will re-enable it all, adding back the httpd and cron entries.

I recommend submitting a support ticket so our technical analysts can take a look at that for you: http://tickets.cpanel.net/submit

Anything set in the WHM typically should remain unchanged between updates.

[surfalot]

Again, I know this is an old post, but same issue here.

What does "mailman" check in Tweak Settings really do?

And better yet, is there a way to simply disable it without a trouble ticket and the necessity of going back in to remove the aliases periodically?

[cPanelDavidG]

Again, I know this is an old post, but same issue here.

What does "mailman" check in Tweak Settings really do?

And better yet, is there a way to simply disable it without a trouble ticket and the necessity of going back in to remove the aliases periodically?

Our developers are currently in the process of improving this functionality so when you disable mailman, it truly stays disabled and mailman-related entries in exim.conf are removed. (Internal Case 30562)

[merlinpa1969]

any news on this,
having to go in and manually REMOVE mailman after every update is not working for us anymore and PCI scans are failing because of this

there needs to be a way to completly DISABLE mailman and have it stay disabled

[cPanelDavidG]

any news on this,
having to go in and manually REMOVE mailman after every update is not working for us anymore and PCI scans are failing because of this

there needs to be a way to completly DISABLE mailman and have it stay disabled

This case is still being worked on, I have no ETA on when this will be resolved.

[safitech]

I can confirm this is starting to get to be a major issue having to redo the httpd.conf everytime there is an update because mailman is not fully removed from exim nor the httpd.conf even when the box is unticked within the Tweak settings.

Small note as well... you might want to add in a .htaccess with "Options -Indexes" into the /img-sys/ folder located at /usr/local/cpanel/img-sys/ as a default across all versions/installations of cPanel. This should not effect anything at all, but is something that comes up with all PCI scans.

[surfalot]

I havn't seen anyone suggest this, but seems to work for me. The real question is will this be broken by a cPanel security update or other.

since it is a virtual directory running through the apache server why not just put a .htaccess file in the folder with the scripts?

/usr/local/cpanel/3rdparty/mailman/cgi-bin/

the .htaccess file:

<Limit GET POST>
order deny,allow
deny from all
</Limit>

<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>

[topshapenick]

Any updates to solving this issue with disabling mailman? This is stalling our PCI compliance and I cannot figure out how to permanently get rid of it.

[topshapenick]

My PCI compliance test is failing b/c of mailman. I do not use it and just want to remove it. I am unable to find which virtual host file it's defined in and I've spent hours on this issue trying to find a solution to no avail. Please advise.

[madaboutlinux]

What does the PCI scan reports on mailman? If you could paste the report for mailman, it will help people here to provide you the solutions immediately.

Well, here is the solution:

1) You can disable Mailman from
WHM >> Tweak Settings >> Mail
OR
/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl stop

2) Remove OR comment the following lines in the Apache configuration file and restart the httpd service

Alias /mailman/archives /usr/local/cpanel/3rdparty/mailman/archives/public/
Alias /pipermail /usr/local/cpanel/3rdparty/mailman/archives/public/
ScriptAlias /mailman /usr/local/cpanel/3rdparty/mailman/cgi-bin/