Re: postscreen scalability

2012-03-14 Thread Wietse Venema
Dan Lists: > On Wed, Mar 14, 2012 at 2:09 PM, Wietse Venema wrote: > >> I assume you are referring to the temporary whitelist. ?I do not see > >> any way to configure what is uses to store the temporary whitelist. > >> Is it configurable? ? Is there any way to share the temp whitelist > >> between

Re: postscreen scalability

2012-03-14 Thread Dan Lists
On Wed, Mar 14, 2012 at 2:09 PM, Wietse Venema wrote: >> I assume you are referring to the temporary whitelist.  I do not see >> any way to configure what is uses to store the temporary whitelist. >> Is it configurable?   Is there any way to share the temp whitelist >> between multiple servers? >

Re: postscreen scalability

2012-03-14 Thread Wietse Venema
Dan Lists: > On Thu, Mar 8, 2012 at 4:06 PM, Wietse Venema wrote: > > Dan Lists: > >> How much traffic can postscreen handle? ? Each mail server in our > >> cluster handles 800,000 to 1,000,000 messages per day. ?We typically > > > > This is mainly limited by the whitelist database latency: the >

Re: postscreen scalability

2012-03-14 Thread Dan Lists
On Thu, Mar 8, 2012 at 4:06 PM, Wietse Venema wrote: > Dan Lists: >> How much traffic can postscreen handle?   Each mail server in our >> cluster handles 800,000 to 1,000,000 messages per day.  We typically > > This is mainly limited by the whitelist database latency: the > time needed to decide t

Re: postscreen scalability

2012-03-08 Thread Wietse Venema
Dan Lists: > How much traffic can postscreen handle? Each mail server in our > cluster handles 800,000 to 1,000,000 messages per day. We typically This is mainly limited by the whitelist database latency: the time needed to decide that a client is OK, and to hand off the connection to a real SM

postscreen scalability

2012-03-08 Thread Dan Lists
How much traffic can postscreen handle? Each mail server in our cluster handles 800,000 to 1,000,000 messages per day. We typically have 60-120 smptd processes, with peaks as high as 320. Adding a greeting delay will result in a lot of open connections. Can postscreen handle this volume even w