Daevid Vincent wrote:
>
>Well, exim hasn't changed since that date above, and the config hasn't
>changed for even longer, so I believe it *is* mailman and not exim:
>
># ll
>total 80
>drwxr-xr-x 2 root root 4096 Jun 26 12:45 .
>drwxr-xr-x 77 root root 4096 Sep 13 03:14 ..
>-rw-r--r-- 1 root
> > > From: John W. Baxter
> > daevid ~ # which exim
> > /usr/sbin/exim
> >
> > daevid ~ # ll /usr/sbin/exim
> > -rws--x--x 1 root root 830012 Jul 7 00:57 /usr/sbin/exim
>
> I doubt it can just be mailman.
Well, exim hasn't changed since that date above, and the config hasn't
changed for even
On Tue, 2005-09-13 at 12:05 -0700, Daevid Vincent wrote:
> # User and group for Mailman, should match your --with-mail-gid
> # switch to Mailman's configure script.
> # Value is normally "mailman"
> MM_UID=mailman
> MM_GID=mailman
> #
> # Domains that your lists are in - colon separat
On Tue, 2005-09-13 at 11:33 -0700, Daevid Vincent wrote:
> > -Original Message-
> > From: John W. Baxter
> >
> > Has Exim lost its setuid bit (and/or its root ownership) in
> > the upgrade?
>
> Thanks for the suggestion John, but the perms look correct. Also, other
> email works fine (inc
> >Mark said, "Yes, it has the flags, but what is the value of
> the ${MAILGID}
> >parameter? The error message you received says it's
> 'mailman' and should be
> >'mail'."
> >
> >And looking at the log, he seems to be correct:
> >Sep 12 12:16:19 [Mailman mail-wrapper] Group mismatch error. Ma
> -Original Message-
> From: John W. Baxter
>
> Has Exim lost its setuid bit (and/or its root ownership) in
> the upgrade?
Thanks for the suggestion John, but the perms look correct. Also, other
email works fine (incoming/outgoing). It's only mailman...
daevid ~ # which exim
/usr/sbin/ex
On 9/12/05 7:58 PM, "Mark Sapiro" <[EMAIL PROTECTED]> wrote:
> The wrapper is telling you that it
> expects to be executed as group 'mailman', and it looks from what
> you've presented that it was in fact built that way. It also seems you
> can't change it in your update package.
>
> The wrapper
Daevid Vincent wrote:
>Mark said, "Yes, it has the flags, but what is the value of the ${MAILGID}
>parameter? The error message you received says it's 'mailman' and should be
>'mail'."
>
>And looking at the log, he seems to be correct:
>Sep 12 12:16:19 [Mailman mail-wrapper] Group mismatch error
Mark said, "Yes, it has the flags, but what is the value of the ${MAILGID}
parameter? The error message you received says it's 'mailman' and should be
'mail'."
And looking at the log, he seems to be correct:
Sep 12 12:16:19 [Mailman mail-wrapper] Group mismatch error. Mailman
expected the mail_
> Yes, it has the flags, but what is the value of the ${MAILGID}
> parameter? The error message you received says it's 'mailman' and
> should be 'mail'.
>
> Your original post says:
>
> >daevid portage-logs # ll /usr/local/mailman/mail/mailman
> >-rwxr-sr-x 1 mailman mailman 7768 Sep 7 11:34
Daevid Vincent wrote:
>
>Furthermore, it appears that the .ebuild has those --with flags mentioned in
>the FAQ.
>
># more /usr/portage/net-mail/mailman/mailman-2.1.5-r4.ebuild
>...
>src_compile() {
>econf \
>--prefix=${INSTALLDIR} \
>--with-mail-gid=${MAILGID
--with-cgi-gid=${APACHEGID} \
|| die "configure failed"
make || die "make failed"
}
...
> -Original Message-
> From: Mark Sapiro [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 12, 2005 1:11 PM
> To: Daevid Vincent; mailman-users@pytho
Daevid Vincent wrote:
>
>Sep 12 12:16:19 [Mailman mail-wrapper] 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 "mail". Try tweaking
>the mail server to run the_script as group "mail
Mailman was working, then a (Gentoo) 'emerge -Davu system' update happened
the other day and looks like it broke mailman.
daevid portage-logs # ll *mailman*
-rw-r--r-- 1 root root 62662 Sep 7 11:34 3485-mailman-2.1.5-r4.log
-rw-r--r-- 1 root root 1105 Sep 7 11:34 3486-mailman-2.1.5-r4.log
Se
14 matches
Mail list logo
