From: Luca Berra (no email)
Date: Sun Feb 01 2004 - 05:45:26 EST
On Sun, Feb 01, 2004 at 11:18:08AM +0100, Magnus Bäck wrote:
>On Sunday, February 01, 2004 at 10:43 CET,
> Luca Berra <> wrote:
>
>> Is there any pratical difference in using
>> XXXX_destination_concurrency_limit in main.cf versus filling the maxproc
>> column for the XXXX transport in master.cf, i was tempted to use the
>> former since it is easier to reconfigure.
>
>The destination concurrency limits the number of concurrent connections
>to the same destination. This is obviously not the same as the total
>number of connections, unless for services defined in master.cf that
>only receive mail for a single destination.
I realize i originally posted insufficient information, I'll try to
explain better.
I use this transport to filter mail to amavisd-new
main.cf:
content_filter=lmtp-filter:127.0.0.1:10025
master.cf:
lmtp-filter unix - - - - - lmtp
-o lmtp_data_done_timeout=1200
-o disable_dns_lookups=yes
Since i use the transport only for this content filter, the number of
concurrent connections will be equal to the total number of connections.
Since the need to limit the number of connections is imposed by the
process limit in amavisd-new i think using
lmtp-filter_destination_concurrency_limit instead of 'maxproc' column
will be even more correct, since a different destination would be a
different scanning host with a different set of processes.
Thanks a lot,
L.
--
Luca Berra --
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
|
|
|