Re: [Exim] Help with mailman?

Ruth Ivimey-Cook wrote:
> This message is in MIME format. The first part should be readable text,
> while the remaining parts are likely unreadable without MIME-aware tools.
> Send mail to mime@??? for more info.
> --
> On Tue, 8 Oct 2002, Nico Erfurth wrote:
>
>>>I'm trying to set up mailman 2.0.9 with exim-4.05, and have got stuck; can
>>>anyone help? The error log was at one time reporting:
>>>
>>>2002-10-08 01:19:23 H=gatemaster.ivimey.org [192.168.0.1] sender verify fail
>>>for <testing-admin@???>: Unrouteable address
>>>2002-10-08 01:19:23 H=gatemaster.ivimey.org [192.168.0.1]
>>>F=<testing-admin@???> rejected RCPT <ruth@???>: Sender
>>>verify failed
>>>
>>>.. but I solved that (I think) by using "local_users=*" (see below). The
>>>main log still reports:
>>>
>>>2002-10-08 01:50:40 17yiZ5-0005PA-00 ** testing@???
>>><testing-admin@???> R=mm21_admin_route T=mm_do_admin: Child
>>>process of mm_do_admin transport returned 2 from command:
>>>/var/mailman/mail/wrapper
>>>
>>
>>Please post your mailman_domains domainlist too, and post an debugrun of
>>exim. It's not needed to set local_parts = * this has the same effect as
>>no local_parts option at all
>
>
>
> # home dir for Mailman
> MAILMAN_HOME=/var/mailman
> # wrapper script for mailman
> MAILMAN_WRAP=MAILMAN_HOME/mail/wrapper
> # user and group for Mailman
> MAILMAN_UID=mailman
> MAILMAN_GID=mailman

You are sure that these are correct?

> FYI, mail.* is set up in DNS as a CNAME to gatemaster, but I thought it best
> to make mailman use its own domain. The ACL:
>
> I put in local_parts=* because the sender_verify kept failing unless the
> sending user was trusted.
but local_parts = * is the same as no local_parts option at all.


> Debug Run attached (I didn't include the log of the error message, which was
> delivered fine)..

>>>>>>>>>>>>>>>>>>>Local deliveries >>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
> --------> testing-admin@??? <--------
> locking /var/spool/exim/db/retry.lockfile
> locked /var/spool/exim/db/retry.lockfile
> opened hints database /var/spool/exim/db/retry: flags=0
> dbfn_read: key=T:testing-admin@???
> no retry record exists
> search_tidyup called
> changed uid/gid: local delivery to testing <testing-admin@???> transport=mm_do_admin
> uid=41 gid=41
> auxiliary group list: <none>
> home=/var/mailman current=/var/mailman
> set_process_info: 24066 delivering 17ytkO-0006Fw-00 to testing using mm_do_admin
> mm_do_admin transport entered
> direct command:
> argv[0] = /var/mailman/mail/wrapper
> argv[1] = mailowner
> argv[2] = ${lc:$local_part}
> direct command after expansion:
> argv[0] = /var/mailman/mail/wrapper
> argv[1] = mailowner
> argv[2] = testing
> Writing message to pipe
> writing data block fd=8 size=58 timeout=3600
> writing data block fd=8 size=372 timeout=3600
> writing data block fd=8 size=1 timeout=3600
> set_process_info: 24068 reading output from |/var/mailman/mail/wrapper mailowner ${lc:$local_part}
> mm_do_admin transport yielded 7
> search_tidyup called
> mm_do_admin transport returned FAIL for testing-admin@???
> post-process testing-admin@??? (7)
> LOG: MAIN
> ** testing@??? <testing-admin@???> R=mm21_admin_route T=mm_do_admin:
Child process of mm_do_admin transport returned 2 from command:
/var/mailman/mail/wrapper

This is the relevant part of the log, thze question is, WHY mailman fails.

You can set return_fail_output=true in your mm_do_admin transport, so
you will get the error-output of the mailman command in the bounce mail.

And mailman writes own logfiles, have a look at these.

ciao