It sounds to me as though your system was bombarded with more than it
could handle.
Tuning is somewhat of a fine art.
concurrencyincoming should probably be throttled back a bit. At what
point was your system choking?
memory is limited by your softlimit setting.
I'm not aware of any sort of cpu constraint.
Keep in mind, your system never really failed. Even the messages that
timed out should have been resent by the sending server.
The better your spamdyke configuration is at blocking spam, the easier
the rest of your system will breathe. If you post your spamdyke.conf
we'll have a look at it.
Ronnie Tartar wrote:
I think you may be right, as it seems to be fine now? I even put my
spamdyke timeout back to 5 second delay.
Are there any parameters that I can adjust to help with this type of issue?
There were no cpu/memory constraints?
Regards
-----Original Message-----
From: news [mailto:[email protected]] On Behalf Of Eric Shubert
Sent: Monday, July 13, 2009 7:06 PM
To: [email protected]
Subject: Re: [qmailtoaster] SMTP issues
I think the cause was a "spam storm". (Is that a technical term?)
Can you turn on spamdyke detailed logging and see what the last message
before the delay is?
Ronnie Tartar wrote:
Did anybody come up with a fix for this?
Port 25 still takes 30 seconds to answer even after turning my delay
greeting in Spamdyke to zero.
CPU load is .15
I looked in smtp log and when I telnet to port 25 I get the following
immediately
@400000004a5ba9bb1ba5146c tcpserver: pid 22068 from 24.73.161.202
@400000004a5ba9bb1ba52bdc tcpserver: ok 22068
mail.host2max.com:72.29.91.110:25 :24.73.161.202::54565
But it still takes 30 seconds for the greeting to come up. Nothing that
it's waiting for etc...
Any help?
Thanks
-----Original Message-----
From: Ronnie Tartar [mailto:[email protected]]
Sent: Monday, July 13, 2009 3:30 PM
To: [email protected]
Subject: Re: [qmailtoaster] SMTP issues
Running 4.0.10 (latest). First thing I did was update from 4.0.8.
I put qmail back in. I did have my timeout set way to low. I bumped it
to
660, it was 30. That would have definitely caused no mail to come through
because it was taking just over 30 seconds for qmail to answer.
----- Original Message -----
From: "Eric Shubert" <[email protected]>
To: <[email protected]>
Sent: Monday, July 13, 2009 2:58 PM
Subject: Re: [qmailtoaster] SMTP issues
There was a bug in the spamdyke 3.x version regarding timeouts. I set
idle-timeout-secs=660
which seems to fix that.
Which version of spamdyke are you running?
Ronnie Tartar wrote:
This was the spamdyke error in the log, it was timing out sending it to
qmail.
Jul 13 06:59:28 mail spamdyke[21362]: TIMEOUT from: (unknown) to:
(unknown)
origin_ip: 72.29.91.100 origin_rdns: prod12.designatedystems.com auth:
(unknown) reason: TIMEOUT
----- Original Message ----- From: "Ronnie Tartar"
<[email protected]>
To: <[email protected]>
Sent: Monday, July 13, 2009 2:43 PM
Subject: Re: [qmailtoaster] SMTP issues
I have spamdyke installed and it was still having the problems.
----- Original Message ----- From: "Eric Shubert" <[email protected]>
To: <[email protected]>
Sent: Monday, July 13, 2009 2:29 PM
Subject: Re: [qmailtoaster] SMTP issues
Gilbert T. Gutierrez, Jr. wrote:
Jake helped me resolve this issue. My server was getting nailed for
connections and by enabling some blacklists, my server is sane again.
Gilbert
I would seriously consider installing spamdyke if you haven't already.
This will lessen the load even more.
--
-Eric 'shubes'
--
-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]
