* Craig Stacey <[EMAIL PROTECTED]> wrote:
> master.cf:
> mailmancom unix - n n - - pipe
> flags=FR user=list argv=/www/lists.example.com/bin/postfix-to-
> mailman.py ${nexthop} ${user}
> mailmanorg unix - n n - - pipe
> flags=FR user=list argv=/www/lists.example.org/bin/postfix-to-
> mailman.py ${nexthop} ${user}
> mailmannet unix - n n - - pipe
> flags=FR user=list argv=/www/lists.example.net/bin/postfix-to-
> mailman.py ${nexthop} ${user}
>
>
> transport:
> lists.example.com mailmancom:
> lists.example.org mailmanorg:
> lists.example.net mailmannet:
>
> /var/log/mail.info:
>
> Oct 27 14:39:23 owney postfix/pipe[16420]: 0788A8F6B2:
> to=<[EMAIL PROTECTED] >, relay=mailmancom, delay=0, status=sent
> (lists.example.com)
> Oct 27 14:39:23 owney postfix/pipe[16420]: 0788A8F6B2:
> to=<[EMAIL PROTECTED] >, relay=mailmancom, delay=0, status=sent
> (lists.example.com)
> Oct 27 14:39:23 owney postfix/pipe[16420]: 0788A8F6B2:
> to=<[EMAIL PROTECTED] >, relay=mailmancom, delay=0,
> status=sent (lists.example.com)
You are sending three messages to three different localparts
([EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]) in one domain (lists.example.com), so
Postfix is using the same transport - pretty normal so far.
> Then, from /www/lists.example.com/logs/smtp, we see only one come out
> the other side:
>
> Oct 27 14:39:23 2008 (2652) <[EMAIL PROTECTED]
>> smtp to core-other for 2 recips, completed in 0.013 seconds
I think the "post" logfile would be more interesting.
> Three messages go in, one comes out the other end.
>
> I did some logging, and found that postfix-to-mailman.py is only
> processing *one* message. The script gets the listname from this line:
>
> local = sys.argv[2]
>
> All the docs specify you should put this line in main.cf:
>
> mailman_destination_recipient_limit = 1
>
> I can find no documentation on that particular config, but it seems
> like it's telling postfix to only put one recipient per message when
> sending to mailman, which would jibe with what the variable setting in
> the above script is looking for.
No, since sys.argv[1] should yield the ${nexthop} setting from
master.cf, i.e. the recipient domain (which is ignored by the script).
> However, it looks like that setting is totally being ignored by our
> postfix install. If I type "postconf", I do *not* see
> "mailman_destination_recipient_limit" listed in the output. That
> seems to me to indicate to me that it's not being honored.
That's perfectly normal - any custom variables defined in main.cf
don't show in postconf -n output.
Ciao
Stefan
--
Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9
Wenn Frauen nicht mehr wissen, was sie tun sollen, ziehen sie sich aus, und das
ist wahrscheinlich das
Beste, was Frauen tun können.
Samuel Beckett
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
