These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for lost Mailman on the new forum.
Web Hosting and Cloud Computing Control Panels
Found the plug-in to deselect mailman and turned it off since I don't use it. But still wondering why the configure fails when all the structure is in place since all the other boxes are fine.
I think our mailman configuration is still wrong for CentOS--I thought it was only wrong for CentOS 3, but maybe things have shifted on CentOS 4 (that would be a bug on the part of CentOS or RHEL, since they are supposed to be "stable" platforms, but we still catch the flack from the change).
I'll have a look.
--
Check out the forum guidelines!
Looks like this still needs a look; Having the same problem on CentOS 4.6/virtualmin 3.5
[code:1]
Failed to save enabled features : The plugin Mailman cannot be used : The mailman program /usr/lib/mailman/bin/mailman was not found on your system.
[/code:1]
For other CentOS users, this configuration fixed the error; I haven't tried actually creating a mailman acct yet:
(go to Virtualmin -> System Settings -> Features and Plugins, select "Configure" to the right of "Mailmain")
[code:1]
Mailman base directory: /usr/lib/mailman
Mailman data directory: /var/lib/mailman
Full path to mailman command: /usr/lib/mailman/bin/mailmanctl
[/code:1]
CentOS
Full path to mailman command: /usr/lib/mailman/bin/mailmanctl
<b>is actually wrong</b>, as was pointed out to me after a support request. With that setting users were unable to send list messages that were being bounced.
The correct path is:
[code:1]/usr/lib/mailman/mail/mailman[/code:1]
afterwhich the system works as it should.
Regards,
Cyrus