Just a follow-up to this problem, uninstalling the latest Microsoft patch fixed the problem. We're guessing that it has something to do with the total number of network connections, since that is the only thing that's different between Declue running and not running-- Declude opens a bunch per incoming email while performing its testing. This is only a theory and will get a lot more study, but for now, an un-patched server works fine. We're going to dig in and find out what the patch does to the server and see if we can figure this out, because apparently the patch is fairly important.
Thanks to all that made suggestions. > I have no idea how it has any effect, but I've enabled and > disabled Declude a dozen times with the same result. We're > using 1.75. > > Tomorrow morning I'm going to spend a couple of hours with > the server offline looking deeper into the problem. It's > difficult to really get down to the problem when it's in a > production context. > > > -----Original Message----- > > From: John Tolmachoff (Lists) [mailto:[EMAIL PROTECTED] > > Sent: Friday, September 12, 2003 12:22 PM > > To: [EMAIL PROTECTED] > > Subject: RE: [Declude.JunkMail] Timing out with latest > Microsoft patch > > > > > > Since Declude has nothing to do with messages being received > > or sent from > > the server, or POP3 service and such, how could disabling > > Declude affect > > this? > > > > What version of Declude.exe are you using? > --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
