RE: Delivery delay problems

2008-09-26 Thread Marco TCHI HONG
>The client concurrency must not exceed the service concurrency, and >virus scanning is CPU intensive, and in my experience this is too much. > >Of course in a multi-filter chain, if any of the filters are high >latency, the combined filter latency can throttle the CPU demand >of any CPU intensive

Re: Delivery delay problems

2008-09-26 Thread Victor Duchovni
On Fri, Sep 26, 2008 at 06:30:03PM +0300, Marco TCHI HONG wrote: > >These concurrency numbers are very high. Running A/V scanning > >at concurrency substantially higher than ~20 (on Dual CPU boxes) is > >generally counter-productive. > > I have two Xeon 5160 Dual-Core 3,0 GHz on my box and 4Gb RA

RE: Delivery delay problems

2008-09-26 Thread Marco TCHI HONG
>These concurrency numbers are very high. Running A/V scanning >at concurrency substantially higher than ~20 (on Dual CPU boxes) is >generally counter-productive. I have two Xeon 5160 Dual-Core 3,0 GHz on my box and 4Gb RAM. About 500k mail go through this MX (50Gb traffic). >What is the destinat

Re: Delivery delay problems

2008-09-26 Thread Victor Duchovni
On Fri, Sep 26, 2008 at 05:44:28PM +0300, Marco TCHI HONG wrote: > >KAV versions I've seen are not fully transparent proxies, they respond > >with banner 220 and EHLO 250 before making a downstream connection. The > >connection to the downstream server may happen as late as "." (after > >the conte

RE: Delivery delay problems

2008-09-26 Thread Marco TCHI HONG
>KAV versions I've seen are not fully transparent proxies, they respond >with banner 220 and EHLO 250 before making a downstream connection. The >connection to the downstream server may happen as late as "." (after >the content is scanned). It is certainly important to make sure that >the configur

Re: Delivery delay problems

2008-09-26 Thread Victor Duchovni
On Fri, Sep 26, 2008 at 09:19:50AM -0400, Wietse Venema wrote: > Wietse: > > >Another possibility is that the > > >Postfix SMTP server behind the content filter has problems when it > > >tries to resolve the 127.0.0.1 client IP address to a hostname. > > Marco TCHI HONG: > > How would be resolvin

Re: Delivery delay problems

2008-09-26 Thread Wietse Venema
Wietse: > >Another possibility is that the > >Postfix SMTP server behind the content filter has problems when it > >tries to resolve the 127.0.0.1 client IP address to a hostname. Marco TCHI HONG: > How would be resolving a problem 127.0.0.1 when in my /etc/hosts.conf I > have : order hosts,bind a

RE: Delivery delay problems

2008-09-26 Thread Marco TCHI HONG
d the message to the content filter ? Marco -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Wietse Venema Envoyé : vendredi 26 septembre 2008 15:40 À : Postfix users Objet : Re: Delivery delay problems Marco TCHI HONG: > Our problem is that mail st

Re: Delivery delay problems

2008-09-26 Thread Wietse Venema
Marco TCHI HONG: > Our problem is that mail stay a long time in the active queue before the > content filter, but when it's sent to the server where mailboxes are > stored there's no problem: > > Sep 26 10:11:57 mx postfix/smtp[1387]: 1906C718411: > to=<[EMAIL PROTECTED]>, relay=127.0.0.1[127.0.0.1

RE: Delivery delay problems

2008-09-26 Thread Marco TCHI HONG
HONG Cc : postfix-users@postfix.org Objet : Re: Delivery delay problems Marco TCHI HONG: > Our problem is that mail stay a long time in the active queue before the > content filter, but when it's sent to the server where mailboxes are > stored there's no problem: > > S

Re: Delivery delay problems

2008-09-26 Thread Wietse Venema
Marco TCHI HONG: > Our problem is that mail stay a long time in the active queue before the > content filter, but when it's sent to the server where mailboxes are > stored there's no problem: > > Sep 26 10:11:57 mx postfix/smtp[1387]: 1906C718411: > to=<[EMAIL PROTECTED]>, relay=127.0.0.1[127.0.0.