[Mailman-Users] RE: mailman-2.1-1.i386.rpm (Group mismatch)

[Parker, David K]

Ok, I figured out you cannot copy the mailmanctl script to the init.d
directory. This is why mailmanctl failed to start. But, I have another
stumbling block. Messages are rejected with the following:


<test1-request at mailgate.ci.bryan.tx.us>: Command died with status 2:
    "/var/mailman/mail/mailman request test". Command output: Group mismatch
    error.  Mailman expected the mail wrapper script to be executed as group
    "mail", but the system's mail server executed the mail script as group
    "nobody".  Try tweaking the mail server to run the script as group
"mail",
    or re-run configure,  providing the command line option
    `--with-mail-gid=nobody'.


-----Original Message-----
From: Parker, David K 
Sent: Tuesday, January 28, 2003 5:02 PM
To: 'mailman-users at python.org'
Subject: mailman-2.1-1.i386.rpm


I've been fighting problems after upgrading Mailman 2.0x to 2.1-1 using
mailman-2.1-1.i386.rpm. I'm making headway but now mailmanctl terminates
with the following error:

# /etc/rc.d/init.d/mailmanctl start
Traceback (most recent call last):
  File "/etc/rc.d/init.d/mailmanctl", line 104, in ?
    import paths
ImportError: No module named paths

I'm thinking that something strange is happening with Python. Python
versions 1.5x and 2.2x are installed. I noticed Mailman requires Python 2.x
to run. (Interstingly enough, mailman-2.1-1.i386.rpm reports to require
python and not python2.) I have packages that require both versions of
Python. If I run "python -V" it indicates version 2. I'm almost at a point
where I've either got to scrap mailman completely and revert to an earlier
rpm or install clean from source. Any suggestions would be appreciated.