RE: [Declude.JunkMail] Experience with 4.x
The purpose of WINSOCKCLEANUPON 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. As WINSOCKCLEANUP is to be used only by those who experience DNS issues I would suggest running your tests again with WINSOCKCLEANUP commented out and see how the behavior differs. Also having the WAITFORMAIL to low can cause the CPU to process very high as it is constantly checking the \proc I would suggest a minimum of 500-1000 David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Monday, May 22, 2006 8:12 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Experience with 4.x Darrell, I put up two Windows Explorer windows side-by-side under normal volume and the pattern was consistent where the proc folder grows while the work folder shrinks until the work folder hits zero at which point the proc folder empties out and everything lands in work and then the pattern repeats with proc growing while work shrinks. My settings are as follows: THREADS50 WAITFORMAIL100 WAITFORTHREADS10 WAITBETWEENTHREADS50 WINSOCKCLEANUPON AUTOREVIEWON INVITEFIXON Matt Darrell ([EMAIL PROTECTED]) wrote: It's a faulty design that leaves more than half a server's CPU capacity unused due to the mere fact that they wait for all threads to complete before moving in a new batch. I can't speak to what you see on your server, but that is not how it is running on my server. I just double checked again to make sure I am not crazy, but as I watch the thread count on my server (decludeproc) the threads fluctuate between 7 - 30 ( threads currently set to 50). It is not uncommon to see the threads move as follow: 11,8,10,7,15, While I was watching it I never seen a case where it went down low enough for the WAITFORMAIL setting to kick in. Watching the proc/work directory you can see files moving in and out, but never really emptying out. Its possible what I am seeing is an anomaly or maybe I am interpreting it wrong. Maybe David can comment on this. Darrell invURIBL - Intelligent URI filtering plug-in for Declude, mxGuard, and ORF. Stop spam at the source the spamvertised domain. More effective than traditional RBL's. Try it today - http://www.invariantsystems.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.
[Declude.JunkMail] OT: Windows Desktop Shortcuts
Hi, all- I don't normally pass stuff like this along, but I found this to be an interesting and potentially dangerous feature of which I was completely unaware. Create a shortcut to Google on your desktop. Name it g (no quotes). Open IE and enter g in the address field (no http://, just g)) . Look at Google magically appear. Enter C:\ in the address field. Watch IE turn into Windows Explorer. Create a shortcut to Notepad. Name it AOL. Open IE and enter AOL. Watch Notepad open up. Same thing with aol.com --- but not with www.aol.com, which actually does give you AOL for some reason. The desktop shortcuts take precedence over the HOSTS file, which of course takes precedence over DNS. I entered g into my HOSTS file with the IP of my website. I created a shortcut named g pointing to Google, as above. I opened IE and entered g and got Google. Then I closed IE, renamed the shortcut, reopened IE and entered g. I got my website. The potential for weirdness and mischief seems extremely high here... Thanks (I think!) to Roger Grimes of Info World for getting me started on this one. -Dave Doherty Skywaves, Inc. --- 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.
Re: [Declude.JunkMail] Experience with 4.x
Matt, That would explain why the behavior on my server is different than yours - I do not use the WINSOCKCLEANUP and thus see the alternate behavior. Darrell --- Check out http://www.invariantsystems.com for utilities for Declude, Imail, mxGuard, and ORF. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers. David Barker writes: The purpose of WINSOCKCLEANUPON 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. As WINSOCKCLEANUP is to be used only by those who experience DNS issues I would suggest running your tests again with WINSOCKCLEANUP commented out and see how the behavior differs. Also having the WAITFORMAIL to low can cause the CPU to process very high as it is constantly checking the \proc I would suggest a minimum of 500-1000 David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Monday, May 22, 2006 8:12 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Experience with 4.x Darrell, I put up two Windows Explorer windows side-by-side under normal volume and the pattern was consistent where the proc folder grows while the work folder shrinks until the work folder hits zero at which point the proc folder empties out and everything lands in work and then the pattern repeats with proc growing while work shrinks. My settings are as follows: THREADS50 WAITFORMAIL100 WAITFORTHREADS10 WAITBETWEENTHREADS50 WINSOCKCLEANUPON AUTOREVIEWON INVITEFIXON Matt Darrell ([EMAIL PROTECTED]) wrote: It's a faulty design that leaves more than half a server's CPU capacity unused due to the mere fact that they wait for all threads to complete before moving in a new batch. I can't speak to what you see on your server, but that is not how it is running on my server. I just double checked again to make sure I am not crazy, but as I watch the thread count on my server (decludeproc) the threads fluctuate between 7 - 30 ( threads currently set to 50). It is not uncommon to see the threads move as follow: 11,8,10,7,15, While I was watching it I never seen a case where it went down low enough for the WAITFORMAIL setting to kick in. Watching the proc/work directory you can see files moving in and out, but never really emptying out. Its possible what I am seeing is an anomaly or maybe I am interpreting it wrong. Maybe David can comment on this. Darrell invURIBL - Intelligent URI filtering plug-in for Declude, mxGuard, and ORF. Stop spam at the source the spamvertised domain. More effective than traditional RBL's. Try it today - http://www.invariantsystems.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.
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 WINSOCKCLEANUPON 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.
RE: [Declude.JunkMail] Experience with 4.x
Mike, 1. The WINSOCKCLEANUPON 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 WINSOCKCLEANUPON 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.
[Declude.JunkMail] New version - any hints
Hi David, You said: 5. Make sure you have the latest version of decludeproc ... There should be a release later today or tommorow. Any ints as to what is in this version? Goran Jovanovic Omega Network Solutions --- 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.
Re: [Declude.JunkMail] Experience with 4.x
Andrew has always been the King of Comments. Nick Hayer wrote: Very nice! It looks like Matt has taught you well on how to comment a file :) -Nick Colbeck, Andrew wrote: I'd second that... on both the observed behaviour and the request for documentation. I'mattaching my highlycommented declude.cfg as a reasonable sample. Andrew 8) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Sent: Tuesday, May 23, 2006 10:36 AM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Experience with 4.x David, That did the trick. I can't even see any messages in my proc folder any more. I might suggest adding your explanation to the comments in the file just in case others feel the need to turn this on like I did. I recalled the issues from the list and I turned it on because I didn't want the possibility of DNS crapping out and the leakage that this would cause. Here's a screen cap of what my processor graph looks like now: Thanks, Matt David Barker wrote: The purpose of WINSOCKCLEANUPON 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. As WINSOCKCLEANUP is to be used only by those who experience DNS issues I would suggest running your tests again with WINSOCKCLEANUP commented out and see how the behavior differs. Also having the WAITFORMAIL to low can cause the CPU to process very high as it is constantly checking the \proc I would suggest a minimum of 500-1000 David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Sent: Monday, May 22, 2006 8:12 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Experience with 4.x Darrell, I put up two Windows Explorer windows side-by-side under normal volume and the pattern was consistent where the proc folder grows while the work folder shrinks until the work folder hits zero at which point the proc folder empties out and everything lands in work and then the pattern repeats with proc growing while work shrinks. My settings are as follows: THREADS50 WAITFORMAIL100 WAITFORTHREADS10 WAITBETWEENTHREADS50 WINSOCKCLEANUPON AUTOREVIEWON INVITEFIXON Matt Darrell ([EMAIL PROTECTED]) wrote: It's a faulty design that leaves more than half a server's CPU capacity unused due to the mere fact that they wait for all threads to complete before moving in a new batch. I can't speak to what you see on your server, but that is not how it is running on my server. I just double checked again to make sure I am not crazy, but as I watch the thread count on my server (decludeproc) the threads fluctuate between 7 - 30 ( threads currently set to 50). It is not uncommon to see the threads move as follow: 11,8,10,7,15, While I was watching it I never seen a case where it went down low enough for the WAITFORMAIL setting to kick in. Watching the proc/work directory you can see files moving in and out, but never really emptying out. Its possible what I am seeing is an anomaly or maybe I am interpreting it wrong. Maybe David can comment on this. Darrell invURIBL - Intelligent URI filtering plug-in for Declude, mxGuard, and ORF. Stop spam at the source the spamvertised domain. More effective than traditional RBL's. Try it today - http://www.invariantsystems.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.
Re: [Declude.JunkMail] Experience with 4.x
Andrew, Thanks for your notes and their history. I'm using the following settings right now: THREADS 30 WAITFORMAIL 500 WAITFORTHREADS 200 WAITBETWEENTHREADS 100 WINSOCKCLEANUP OFF INVITEFIX ON AUTOREVIEW ON There are a few reasons for trying these values. THREADS 30 - I'm pretty confident that dual 3.2 Ghz Xeons and RAID can only handle 30 threads with average messages. In reality, one single message can spike the system to 100%, but these are uncommon. I figure that if I open this up too wide and I am dealing with a backup or something, launching more threads when at 100% CPU utilization will actually slow the system down. This was the same with 2.x and before. There is added overhead to managing threads and you don't want that to happen on top of 100% CPU utilization. I am going to back up my server later tonight to see if I can't find what the magic number is since I don't want to be below that magic number, and it would probably be best to be a little above it. WAITFORMAIL 500 - On my server, this never kicks in, but if it did, it wouldn't make sense to delay for too long because I could build up messages. A half second seems good. WAITFORTHREADS 200 - This apparently kicks in only when I reach my thread limit; sort of like a throttle. I don't want it to be too long because this should only happen when I am hammered, but it is wise not to keep hammering when you are at 100%. Sort of a mixed bag choice here. WAITBETWEENTHREADS 100 - I see this setting as being the biggest issue with sizing a server. Setting it at 100 ms means that I can only handle 10 messages per second, and this establishes an upper limit for what the server can do. I currently average about 5 messages per second coming from my gateways at peak hours, so I figured that to be safe, I should double that value. INVITEFIX ON - I have it on because it comes on by default and I don't know any better. I know nothing about the cause for needing this outside of brief comments. It seems strange that my Declude setup could ruin an invitation unless I was using footers. If this is only triggered by footer use, I would like to know so that I could turn it off. I would imagine that this causes extra load to do the check. AUTOREVIEW ON - I have this on for the same reason that Andrew pointed out. When I restart Decludeproc, messages land in my review folder, and I don't wish to keep manually fishing things out. If there is an issue with looping, it would be wise for Declude to make this only trigger say every 15 minutes instead of more regularly. Feel free to add to this if you want. Matt Colbeck, Andrew wrote: I'd second that... on both the observed behaviour and the request for documentation. I'mattaching my highlycommented declude.cfg as a reasonable sample. Andrew 8) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Sent: Tuesday, May 23, 2006 10:36 AM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Experience with 4.x David, That did the trick. I can't even see any messages in my proc folder any more. I might suggest adding your explanation to the comments in the file just in case others feel the need to turn this on like I did. I recalled the issues from the list and I turned it on because I didn't want the possibility of DNS crapping out and the leakage that this would cause. Here's a screen cap of what my processor graph looks like now: Thanks, Matt David Barker wrote: The purpose of WINSOCKCLEANUPON 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. As WINSOCKCLEANUP is to be used only by those who experience DNS issues I would suggest running your tests again with WINSOCKCLEANUP commented out and see how the behavior differs. Also having the WAITFORMAIL to low can cause the CPU to process very high as it is constantly checking the \proc I would suggest a minimum of 500-1000 David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Sent: Monday, May 22, 2006 8:12 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Experience with 4.x Darrell, I put up two Windows Explorer windows side-by-side under normal volume and the pattern was consistent where the proc folder grows while the work folder shrinks until the work folder hits zero at which point the proc folder empties out and everything lands in work and then the pattern repeats with proc growing while work shrinks. My settings are as follows: THREADS50 WAITFORMAIL100 WAITFORTHREADS10 WAITBETWEENTHREADS50 WINSOCKCLEANUPON AUTOREVIEWON INVITEFIXON Matt Darrell ([EMAIL PROTECTED]) wrote:
RE: [Declude.JunkMail] Experience with 4.x
Thanks, Nick. It's a defensivemechanism I've used for years: keep the documentation with the settings. I often do the same with registry keys by adding a text string and blathering away. Adding dates and initials is also a good idea. Andrew 8) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick HayerSent: Tuesday, May 23, 2006 11:33 AMTo: Declude.JunkMail@declude.comSubject: Re: [Declude.JunkMail] Experience with 4.x Very nice!It looks like Matt has taught you well on how to comment a file :)-NickColbeck, Andrew wrote: I'd second that... on both the observed behaviour and the request for documentation. I'mattaching my highlycommented declude.cfg as a reasonable sample. Andrew 8) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of MattSent: Tuesday, May 23, 2006 10:36 AMTo: Declude.JunkMail@declude.comSubject: Re: [Declude.JunkMail] Experience with 4.xDavid,That did the trick. I can't even see any messages in my proc folder any more. I might suggest adding your explanation to the comments in the file just in case others feel the need to turn this on like I did. I recalled the issues from the list and I turned it on because I didn't want the possibility of DNS crapping out and the leakage that this would cause.Here's a screen cap of what my processor graph looks like now: Thanks,MattDavid Barker wrote: The purpose of WINSOCKCLEANUPON 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. As WINSOCKCLEANUP is to be used only by those who experience DNS issues I would suggest running your tests again with WINSOCKCLEANUP commented out and see how the behavior differs. Also having the WAITFORMAIL to low can cause the CPU to process very high as it is constantly checking the \proc I would suggest a minimum of 500-1000 David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Sent: Monday, May 22, 2006 8:12 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Experience with 4.x Darrell, I put up two Windows Explorer windows side-by-side under normal volume and the pattern was consistent where the proc folder grows while the work folder shrinks until the work folder hits zero at which point the proc folder empties out and everything lands in work and then the pattern repeats with proc growing while work shrinks. My settings are as follows: THREADS50 WAITFORMAIL100 WAITFORTHREADS10 WAITBETWEENTHREADS50 WINSOCKCLEANUPON AUTOREVIEWON INVITEFIXON Matt Darrell ([EMAIL PROTECTED]) wrote: It's a faulty design that leaves more than half a server's CPU capacity unused due to the mere fact that they wait for all threads to complete before moving in a new batch. I can't speak to what you see on your server, but that is not how it is running on my server. I just double checked again to make sure I am not crazy, but as I watch the thread count on my server (decludeproc) the threads fluctuate between 7 - 30 ( threads currently set to 50). It is not uncommon to see the threads move as follow: 11,8,10,7,15, While I was watching it I never seen a case where it went down low enough for the WAITFORMAIL setting to kick in. Watching the proc/work directory you can see files moving in and out, but never really emptying out. Its possible what I am seeing is an anomaly or maybe I am interpreting it wrong. Maybe David can comment on this. Darrell invURIBL - Intelligent URI filtering plug-in for Declude, mxGuard, and ORF. Stop spam at the source the spamvertised domain. More effective than traditional RBL's. Try it today - http://www.invariantsystems.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.
RE: [Declude.JunkMail] Experience with 4.x
"Those who cannot remember their mistakes are doomed to repeat them!" Andrew 8) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MattSent: Tuesday, May 23, 2006 12:26 PMTo: Declude.JunkMail@declude.comSubject: Re: [Declude.JunkMail] Experience with 4.x Andrew has always been the King of Comments.Nick Hayer wrote: Very nice!It looks like Matt has taught you well on how to comment a file :)-NickColbeck, Andrew wrote: I'd second that... on both the observed behaviour and the request for documentation. I'mattaching my highlycommented declude.cfg as a reasonable sample. Andrew 8) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of MattSent: Tuesday, May 23, 2006 10:36 AMTo: Declude.JunkMail@declude.comSubject: Re: [Declude.JunkMail] Experience with 4.xDavid,That did the trick. I can't even see any messages in my proc folder any more. I might suggest adding your explanation to the comments in the file just in case others feel the need to turn this on like I did. I recalled the issues from the list and I turned it on because I didn't want the possibility of DNS crapping out and the leakage that this would cause.Here's a screen cap of what my processor graph looks like now: Thanks,MattDavid Barker wrote: The purpose of WINSOCKCLEANUPON 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. As WINSOCKCLEANUP is to be used only by those who experience DNS issues I would suggest running your tests again with WINSOCKCLEANUP commented out and see how the behavior differs. Also having the WAITFORMAIL to low can cause the CPU to process very high as it is constantly checking the \proc I would suggest a minimum of 500-1000 David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Sent: Monday, May 22, 2006 8:12 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Experience with 4.x Darrell, I put up two Windows Explorer windows side-by-side under normal volume and the pattern was consistent where the proc folder grows while the work folder shrinks until the work folder hits zero at which point the proc folder empties out and everything lands in work and then the pattern repeats with proc growing while work shrinks. My settings are as follows: THREADS50 WAITFORMAIL100 WAITFORTHREADS10 WAITBETWEENTHREADS50 WINSOCKCLEANUPON AUTOREVIEWON INVITEFIXON Matt Darrell ([EMAIL PROTECTED]) wrote: It's a faulty design that leaves more than half a server's CPU capacity unused due to the mere fact that they wait for all threads to complete before moving in a new batch. I can't speak to what you see on your server, but that is not how it is running on my server. I just double checked again to make sure I am not crazy, but as I watch the thread count on my server (decludeproc) the threads fluctuate between 7 - 30 ( threads currently set to 50). It is not uncommon to see the threads move as follow: 11,8,10,7,15, While I was watching it I never seen a case where it went down low enough for the WAITFORMAIL setting to kick in. Watching the proc/work directory you can see files moving in and out, but never really emptying out. Its possible what I am seeing is an anomaly or maybe I am interpreting it wrong. Maybe David can comment on this. Darrell invURIBL - Intelligent URI filtering plug-in for Declude, mxGuard, and ORF. Stop spam at the source the spamvertised domain. More effective than traditional RBL's. Try it today - http://www.invariantsystems.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.
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 WINSOCKCLEANUPON 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 WINSOCKCLEANUPON 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.
Re: [Declude.JunkMail] Experience with 4.x
I have an idea. Maybe this should be triggered automatically if every DNS lookup times out on a single message. That way we wouldn't have to set it, and it would only be called when conditions warrant. Matt Colbeck, Andrew wrote: 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 WINSOCKCLEANUPON 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 WINSOCKCLEANUPON 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.
RE: [Declude.JunkMail] New version - any hints
4 items .. Releasing tomorrow morning: 1. Increased performance for the AVG DB updates 2. AVG virus name reporting fixed 3. Configurable times for AVG updates 4. Buffer overflow fix caused by format of certain 'broken' emails David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Goran Jovanovic Sent: Tuesday, May 23, 2006 11:56 AM To: Declude.JunkMail@declude.com Subject: [Declude.JunkMail] New version - any hints Hi David, You said: 5. Make sure you have the latest version of decludeproc ... There should be a release later today or tommorow. Any ints as to what is in this version? Goran Jovanovic Omega Network Solutions --- 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.
RE: [Declude.JunkMail] Experience with 4.x
David, that sounds like the case I saw that noted that his firewall wasn't allowing outbound DNS and also noted that implementing WINSOCKCLEANUP ON worked for him. I wasn't at all sure that the winsock fix was relevant for him! I'll keep watching my folders. Perhaps I'll get lucky enough to need to the fix and may offer some further insight here. Andrew. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Barker Sent: Tuesday, May 23, 2006 3:30 PM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Experience with 4.x The only way that we have detected this was with Imail and mail being stuck in the spool. ...network stack causing loss of functionality for basic network operations is generic but if I remember correctly when this happened the admin was not even able to ping an outside server, which would suggest to me other IP communications fail as well. David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Colbeck, Andrew Sent: Tuesday, May 23, 2006 6: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 WINSOCKCLEANUPON 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 WINSOCKCLEANUPON 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. ---
RE: [Declude.JunkMail] Experience with 4.x
Thanks for the help. Any feedback appreciated. David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Colbeck, Andrew Sent: Tuesday, May 23, 2006 6:36 PM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Experience with 4.x David, that sounds like the case I saw that noted that his firewall wasn't allowing outbound DNS and also noted that implementing WINSOCKCLEANUP ON worked for him. I wasn't at all sure that the winsock fix was relevant for him! I'll keep watching my folders. Perhaps I'll get lucky enough to need to the fix and may offer some further insight here. Andrew. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Barker Sent: Tuesday, May 23, 2006 3:30 PM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Experience with 4.x The only way that we have detected this was with Imail and mail being stuck in the spool. ...network stack causing loss of functionality for basic network operations is generic but if I remember correctly when this happened the admin was not even able to ping an outside server, which would suggest to me other IP communications fail as well. David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Colbeck, Andrew Sent: Tuesday, May 23, 2006 6: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 WINSOCKCLEANUPON 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
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 WINSOCKCLEANUPON 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 WINSOCKCLEANUPON 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
[Declude.JunkMail] OT Undeliverable Mail to ATT.net
Hello all, A little off topic but is any one seeing undeliverable mail to att.net. I have been seeing 450-Busy try again later evertime we connect to att.net. Any idea on what is going on with att.net Lenny Bauman President LRBCG.COM, Inc. 419-621-5770 1-888-621-6475 --- [This E-mail scanned for viruses by LRBCG.COM, Inc.] --- 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.
RE: [Declude.JunkMail] Experience with 4.x
This sounds like me. I found some notes from my issue back in December. When upgrading to v 3 from v 2x we would loose connectivity every 3 or 4 hours. We finally figured out Decludeproc needs to get out on port 53 for some dns function. We allowed outbound port 53 for dns and the problem went away. This apparently is for the initial authorization of the software. I think this is a one time event. Upgrading from V3 to V4 we had the same problem. It was resolved with a phone call to Declude and the discovery that that the initial authorization had been moved from port 53 to port 25. After making that change to the firewall V4 runs fine. Good luck John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Colbeck, Andrew Sent: Tuesday, May 23, 2006 3:36 PM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Experience with 4.x David, that sounds like the case I saw that noted that his firewall wasn't allowing outbound DNS and also noted that implementing WINSOCKCLEANUP ON worked for him. I wasn't at all sure that the winsock fix was relevant for him! I'll keep watching my folders. Perhaps I'll get lucky enough to need to the fix and may offer some further insight here. Andrew. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Barker Sent: Tuesday, May 23, 2006 3:30 PM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Experience with 4.x The only way that we have detected this was with Imail and mail being stuck in the spool. ...network stack causing loss of functionality for basic network operations is generic but if I remember correctly when this happened the admin was not even able to ping an outside server, which would suggest to me other IP communications fail as well. David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Colbeck, Andrew Sent: Tuesday, May 23, 2006 6: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 WINSOCKCLEANUPON 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
Re: [Declude.JunkMail] OT Undeliverable Mail to ATT.net
Hi Lenny- This was raised a few weeks ago by somebody else, either on this list or the IMail list. I never saw a resolution to it beyond keep trying... -Dave Doherty Skywaves, Inc. - Original Message - From: Lenny Bauman [EMAIL PROTECTED] To: Declude.JunkMail@declude.com Sent: Tuesday, May 23, 2006 6:42 PM Subject: [Declude.JunkMail] OT Undeliverable Mail to ATT.net Hello all, A little off topic but is any one seeing undeliverable mail to att.net. I have been seeing 450-Busy try again later evertime we connect to att.net. Any idea on what is going on with att.net Lenny Bauman President LRBCG.COM, Inc. 419-621-5770 1-888-621-6475 --- [This E-mail scanned for viruses by LRBCG.COM, Inc.] --- 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.
RE: [Declude.JunkMail] Experience with 4.x
Thanks for ringing in, John. Wow, this new-fangled support forum thingy does have it's uses! Andrew 8) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Doyle Sent: Tuesday, May 23, 2006 4:13 PM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Experience with 4.x This sounds like me. I found some notes from my issue back in December. When upgrading to v 3 from v 2x we would loose connectivity every 3 or 4 hours. We finally figured out Decludeproc needs to get out on port 53 for some dns function. We allowed outbound port 53 for dns and the problem went away. This apparently is for the initial authorization of the software. I think this is a one time event. Upgrading from V3 to V4 we had the same problem. It was resolved with a phone call to Declude and the discovery that that the initial authorization had been moved from port 53 to port 25. After making that change to the firewall V4 runs fine. Good luck John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Colbeck, Andrew Sent: Tuesday, May 23, 2006 3:36 PM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Experience with 4.x David, that sounds like the case I saw that noted that his firewall wasn't allowing outbound DNS and also noted that implementing WINSOCKCLEANUP ON worked for him. I wasn't at all sure that the winsock fix was relevant for him! I'll keep watching my folders. Perhaps I'll get lucky enough to need to the fix and may offer some further insight here. Andrew. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Barker Sent: Tuesday, May 23, 2006 3:30 PM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Experience with 4.x The only way that we have detected this was with Imail and mail being stuck in the spool. ...network stack causing loss of functionality for basic network operations is generic but if I remember correctly when this happened the admin was not even able to ping an outside server, which would suggest to me other IP communications fail as well. David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Colbeck, Andrew Sent: Tuesday, May 23, 2006 6: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 WINSOCKCLEANUPON
RE: [Declude.JunkMail] Experience with 4.x
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 WINSOCKCLEANUPON 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
Re: [Declude.JunkMail] OT Undeliverable Mail to ATT.net
We have seen this issue alot. We attempted contacting ATT and getting higher than 1st level tech support, but found that to be more difficult than exposing a covert, undercover CIA agent. Finally, we connected with a supervisor, who, with a phone in each ear, told us that the real tech support guys said they were aware of it but nothing could be done. I later was told about an article which indicated that ATT was going to introduce a new service called 'fast e-mail' (or something similar) for an additional fee. Go figure. Tuesday, May 23, 2006, 5:42:54 PM, Lenny Bauman [EMAIL PROTECTED] wrote: LB Hello all, LB A little off topic but is any one seeing undeliverable mail to att.net. I LB have been seeing 450-Busy try again later evertime we connect to att.net. LB Any idea on what is going on with att.net LB Lenny Bauman LB President LB LRBCG.COM, Inc. LB 419-621-5770 LB 1-888-621-6475 LB --- LB [This E-mail scanned for viruses by LRBCG.COM, Inc.] LB --- LB This E-mail came from the Declude.JunkMail mailing list. To LB unsubscribe, just send an E-mail to [EMAIL PROTECTED], and LB type unsubscribe Declude.JunkMail. The archives can be found LB at http://www.mail-archive.com. Don Brown - Dallas, Texas USA Internet Concepts, Inc. [EMAIL PROTECTED] http://www.inetconcepts.net (972) 788-2364Fax: (972) 788-5049 --- 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.
