Re: mailman upgrade problem

2006-12-18 Thread Paul Schmehl
--On December 18, 2006 8:46:28 PM -0500 "Michael P. Soulier" <[EMAIL PROTECTED]> wrote: On 17/12/06 Paul Schmehl said: Apparently you're running Postfix. Is this problem unique to postfix? No. If you read the docs for mailman, you'll find that almost every mail server uses a different gr

Re: mailman upgrade problem

2006-12-18 Thread Michael P. Soulier
On 17/12/06 Paul Schmehl said: > Apparently you're running Postfix. Is this problem unique to postfix? > Put this in /usr/local/etc/pkgtools.conf, and you will never have this > problem again: > MAKE_ARGS = { ># Preset mailman so it will compile with the right group >'mail/mailm

Re: mailman upgrade problem

2006-12-17 Thread Paul Schmehl
--On December 16, 2006 10:07:27 PM -0500 "Michael P. Soulier" <[EMAIL PROTECTED]> wrote: I just did a portupgrade on mailman, and now it's doing this. Dec 16 22:05:27 kanga Mailman mail-wrapper: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "nobody", bu

Re: mailman upgrade problem

2006-12-16 Thread Michael P. Soulier
On 16/12/06 Michael P. Soulier said: > This is odd though, considering the wrapper program is group ownership > mailman, with the sgid bit set. > > Plus, if I change the group ownership to nobody, it complains about the > opposite. I had to build it this way to fix the issue. MAIL_GID=mailman

Re: mailman upgrade problem

2006-12-16 Thread Michael P. Soulier
On 16/12/06 Michael P. Soulier said: > I just did a portupgrade on mailman, and now it's doing this. > > Dec 16 22:05:27 kanga Mailman mail-wrapper: Group mismatch error. Mailman > expected the mail wrapper script to be executed as group "nobody", but the > system's mail server executed the mail

mailman upgrade problem

2006-12-16 Thread Michael P. Soulier
I just did a portupgrade on mailman, and now it's doing this. Dec 16 22:05:27 kanga Mailman mail-wrapper: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "nobody", but the system's mail server executed the mail script as group "mailman". Try tweaking the ma