Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 30627 - mailman --with-cgi-gid error in ebuild
Summary: mailman --with-cgi-gid error in ebuild
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Net-Mail Packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-07 21:04 UTC by Chris Verges
Modified: 2007-05-04 11:29 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
fixed ebuild with proper APACHEGID line (mailman-2.1.2-r1.ebuild,3.60 KB, text/plain)
2003-10-07 21:05 UTC, Chris Verges
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Verges 2003-10-07 21:04:00 UTC
The default mailman 2.1.2-r1 assumes the --with-cgi-gid (set in the ebuild to
variable APACHEGID) is a hardcoded 81 rather than the group name "nobody".  On
some Gentoo systems, the group "nobody" corresponds to gid 65534, not 81.  To
fix this problem, the following APACHEGID line should read:

   APACHEGID="nobody"

Reproducible: Always
Steps to Reproduce:
0. Set your nobody gid to anything BUT 81
1. ACCEPT_KEYWORDS="~x86" emerge mailman
2. Setup mailman according to the README.gentoo.gz file
3. Add a mailing list with at least one recipient
4. Send a message to the mailing list
5. Receive error message from postfix/mailman.
Actual Results:  
Postfix/Mailman returned a message similar to this:

<security@headnut.org>: Command died with status 2:
    "/usr/local/mailman/mail/mailman post security". Command output: Group
    mismatch error.  Mailman expected the mail wrapper script to be executed as
    group "mailman", but the system's mail server executed the mail script as
    group "nobody".  Try tweaking the mail server to run the script as group
    "mailman", or re-run configure,  providing the command line option
    `--with-mail-gid=nobody'.

Expected Results:  
The message sent to the group should have been sent correctly.
Comment 1 Chris Verges 2003-10-07 21:05:57 UTC
Created attachment 18928 [details]
fixed ebuild with proper APACHEGID line
Comment 2 Narada Sage 2003-10-08 17:29:12 UTC
I had this problem but in my case I had to set MAILGID="nobody" to fix it.
 By the way, the attached ebuild has APACHEGID="81" rather than what you
intended APACHEGID="nobody".
Comment 3 Chris Verges 2003-10-08 18:45:13 UTC
Ah, yes ... Sorry.  I forgot I had done an rsync prior to submitting this.
 Anyway, yes, I think the ebuild should reflect what the other packages do
in their base installs.  So if apache runs as nobody, then mailman should
run as nobody.  etc.  Just brings more uniformity to the situation.
Comment 4 Martin Holzer (RETIRED) gentoo-dev 2004-01-06 15:13:52 UTC
gentoo default is

apache:x:81:81:apache:/home/httpd:/bin/false
and apache runs as apache
Comment 5 Steven Green 2007-05-04 11:29:04 UTC
(In reply to comment #4)
> gentoo default is
> 
> apache:x:81:81:apache:/home/httpd:/bin/false
> and apache runs as apache

For historical reasons, the gid for apache is not 81 on my system.  But it builds if I edit the ebuild to read:

APACHEGID=apache

Is there any reason why the ebuild can not be changed to use "apache" instead of the hard coded "81".

I have a similar problem with MAILGID using sendmail.  I have to change it from "daemon" to:
MAILGID=mailnull.