OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: Limiting simultaneous transport usage

From: Noel Jones (njonesmegan.vbhcs.org)
Date: Tue Dec 02 2008 - 15:17:33 CST


Egoitz Aurrekoetxea wrote:
>
> I have been talking about smtp client threads of postfix... but imagine
> now (for understanding better...) amavis for example... you launch two
> amavis processes as you specified in amavisd.conf. So if you set the
> proccess_limit for amavis to 2 in master.cf <http://master.cf> you
> shouldn't never have a transport timeout or any kind of error for
> waiting messages in active queue till amavis has a free proccess for
> accepting the message? the only thing could happen is that the active
> queue reaches the limit of messages in this queue and later are deferred
> instead of going to active from incoming?
>

See the README.postfix included with amavisd-new for details
on setting up amavisd-new with postfix.

- The number of postfix smtp processes feeding amavisd-new
must be less than or equal to the number of amavisd-new
processes running.
- The number of postfix smtpd processes receiving mail from
amavisd-new must be equal to or greater than the number of
amavisd-new processes.
- Amavisd-new must be able to process messages in less than
postfix $smtp_data_done_timeout seconds, usually set in
master.cf for the smtp feeding amavisd-new.

If the above conditions are met, there should be no timeout
errors regardless of the amount of mail queued, up to the
limits of the machine. All mail will stay in the active
queue, up to $qmgr_message_active_limit.

See the README.postfix included with amavisd-new for details
on setting up amavisd-new with postfix.

--
Noel Jones