That's what I did, but it didn't work. Nor did chgrp nogroup.

- Mark
"Too much sanity may be madness! But maddest of all -- to see life as it is and 
not as it should be."


-----Original Message-----
From: mouss [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 9:34 AM
To: Mark A. Olbert
Cc: postfix-users@postfix.org
Subject: Re: mailman integration question

Mark A. Olbert a écrit :
> Thanks to mouss and others for helping me figure out how to configure postfix 
> and amavisd to route mail to different endpoints based on whether the address 
> is in a subdomain.
>
> I'm running into a GID problem in the interface between mailman and postfix. 
> Here's the error message:
>
> (Command died with status 2: "/usr/mailman/mail/mailman post mailman". 
> Command output: Group mismatch error.  Mailman expected the mail wrapper 
> script to be executed as group "mailman", but the system's mail server 
> executed the mail script as group "nogroup".  Try tweaking the mail server to 
> run the script as group "mailman", or re-run configure,  providing the 
> command line option `--with-mail-gid=nogroup'.)
>
> In googling the problem I came across one purported solution which involved 
> simply creating a separate aliases file for mailman aliases, whose group 
> ownership was set to mailman. That didn't work, nor did setting the separate 
> aliases file's group ownership to nogroup.
>
> Before I go in and reconfigure mailman I thought I'd check here and in the 
> mailman users group to see if anyone had any other alternative solutions.
>

Put mailman aliases in their own file and make it belong to the right
uid:gid.

alias_maps =
        # adjust path to system aliases
        hash:/etc/aliases
        # mailman aliases
        hash:/etc/postfix/mailman_aliases

# postalias hash:/etc/postfix/mailman_aliases
# chown mailman:mailman /etc/postfix/mailman_aliases



__________ Information from ESET NOD32 Antivirus, version of virus signature 
database 3677 (20081209) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com



__________ Information from ESET NOD32 Antivirus, version of virus signature 
database 3677 (20081209) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Reply via email to