[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Mailman/Exim4 issues



I've been having some problem getting Mailman to work with Exim4, I've been
googling and trying stuff for a couple of days and I'm at a dead end.
I'm kind of hoping by the time I articulate my problem and the steps and
checks I have performed to solve it, in this email,  I will spot the
solution.

I'm running Sarge, a fresh install.
My DNS is working, I can resolve my FQDN locally and remotely.
Apache is installed and I can access it locally and remotely.

Exim4 is installed and configured to send and receive email.
Dovecot is installed and IMAP and POP3 both work.

I can send and receive mail.

I have install Mailman and that process created the mailman user and group.
/etc/mailman/mm_cfg.py has been altered to reflect my hostname...

# Default domain for email addresses of newly created MLs
DEFAULT_EMAIL_HOST = 'mydomain.com'
#-------------------------------------------------------------
# Default host for web interface of newly created MLs
DEFAULT_URL_HOST   = 'www.mydomain.com'


I created a mailman list and `check_perms` reports 'No problems found'.
Which is nice.
The Mailman pages are available and I can create lists.

So I create a list called 'test'.

I receive the email messages confirming the list has been created and
showing the aliases.
I'm using Exim4 so I'm pretty sure I do not need to add the aliases to my
/etc/aliases file.

For my Exim4 configuration I have the following...

/etc/exim4/conf.d/main.01_exim4-config_listmacrosdefs

# Home dir for your Mailman installation -- aka Mailman's prefix
# directory.
MAILMAN_HOME=/var/lib/mailman
MAILMAN_WRAP=MAILMAN_HOME/mail/mailman

# User and group for Mailman, should match your --with-mail-gid
# switch to Mailman's configure script.
MAILMAN_USER=mailman
MAILMAN_GROUP=mailman


I add the file, /etc/exim4/conf.d/router/450_exim4-config_mailman_router,
and that contains :

  mailman_router:
    driver = accept
    require_files = MAILMAN_HOME/lists/$local_part/config.pck
    local_part_suffix_optional
    local_part_suffix = -bounces : -bounces+* : \
                        -confirm+* : -join : -leave : \
                        -owner : -request : -admin
    transport = mailman_transport

One thing that did give me pause for thought was the advice in the
README.EXIM which said 'Put this router somewhere after the "begin routers"
line of your config file, and remember that order matters.'

I chose 450 because 400 is for system aliases, and although I'm not using
them for mailman, this seems like a likely place for exim to be dealing with
mailman/router stuff.


For the transport section, I have :

/etc/exim4/conf.d/transport/40_exim4-config_mailman_transport 

  mailman_transport:
    driver = pipe
    command = MAILMAN_WRAP \
              '${if def:local_part_suffix \
                    {${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \
                    {post}}' \
              $local_part
    current_directory = MAILMAN_HOME
    home_directory = MAILMAN_HOME
    user = MAILMAN_USER
    group = MAILMAN_GROUP

This matches the README.EXIM example.

Ok, so that is the config, I restart the services...
`/etc/init.d/exim4 reload`
`/etc/init.d/mailman reload`

Right, from gmail I send a blank massage to test-join@mydomain.com.....
A quick refresh will present me with the following reply...

<snip>
This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

    test-join@lostplot.com

Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 9): 550 unknown user
</snip>


/var/log/exim4/mainlog and rejectlog have the following...
2005-11-07 23:05:51 H=zproxy.gmail.com [64.233.162.194]
F=<xxxxx.xxxx@gmail.com> rejected RCPT <test-join@mydomain.com>:
Unrouteable address



I'm not really sure what's going on at this point, Exim appears to not to
recognise the test-join, but isn't what the router section was for ?
Is it an ordering issue ?

I read something about a local_domains setting, but didn't find where this
should be set, and I do recive normal mail for this server.

Any help appreciated.

Thanks

Matt



Reply to: