I had to modify the ebuild to make mailman running. Without that, it always returned an error message as shown bellow. Reproducible: Always Steps to Reproduce: 0. Having postfix installed 1. emerge mailman-2.1.1 2. emerge mailman-2.1.1-r3 3. bring up your archives, make your change in the apache configuration 4. run a bin/check_perm -f (to be sure of what you've done) 5. try to send a mail on one of your mailing-lists Actual Results: Command died with status 2: "/home/mailman/mail/mailman post [list]". Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "daemon", but the system's mail server executed the mail script as group "nobody". Try tweaking the mail server to run the script as group "daemon", or re-run configure, providing the command line option `--with-mail-gid=nobody'. Expected Results: The mail would be sent to every folks who has subscribe to the list. I have replaced the line : -- MAILGID="daemon" -- of the ebuild by : -- MAILGID="nobody" -- and remerge mailman. Now everything is running well... and my users are happy ;c)
Sorry to stick you with yet another mailman bug, Todd, but we don't really have anyone else for it...
What mail agent are you running?
SMTP: postfix MTA: uw-imapd MUA: squirrelmail But the pb seems to come when we send the message, not when we recieve it. And I think that mailman is only "speaking" w/ the SMTP server, isn't it ? It doesn't have any "contact" w/ the MUA... :c/ But however, you have the requested information ;c)
This problem has to do with how each mail package runs as a different uid, it will be fixed asap.
