[Mailman-Users] Failure to exec script
merle.reine at lindows.com
Thu Oct 2 04:07:48 CEST 2003
Good info. However, I found a post via Google that resolved the problem.
It appears that on SuSe, when you run SuSEconfig after setting up mailman
(which you must do), it sets a file in /etc/mailman.mail-gid and puts
:65533 in the file. Once I changed the file contents to :67 then mailman
is now working correctly. Perhaps make a note to add to documentation for
mailman if running SuSE 8.2 and up, that this is the case. As mailman
runs as gid 67 by default and SuSE sets it to 65533 (nobody) by default,
therefore the error.
Thanks for all the help.
On 01 Oct 2003 21:08:45 -0400, Jon Carnes <jonc at nc.rr.com> wrote:
> Looks like you've got some security sub-program running on boot that
> checks and resets the system rights on certain files. Check the aliases
> file that contains your Mailman aliases and make sure that it's group
> rights are set properly.
> Good Luck - Jon Carnes
> BTW: Mandrake's msec does something similar and is kicked off via cron
> so you don't even need to reboot for it to happen.
> On Wed, 2003-10-01 at 18:59, Merle Reine wrote:
>> Mailman has been working fine finally until I rebooted. No files were
>> modified but now when sending to a list, the following error is in
>> Oct 1 16:05:01 mail postfix/local: B9187115AC:
>> to=<staff at mail.lfriendly.com>, relay=local, delay=0, status=bounced
>> (Command died with status 2: "/usr/lib/mailman/mail/mailman post staff".
>> Command output: Failure to exec script. WANTED gid 65533, GOT gid 67. )
>> Mailman user is gid 67 and user nobody is gid 65533. I ran check_perms
>> and permissions are correct on all the files.
>> Any ideas? This is installed via rpm on a SuSe system. Mailman version
Lindows.com Hardware Certification Specialist
More information about the Mailman-Users