EMAIL PROTECTED]] On Behalf Of
Darrell ([EMAIL PROTECTED])
Sent: Monday, April 18, 2005 11:12 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Error 183 in Declude Virus
and double processing in Declude JunkMail during heavy load
I submitted a support ticket this morning about pr
To: Declude.JunkMail@declude.com
> Subject: Re: [Declude.JunkMail] Error 183 in Declude Virus
> and double processing in Declude JunkMail during heavy load
>
> I submitted a support ticket this morning about problems I
> seen under 2.0.6 with high load. This weekend while doing
>
Matt,
I had this same exact issue, with exact same
symptoms (Win 2000 SP4) and I called Declude on it a few weeks ago.
Eventually, I just copied in a new Declude 1.82.exe file and reinstalled my
scanners and the issue went away. I saw the same Error starting scanner
and the Error 183.
I submitted a support ticket this morning about problems I seen under 2.0.6
with high load. This weekend while doing some maintenance I ran into some
load issues when I brought one of the servers down I maintain. When I bring
one of the servers offline I know the other server will start dropping
Title: Message
Andy,
Thanks for the information. There is no doubt that you could limit the
processes and never reach this overloaded condition and that would mask
the issue, and gateway validation should also prevent overloaded
conditions if you were formerly being bombarded. What I'm curio
Title: Message
Hi
Matt:
While
I was beta testing 2.0.6, I was also suffering from some distributed dictionary
attacks - and I was scrutinizing the log files much more closely (to look for
possible beta errors).
I
don't know WHICH of these three factors were critical (2.x vs. load vs. le
