John, I've been monitoring DecludeProc.exe with Performance Monitor, specifically, the process counters for threads, cpu, handles and working set memory and have not seen any leaks.
It was through monitoring the threads that I was able to comment on the sawtooth pattern that Matt and I were both seeing. I'm also using an in-house script to count the number of message files in the proc folder and email the results if the count is more than 100 to an internal mailserver's IP address thanks to a 3rd party SMTP tool (postie.exe)... That whole bandaid mechanism should survive any DNS relates WinSock outage. I think I've got my belt and suspenders on. Andrew 8) > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John Doyle > Sent: Tuesday, May 23, 2006 3:43 PM > To: Declude.JunkMail@declude.com > Subject: RE: [Declude.JunkMail] Experience with 4.x > > Andrew > > I had this problme last year, decludeproc will suffer memory > creep, slowly building over time. > You can see if it's happening by opening taskmanager and > checking the memory used by decludeproc. > For us it would run for about 4 hours before a problem arose. > > I can't remember what finally fixed the problem for us. I > have used the dnsoverride function to direct it to a less > used dns server. But I can't recall if that was the fix or > not. We might have had a firewall port issue. > > I'd turn the winsockcleanup off and monitor your memory > usage. If it keeps creeping up turn it back on. > > John > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Colbeck, Andrew > Sent: Tuesday, May 23, 2006 3:26 PM > To: Declude.JunkMail@declude.com > Subject: RE: [Declude.JunkMail] Experience with 4.x > > > Thanks, David. > > I've read all of the support forum emails that have been > posted on the WINSOCKCLEANUP and even reviewed them again via > the mail archive website before my own implementation. > > What I haven't been able to tell is whether I can diagnose > this issue if I have it before it becomes an outage. > > Can it only be detected by it's side-effect of filling up the > proc folder? > > If I have a mechanism on my IMail server that does DNS > queries... Will they fail when the WinSock needs being > cleaned up? I think not, as at least one posting > specifically mentioned that IMail IP4R tests worked when > DecludeProc IP4R tests timed out. > > Your official description for "WINSOCKCLEANUP ON" says > "...network stack causing loss of functionality for basic > network operations"; is this deliberately generic so that you > don't have to explain what a DNS test is, or does it imply > that other IP communications will also fail, e.g. > SMTP and (critically for me) RDP? > > Andrew. > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > David Barker > > Sent: Tuesday, May 23, 2006 3:12 PM > > To: Declude.JunkMail@declude.com > > Subject: RE: [Declude.JunkMail] Experience with 4.x > > > > Andrew, > > > > In certain cases we found that Imail would stop resolving, > it seemed > > that stop/starting the decludeproc or smtp service fixed > the problem > > by resetting the winsock. So we added WINSOCKCLEANUP to > deal with this > > specific Imail issue. > > > > David B > > www.declude.com > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Colbeck, > > Andrew > > Sent: Tuesday, May 23, 2006 3:45 PM > > To: Declude.JunkMail@declude.com > > Subject: RE: [Declude.JunkMail] Experience with 4.x > > > > David, is there a proactive way to detect if an installation would > > benefit from the WINSOCKCLEANUP ON directive in declude.cfg? > > > > I would rather be able to detect this while it's happening than to > > react when I find that spam is leaking or that the proc folder is > > continually growing. > > > > Andrew. > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of > > David Barker > > > Sent: Tuesday, May 23, 2006 7:48 AM > > > To: Declude.JunkMail@declude.com > > > Subject: RE: [Declude.JunkMail] Experience with 4.x > > > > > > Mike, > > > > > > 1. The WINSOCKCLEANUP ON activates when the \Proc > reaches 0 > > > 2. If Decludeproc stops unexpectedly files it is busy with > > are move to > > > the \review > > > 3. You can use AUTOREVIEW ON to have these move back to the \proc > > > 4. Be aware though if there is a real problem message you > may find > > > that the message gets looped 5. Make sure you have the > > latest version > > > of decludeproc ... There should be a release later today or > > tommorow. > > > > > > David B > > > www.declude.com > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of Mike N > > > Sent: Tuesday, May 23, 2006 10:23 AM > > > To: Declude.JunkMail@declude.com > > > Subject: Re: [Declude.JunkMail] Experience with 4.x > > > > > > I found that WINSOCKCLEANUP ON would force a reset if the \proc > > > directory > > > never hits 0. In this case, files build up in the \review > > > subfolder which > > > require manual processing. > > > > > > ----- Original Message ----- > > > From: "David Barker" <[EMAIL PROTECTED]> > > > To: <Declude.JunkMail@declude.com> > > > Sent: Tuesday, May 23, 2006 7:34 AM > > > Subject: RE: [Declude.JunkMail] Experience with 4.x > > > > > > > > > > The purpose of WINSOCKCLEANUP ON is to reset the > > > winsock, what > > > > happens when using this setting is that when the \proc > > > directory hit 0 > > > > decludeproc will finish processing all the messages in > the \work > > > > before checking the \proc again. > > > > > > --- > > > 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. > > > > > > --- > > > 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. > > > > > --- > > 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. > > > > --- > > 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. > > > --- > 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. > > --- > 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. > --- 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.
