OK. Further searching turned up the FAQ pasted below from the Mailman
community FAQ, the gist of which is I have to recompile Mailman to
run as the required GID.

Has anyone else had to to do this or found another solution?

Thanks!

- Ken

Mailman FAQ Search Results
Your search matched the following entry: 
--------------------------------------------------------------------------------

1.4. Failure to exec script. WANTED gid 0, GOT gid 12.
NOTE: This is the most common and frequest question asked on the
Mailman support lists. 
Have you ever gotten the following error message? 

The original message was received at Tue, 6 Nov 2001 16:27:56 -0500
from IDENT:[EMAIL PROTECTED] [127.0.0.1] 


   ----- The following addresses had permanent fatal errors -----

"|/home/mailman/mail/mailman_wrapper post test" 
    (reason: 2)
    (expanded from: <[EMAIL PROTECTED]>)

   ----- Transcript of session follows -----

Message delivered to mailing list <[EMAIL PROTECTED]> Failure
to exec script. WANTED gid 0, GOT gid 12. (Reconfigure to take 12?)
554 5.3.0 unknown mailer error 2 
Normally you will need to reconfigure the software. You can do this
by issuing the following commands in the Source Code directory. 


  # make clean

  # echo "NOTE: The following values for the GID's are example
          values.  The ones needed my your system will likely be
          different.  Check your MTA, web server configuration, and
          logged error messages for details and the correct values.

  # configure --with-cgi-gid=233 --with-mail-gid=12
  # make install

Sometimes this still does not solve the problem. In these cases, you
need to check the following for the source of the problem: 
For those people using Sendmail as their MTA under Mailman (not
generally recommended for performance reasons): 


  1. Does the smrsh directory contain a LINK to the actual Binary. 
Placing a Binary in the directory 

will have sendmail use the binary file, not the file which you are
compiling. 

  2. If you renamed the file (due to a confilict with Majordomo), are
you using a Link to the MailMan 

binary wrapper file? 

    [EMAIL PROTECTED] mail]# ls -l
    total 32
    lrwxrwxrwx    1 root     root           26 Nov  7 09:37
mailman_wrapper -> /home/mailman/mail/wrapper*
    -rwxr-sr-x    1 root     mailman     31000 Nov  7 09:39 wrapper*
    [EMAIL PROTECTED] mail]#

Edit this entry / Log info / Last changed on Tue Nov 27 18:16:55 2001
by J C Lawrence 

 
--- Ken <[EMAIL PROTECTED]> wrote:
> This appears to be the critical error:
> 
> Apr 15 12:21:13 delta Mailman mail-wrapper: Failure to exec script.
> WANTED gid 1, GOT gid 1003.  (Reconfigure to take 1003?)
> Apr 15 12:21:13 delta Mailman mail-wrapper: Failure to exec script.
> WANTED gid 1, GOT gid 1003.  (Reconfigure to take 1003?)
> 
> --- Ken <[EMAIL PROTECTED]> wrote:
> > I have read through the archives. DBMail and postfix are working
> > fine. I added mailman to the system and configured the aliases in
> > the
> > database for dbmail with the pipes to the mailman executables. I
> > added the aliases to the transport table in postfix. Mailman web
> > interface works properly.
> > 
> > However, email requests are not being processed.
> > 
> > Any ideas on what I might be doing wrong?
> > 
> > Thanks! I'm really impressed with the potential for dbmail.
> > 
> > - Ken
> > 
> > __________________________________________________
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo
> > http://search.yahoo.com
> > _______________________________________________
> > Dbmail mailing list
> > [email protected]
> > https://mailman.fastxs.nl/mailman/listinfo/dbmail
> 
> 
> __________________________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo
> http://search.yahoo.com
> _______________________________________________
> Dbmail mailing list
> [email protected]
> https://mailman.fastxs.nl/mailman/listinfo/dbmail


__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com

Reply via email to