[Mailman-Users] mailman stopped working after upgrade
Daevid Vincent
daevid at daevid.com
Tue Sep 13 21:05:39 CEST 2005
> >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_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 "mailman", or
> re-run configure,
> >_providing the command line option `--with-mail-gid=mail'._
> >
> >But the .ebuild script sets it to gid 280, shouldn't it be
> 8? why is that?
> >Is that the problem? How can I fix that. Re-emerging doesn't
> let me change
> >those .ebuild values. MD5 errors and such.
> >
> >APACHEGID="81"
> >MAILGID="280"
> >
> >src_compile() {
> > econf \
> > --prefix=${INSTALLDIR} \
> > --with-mail-gid=${MAILGID} \
> > --with-cgi-gid=${APACHEGID} \
> > || die "configure failed"
> >
> > make || die "make failed"
> >}
> >
> ># ll /etc/exim/exim.conf
> >-rw-r--r-- 1 root root 29452 Apr 29 13:54 /etc/exim/exim.conf
> >
> > # 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
> >
> >So, these match what the comment says there, and what the
> .ebuild is doing.
> >
> >I'm so confused. *sigh*
>
>
> As well you should be at this point. 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 also complains that it is not being executed as group
> 'mailman', but rather as group 'mail'. This is the confusing part
> because it seems from the above that you are telling Exim to invoke
> the wrapper as group 'mailman' yet the wrapper is telling you it is
> being invoked as group 'mail'. I would look carefully at the Exim
> configuration to be sure that
>
> MM_UID=mailman
> MM_GID=mailman
>
> are in the right place and are not being overridden somewhere else.
Below is portions of my /etc/exim/exim.conf. I deleted out any irrellevant
parts, but I kept everything in the right order... I believe it's pretty
much stock. (I don't know much about exim).
># cat /etc/exim/exim.conf
######################################################################
# Runtime configuration file for Exim #
######################################################################
#
# copied from http://www.exim.org/howto/mailman21.html#exconf
#
# Home dir for your Mailman installation -- aka Mailman's prefix
directory.
# By default this is set to "/usr/local/mailman"
# On a Red Hat/Fedora system using the RPM use "/var/mailman"
# On Debian using the deb package use "/var/lib/mailman"
# This is normally the same as ~mailman
MM_HOME=/usr/local/mailman
#
# 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 separated list
# you may wish to add these into local_domains as well
domainlist
mm_domains=daevid.com:rollinballzcrew.com:me-racing.com:marq.org
#
# -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
#
# These values are derived from the ones above and should not need
# editing unless you have munged your mailman installation
#
# The path of the Mailman mail wrapper script
MM_WRAP=MM_HOME/mail/mailman
#
# The path of the list config file (used as a required file when
# verifying list addresses)
MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck
######################################################################
# MAIN CONFIGURATION SETTINGS #
######################################################################
exim_user = mail
######################################################################
# ROUTERS CONFIGURATION #
# Specifies how addresses are handled #
######################################################################
# THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! #
# An address is passed to each router in turn until it is accepted. #
######################################################################
mailman_router:
driver = accept
domains = +mm_domains
require_files = MM_LISTCHK
local_part_suffix_optional
local_part_suffix = -admin : \
-bounces : -bounces+* : \
-confirm : -confirm+* : \
-join : -leave : \
-owner : -request : \
-subscribe : -unsubscribe
transport = mailman_transport
procmail:
debug_print = "R: procmail for $local_part@$domain"
driver = accept
check_local_user
transport = procmail_pipe
require_files = ${local_part}:${home}/.procmailrc:+/usr/bin/procmail
no_verify
no_expn
userforward:
driver = redirect
check_local_user
# local_part_suffix = +* : -*
# local_part_suffix_optional
file = $home/.forward
# allow_filter
no_verify
no_expn
check_ancestor
file_transport = address_file
pipe_transport = address_pipe
reply_transport = address_reply
localuser:
driver = accept
check_local_user
# local_part_suffix = +* : -*
# local_part_suffix_optional
transport = local_delivery
cannot_route_message = Unknown user
######################################################################
# TRANSPORTS CONFIGURATION #
######################################################################
# ORDER DOES NOT MATTER #
# Only one appropriate transport is called for each delivery. #
######################################################################
mailman_transport:
driver = pipe
command = MM_WRAP \
'${if def:local_part_suffix \
{${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \
{post}}' \
$local_part
current_directory = MM_HOME
home_directory = MM_HOME
user = MM_UID
group = MM_GID
# End of Exim configuration file
More information about the Mailman-Users
mailing list