MailMan Server 500 Error.

[techid]

Redhat 7.3 system, clean install of cPanel, with SuExec enabled (and do not want to disable.) (If I were to disable it, it does work perfectly fine, but like I said I would like to keep it enabled.)

Clients are able to create new lists, but are unable to edit them.

Came here, searched, found &use /scripts/fixmailmanwithsuexec& so I tried that, it did it's little &Found myserver.mydomain.com with responds to ip.ip.ip.ip& routine... but still get the 500 Internal Errors..

Then I tried the rename mailman DIR then run /scripts/upcp and let CPanel reinstall it, still no luck.

I look at /home/apache/logs/suexec_log, and it's got a &Directory Is writable by others!& So I change the permission to 755, no luck, now I get '[2002-08-04 23:07:33]: error: file is either setuid or setgid: (/usr/local/cpanel/3rdparty/mailman/cgi-bin/admin)'

When I look at the Apache error log I get, '[Sun Aug 4 23:07:33 2002] [error] [client x.x.x.x] Premature end of script headers: /usr/local/cpanel/3rdparty/mailman/cgi-bin/admin'

If anyone else has any ideas please let me know.

Thank you,
Timothy Sheehan

[(SH)Saeed]

Anyone have a solution to this problem? We've also tried running all the different related /scripts/fix* scripts and still no luck.

[(SH)Saeed]

Anyone?

[2002-08-10 14:04:04]: info: (target/actual) uid: (user/user) gid: (user/user) cmd: admin
[2002-08-10 14:04:04]: error: directory is writable by others: (/usr/local/cpanel/3rdparty/mailman/cgi-bin)

Is the only option to disable suExec?

[(SH)Saeed]

*bump*
Noone else is having problems with this? Anyone kind enough to tell me what permission and owner/group you have on the directory &usr/local/cpanel/3rdparty/mailman/cgi-bin&..

Thank you.

[(SH)Saeed]

By the way, I've tried running both /scripts/fixmailmanwithsuexec and /scripts/fixoldlistswithsuexec and still the same problem.

[techid]

As stated, I as well have done the same, but still no go.

[(SH)Saeed]

I finally got the suExec problem solved after hours of research through the web and now this is what I get..

[quote:1b19cf57b0]Bug in Mailman version 2.0.11

We're sorry, we hit a bug!

Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.[/quote:1b19cf57b0]

So I check the Apache error file and this error is like 60 lines. Here are the important part:

[quote:1b19cf57b0][----- Mailman Version: 2.0.11 -----]
[----- Traceback ------]
Traceback (innermost last):
File &/usr/local/cpanel/3rdparty/mailman/scripts/driver&, line 71, in run_main
immediate=1)
File &/usr/local/cpanel/3rdparty/mailman/Mailman/Logging/StampedLogger.py&, line 49, in __init__
Logger.__init__(self, category, nofail, immediate)
File &/usr/local/cpanel/3rdparty/mailman/Mailman/Logging/Logger.py&, line 40, in __init__
self.__get_f()
File &/usr/local/cpanel/3rdparty/mailman/Mailman/Logging/Logger.py&, line 55, in __get_f
f = self.__fp = open(self.__filename, 'a+', 1)
IOError: [Errno 13] Permission denied: '/usr/local/cpanel/3rdparty/mailman/logs/error'
[----- Python Information -----]
sys.version = 1.5.2 (#1, Jul 5 2001, 03:02:19) [GCC 2.96 20000731 (Red Hat Linux 7.1 2
sys.executable = /usr/bin/python
sys.prefix = /usr
sys.exec_prefix= /usr
sys.path = /usr
sys.platform = linux-i386
[----- Environment Variables -----][/quote:1b19cf57b0]

At the end there are lots of lines with all the environment variables. Anyone?

[(SH)Saeed]

[quote:12c7bd9faa][i:12c7bd9faa]Originally posted by techid[/i:12c7bd9faa]

As stated, I as well have done the same, but still no go.

[/quote:12c7bd9faa]

This is what I did. Make sure both the cgi-bin directory and the files in it are chmod 755 and not 775. Then make sure that the account mailmain is run on is set to user/group nobody. Hopefully, you will have better luck than me and that will fix your mailman problems.

[(SH)Saeed]

For anyone that cares to know, these issues seem to have been solved with the build 62 update.

[LinuxFreaky]

I'm running into this exact problem through suexec and here's my WHM version:
WHM 5.3.0
Cpanel 5.3.0-R68
RedHat 7.2

On another server I have Redhat 7.3 and don't have this problem at all.

When I run it I got:
[2002-12-03 10:34:33]: error: directory is writable by others: (/usr/local/cpanel/3rdparty/mailman/cgi-bin)

Then I did a chmod 2755 on /usr/local/cpanel/3rdparty/mailman/cgi-bin.

After that I ran the script and got:

[2002-12-03 10:36:40]: error: file is either setuid or setgid: (/usr/local/cpanel/3rdparty/mailman/cgi-bin/admin)

What do I do now? Is there a fix for this?

[bdraco]

Use the latest buildapache.sea. It will patch httpd to work properly with mailman+suexec.

[chakky]

Hi,

tried the enabling of the server with suexec and this caused all mailing lists to be accessed only by the http://servername/mailman/
rather than the domain name

Following Nick's advice, I tried the latest buildapache (Nov 30 updated) and then tried creating new lists to see if it would work and it did not resolve it.

Seems like my only option is to disable suexec for clients who need mailinglist accessible by their domain name.This is done
by changing the user and group in their virtual host entry to nobody and restarting httpd.

The problem then, is that their frontpage shows some errors and I will have to reinstall that also for the domain.

Any other possible workaround??
Anybody....

[Admin356]

This isn't a cpanel problem (Maybe).

Did you move the mailman directories to /home too ?

It could be because the usr directory or directories below it were under the / partition originally and you moved them to the /home partition?

The link to usr or mailman now doesn't comply with suexec rules, as it is world writeable.

[chakky]

Hi,

I have done nothing of the sort.This comes in randomly from the clients.I just remove suexec each time for the users if they admanantly want this done..which is a security issue.

FYI..most of these domains were moved before suexec was enabled for mailing lists from another server where suexec was not enabled...but then again quite a few of them were on the server and yet encounter this...

[NNNils]

I have the same on a server with 6.0 S88