| 1 |
On Tue, 2005-12-13 at 01:02 -0800, Jessica Rasku wrote: |
| 2 |
> I installed mailman about a week ago and didn't realise that it was not |
| 3 |
> working correctly until today. It appears that mailman is expecting to |
| 4 |
> be executed (by sendmail) as group "mailman" GID 280 and sendmail is |
| 5 |
> executing it as group "daemon" GID 2. I can see that the solution is |
| 6 |
> probably to do a manual build of mailman changing the expected GID to 2 |
| 7 |
> which is what it is getting (seems the most logical to me), I just am |
| 8 |
> not sure how to go about this. I haven't done any manual installs |
| 9 |
> within the portage system yet. Any help would be appreciated. |
| 10 |
> |
| 11 |
> Jessica |
| 12 |
|
| 13 |
When I had this problem the following answer helped me: |
| 14 |
|
| 15 |
Michael, |
| 16 |
I've had the same problem before. In order for Mailman to work |
| 17 |
properly, it has to know the gid of the mail program at compile time. |
| 18 |
In this case it was told the mail program's gid was that of group |
| 19 |
"mailman", but when the script was executed it was with the gid of |
| 20 |
group |
| 21 |
"deamon". The easiest way I've found (and possibly the only?) to fix |
| 22 |
it |
| 23 |
is to use vigr to get the gid of the daemon group, then edit the |
| 24 |
mailman |
| 25 |
ebuild file. Right near the top of the file is an option for setting |
| 26 |
the mail-gid. Change that number to the one you found from vigr, then |
| 27 |
re-emerge mailman. Keep in mind that you'll have to repeat this |
| 28 |
procedure every time you upgrade mailman because the new ebuild won't |
| 29 |
have your changes in it. |
| 30 |
Bryan |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-user@g.o mailing list |
Archives