OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: recipients in master.cf
From: Wietse Venema (wietseporcupine.org)
Date: Fri Jun 23 2000 - 08:09:27 CDT

Lars Hecking:
>
> > > You need to add
> > >
> > > vscan_destination_concurrency_limit = 100
> >
> > Isn't that vcan_destination_recipient_limit, the number of
> > recipients per delivery?
> >
> > vscan_destination_concurrency_limit limits the number of simultaneous
> > vscan instances that deliver to the same destination.
>
> That would explain some stuff ...
>
> I think you're right, and I need to replace this with
>
> vscan_destination_concurrency_limit = $default_destination_concurrency_limit
>
> or even leave it out completely.
>
> As vscan_destination_concurrency_limit is a new, transport specific
> parameter, is it set automatically, or do I need to set it explicitly
> as above?

It defaults to $default_destination_concurrency_limit.

As these parameter names are made up on the fly from entries in
master.cf it is a bit hard to list such parameters in postconf
output. On the other hand, it should be possible to test for all
names in master.cf if an explicit xxx_destination_concurrency_limit
is specified in main.cf.

        Wietse