Mike wrote:
> Amavis-new README.postfix.txt
>
> [25][Note] Note
> The number of Postfix clients that may
connect
> simultaneously
> to amavisd-new instances must be limited
to the
> maximum number
> of daemon child processes amavisd-new
starts.
>
> If the Postfix transport client was
allowed to open more
> connections amavisd-new can handle,
amavisd-new
> would start to
> queue incoming Postfix connections.
Postfix in
> turn would
> interpret such behaviour as
"unresponsive
> remote MTA" and
> would
> itself begin to queue mail that should be
> filtered. All this
> would possibly throttle down the complete
system and all
> further filtering attempts would suffer.
>
> Cheers
> Mike
>
> -----Original Message-----
> From: maia-users-bounces renaissoft.com
> [mailto:maia-users-bouncesrenaissoft.com] On Behalf
Of Kurt Buff
> Sent: 05 September 2007 17:44
> To: Rick Zeman; maia-usersrenaissoft.com
> Subject: Re: [Maia-users] (no subject)
>
> Rick Zeman wrote:
> > No, I think you've swing the pendulum too far the
other way,
> > at least as
> > far as your content filter is concerned. You need
to change your
> > smtp-amavis back to 2 to match the $max_servers in
your
> amavis conf.
> > Again, from mine (I use lmpt for the local
delivery. YMMV).
> >
> > amavisfeed unix - - n -
3 lmtp
> > -o lmtp_data_done_timeout=1200
> > -o lmtp_send_xforward_command=yes
> > -o disable_dns_lookups=yes
> > -o max_use=20
> >
> > $max_servers = 3; # number of
pre-forked children
> > (2..15 is
> > common)
>
> Errr...
>
> Why?
>
> Not being snotty, just that I don't understand the
(strict?)
> dependence.
>
> Kurt
Oh, fine. Just quote documentation at me, why don't you.
This seems cogent. I'll put that back in.
Kurt
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users
|
