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 > /var/log/mail: > > > Oct 1 16:05:01 mail postfix/local[6371]: B9187115AC: > to=<[EMAIL PROTECTED]>, 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 > 2.1.1-91 > > > ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
