[Mailman-Users] RE: Desperation time

John-David Childs jdc at nterprise.net
Thu May 13 18:03:12 CEST 1999

Yesterday I posted a question about why mail sent to a mailman mailing
list (or listowner) was going to the bitbucket with an error message
like "DSN Unknown Mailer Error 1" or "Operating System Error".

I theorized at first that it was my version of python (1.5.2b2?) 
and the fact that I'm using *BSD.  Upgrading to 1.5.2 final didn't help.

I also upgraded from mailman 1.0b9 to 1.0rc1.  Nope. Same problem.

Next, I theorized that my renaming of mailman's wrapper to "mmwrapper"
(to avoid conflicts with Majordomo's wrapper in my smrsh "sm.bin"
directory) might have triggered some hardcoded names in the mailman
scripts/sources.  Nope, that wasn't it either.

I was not getting any of the "wanted GID=XX, got GID=yy" errors from
wrapper common to other installations.  

I finally figured out a workaround, although I'm not happy at all with it.  
I had to install mailman's wrapper in the smrsh directory as root (the one
in the ~mailman/mail directory is owned by mailman.daemon).  I'm not
completely finished testing, but it looks like I have to set the SUID bit
too :(  This was necessary so that the wrapper program could assume what
ever priviledges it thought it needed.  Setting it to mailman.daemon with
the SGID bit set didn't seem to work.

So...do I have something else messed up in my installation?  I've never
seen anyone else complain that wrapper had to be root with smrsh (I'm not
sure if smrsh is the issue here or what).

John-David Childs (JC612)	Enterprise Internet Solutions
Systems Administration          http://www.nterprise.net
  & Network Engineering         8707 E. Florida Ave #814 Denver, CO 80231
You could get a new lease on life -- if only you didn't need the first
and last month in advance.

More information about the Mailman-Users mailing list