When running mailman under sendmail, mailman expects to be running under group mailman. but sendmail uses smrsh and this (or sendmail itselfs) seems to sets the group to devel (and do not care if group-set,... is set). Solution is to set group within the ebuild-file to 2 (=devel) and rebuild mailman "manualy". Beneath: sendmail/smrsh needs the link mailman -> /usr/local/mailman/mail/mailman set in the directory /usr/adm/sm.bin to be able to call mailman. Reproducible: Always Steps to Reproduce: 1. emerge sendmail 2. emerge mailman 3. follow the steps given by mailman-install-howto and nothing worked
I am having the same problem. I am working on it. I've yet to try to build it manually, but that may be the next step. Is there a way that the mailman ebuild can detect the MTA and set the MAILGID appropriately? It seems that it has to be setup differently for different MTAs.
A previous bug report, 19257, configured the mailman ebuild to use the 'daemon' group when sendmail was the mta. My problem is that my install of sendmail seems to run in the 'mail' group. This is not set in the sendmail ebuild.
What I have done is to create a dirrectory: /usr/local/portage and added: PORTDIR_OVERLAY="/usr/local/portage" to make.conf. I then coppied: /usr/portage/net-mail/mailman to: /usr/local/portage/net-mail/mailman I then edited the ebuild, to change the: MAILGID="280" to: MAILGID="2" then did a: md5sum mailman-2.1.5-r4.ebuild >> Manifest and then moved and edited that line, to match with the format of the other lines in the Manifest file, and removed the existing line for that ebuild. Then all I had to do was do an: emerge -a mailman and since I have it working fine. I also made a similar change when I changed over to courier MTA. Jessica
Same problem here with courier MTA. The mailman ebuild is configured with --with-mail-gid=280, which is the 'mailman' group. Courier, and I expect many mail servers in gentoo, operate with a gid of 12, or 'mail'. The mail system gid should either be auto-detected or set to 12 in the ebuild. The gid 280 is the file ownership group for the mailman filesystem and group identity of the mailman user in /etc/passwd, but this doesn't generally, nor should it necessarily correspond to the gid of the running MDA. Although courier allows one to set the uid and gid of the mail delivery agent on a per-user/per-delivery basis, a feed to mailman is often done using a default configuration for which no explicit user is known. The default gid for courier/maildrop is 12, 'mail'. Changing the value of MAILGID in the mailman ebuild script from 280 to 12 solved the problem. I suggest that even if all MDA's don't run with this effective gid, it's a better choice than 280.
From what I can see, this has already been fixed, just forgotten to close the bug.