[gentoo-user] mailman 2.1.5-r4/sendmail issue with ``Group missmatch error.''

[gentoo-user] mailman 2.1.5-r4/sendmail issue with ``Group missmatch error.''

[Jessica Rasku]

I installed mailman about a week ago and didn't realise that it was not 
working correctly until today.  It appears that mailman is expecting to 
be executed (by sendmail) as group "mailman" GID 280 and sendmail is 
executing it as group "daemon" GID 2.  I can see that the solution is 
probably to do a manual build of mailman changing the expected GID to 2 
which is what it is getting (seems the most logical to me), I just am 
not sure how to go about this.  I haven't done any manual installs 
within the portage system yet.  Any help would be appreciated.

							Jessica

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] mailman 2.1.5-r4/sendmail issue with ``Group missmatch error.''

[Michael Sullivan]

On Tue, 2005-12-13 at 01:02 -0800, Jessica Rasku wrote:
> I installed mailman about a week ago and didn't realise that it was not 
> working correctly until today.  It appears that mailman is expecting to 
> be executed (by sendmail) as group "mailman" GID 280 and sendmail is 
> executing it as group "daemon" GID 2.  I can see that the solution is 
> probably to do a manual build of mailman changing the expected GID to 2 
> which is what it is getting (seems the most logical to me), I just am 
> not sure how to go about this.  I haven't done any manual installs 
> within the portage system yet.  Any help would be appreciated.
> 
> 							Jessica

When I had this problem the following answer helped me:

Michael,
I've had the same problem before.  In order for Mailman to work 
properly, it has to know the gid of the mail program at compile time.  
In this case it was told the mail program's gid was that of group 
"mailman", but when the script was executed it was with the gid of
group 
"deamon".  The easiest way I've found (and possibly the only?) to fix
it 
is to use vigr to get the gid of the daemon group, then edit the
mailman 
ebuild file.  Right near the top of the file is an option for setting 
the mail-gid.  Change that number to the one you found from vigr, then 
re-emerge mailman.  Keep in mind that you'll have to repeat this 
procedure every time you upgrade mailman because the new ebuild won't 
have your changes in it.
Bryan

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] mailman 2.1.5-r4/sendmail issue with ``Group missmatch error.''

[Jessica Rasku]

Michael Sullivan wrote:

> When I had this problem the following answer helped me:
> 
> Michael,
> I've had the same problem before.  In order for Mailman to work 
> properly, it has to know the gid of the mail program at compile time.  
> In this case it was told the mail program's gid was that of group 
> "mailman", but when the script was executed it was with the gid of
> group 
> "deamon".  The easiest way I've found (and possibly the only?) to fix
> it 
> is to use vigr to get the gid of the daemon group, then edit the
> mailman 
> ebuild file.  Right near the top of the file is an option for setting 
> the mail-gid.  Change that number to the one you found from vigr, then 
> re-emerge mailman.  Keep in mind that you'll have to repeat this 
> procedure every time you upgrade mailman because the new ebuild won't 
> have your changes in it.

I have tried this twice.  Once changing the ebuild in 
/var/db/pkg/net-mail/ then I created a /root/portage-overlay/ and tried 
to do it that way.  I'm missing something.  I'm just not sure what it 
is.  I feel pretty clueless right now.

							Jessica

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] mailman 2.1.5-r4/sendmail issue with ``Group missmatch error.''

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 957 bytes --]

On Tue, 13 Dec 2005 18:37:06 -0800, Jessica Rasku wrote:

> I have tried this twice.  Once changing the ebuild in 
> /var/db/pkg/net-mail/

Don't touch the ebuilds in /var/db/pkg, these are the ebuilds used to
uninstall packages, it is a copy of the ebuild used to install the
existing version, so altering it could have strange effects. The ebuilds
use to install packages are in /usr/portage. you can edit these, but they
will be reset after an emerge --sync.

> then I created a /root/portage-overlay/ and tried 
> to do it that way.

Putting an overlay directory in /root seems like a bad idea. The portage
user won't be able to access it. The standard location
is /usr/local/portage, copy the directory for the package you are dealing
with to an identical location in here,
e.g. /usr/local/portage/net-mail/mailman, before editing the ebuild.


-- 
Neil Bothwick

Run with scissors. Remove mattress tags. Top post. Be a rebel.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]