In amavisd-new documentation README.postfix (version 148,
BTW, the release online is outdate, as reports version 122
see http://www.ijs.si/software/amavisd/README.postfix)
there is reported that using amavisfeed_destination_concurrency_limit = XX
is an alternative way to master.cf for controlling the maximum numbers of
concurrent processes (which should be in sync with amavis $max_servers).
Indeed I found that
the number of concurrent lmtp processes named amavisdfeed
exceed 1 unit the number in amavisfeed_destination_concurrency_limit. E.g.
if I have amavisfeed_destination_concurrency_limit = 2, I get 3
amavisfeed lmtp processes running,
if I have amavisfeed_destination_concurrency_limit = 1 I get 1 lmtp
process running and so on.
On the other hand setting such limit in master.cf won't exceed the
specified number.

Are you obtaining the same behaviour? Furthermore I get also that
postconf <transport>_destination_concurrency_limit doesn't show any output
(probably works only with internal vars). Anyway seems also that
using <transport>_destination_concurrency_limit has a weird behaviour,
e.g. if you specify it to 1, the meaning changes from global (per-domain)
to per-recipient (e.g. see this thread
http://archives.neohapsis.com/archives/postfix/2007-11/1466.html).

Bye
Giuseppe.

------------------------------------------------------------------------------
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/amavis-user 
 AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 
 AMaViS-HowTos:http://www.amavis.org/howto/ 

Reply via email to