From what Jake has said, having NO RBLs would make any performance problem you have worsen. If you use zen.spamhaus.org that should make a noticeable difference in the number of smtp processes running.

[email protected] wrote:
Hi,
my incoming message are stable in the 30/60 to 40/60 range.

Fabio

----Messaggio originale----
Da: [email protected]
Data: 13/07/2009 19.59
A: <[email protected]>
Ogg: Re: [qmailtoaster] SMTP timeouts

Eric Shubert wrote:
You too? What the heck's going on???
(BTW, nice to see you again on Saturday)

I don't see anything in particular, except that your system appears to be busy scanning a lot at times.

Timeouts are intermittent I'm guessing, right?

I'm also guessing that timeouts occur when there are many scans active at the same time. Can you confirm this?

Are you seeing a lot of paging when this happens?
I just helped Gilbert out over the phone and am logged into his system now.
His particular scenario looked to be maxed out connections. He was not running any blacklists and was consistently running 199/200 incoming connections (check your /var/log/qmail/smtp current file to see how many incoming connections you have). I enabled cbl.abuseat.org and zen.spamhaus.org and his incoming connections dropped to 25/200 and his server became responsive again.

You others having similar issues may want to investigate this. It looks like there may be a spam storm this fine Monday and your incoming connections may be maxed out.



--
-Eric 'shubes'


---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
     If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
    Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
    For additional commands, e-mail: [email protected]


Reply via email to