lists+postfix--- via Postfix-users:
> hello !
>
> I have an issue with transport_destination_recipient_limit setting.
> my config is like:
>
> master.cf:
> dx unix - n n - 20 pipe
> flags=Rq argv=/usr/local/bin/someprog ${sender} ${recipient}
>
> main.cf:
> dx_destination_recipient_limit = 300
> header_checks=pcre:header_checks.pcre
That header_checks settng seems unlikely.
> header_checks.pcre:
> /./ FILTER dx:
>
> the postfix still uses default_destination_recipient_limit value (ie 50)
> when passing delivery to dx transport and does multiple deliveries via
> dx transport for single a message with number of recepients > 50.
>
> rising default_destination_recipient_limit fixes the situation.
>
> It looks like dx_destination_recipient_limit does not work for pipe
> transport. but default_destination_recipient_limit does.
The _destiation_recipient_limit is implemented in the scheduler
(qmgr) not the pipe delivery agent.
> is this a postfix bug or it is misconfiguration ?
That feature has not chanegd in ~25 years, and it sill works
as promised:
Configuration:
$ postconf header_checks default_destination_recipient_limit
dx_destination_recipient_limit
header_checks = pcre:/etc/postfix/header_checks.pcre
default_destination_recipient_limit = 2
dx_destination_recipient_limit = 3
$ postconf -Mf dx/unix
dx unix - n n - 20 pipe flags=Rq
user=nobody argv=/usr/sbin/postlog ${recipient}
Command:
$ echo test | mail -s test 1 2 3 4 5 6
Loggging:
Sep 25 09:42:12 wzv postfix/postlog[3988108]: 1...@porcupine.org
2...@porcupine.org 3...@porcupine.org
Sep 25 09:42:12 wzv postfix/postlog[3988109]: 4...@porcupine.org
5...@porcupine.org 6...@porcupine.org
That is three recipients per delivery request, and not the lower
value of default_destination_recipient_limit. Exactly as it should
be.
This requires running "postfix reload" before doing any tests.
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
