Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Dave, Just call the number and there will be an option for getting hotfixes before you get tossed into the pay for support system. Just give the person the hotfix number and your information and they will E-mail you a link to download it almost immediately. It's actually very easy, they just do a very poor job of explaining how it works on their site. Matt Dave Doherty wrote: Matt- The link http://support.microsoft.com/?kbid=830381 leads to a bunch of pay support resources. Did you have to pay MS for this fix? -Dave - Original Message - From: Matt To: Declude.JunkMail@declude.com Sent: Tuesday, January 25, 2005 2:01 PM Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Yeah, that's what I meant :) I also screwed up the stat for what MS DNS 2003 can apparently handle; it is in fact 9,500 per second and not minute. http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=""> Matt John Tolmachoff (Lists) wrote: Service Pack 2? For Windows 2003? Service Pack 1 is in beta right now. John Tolmachoff Engineer/Consultant/Owner eServices For You -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Sent: Tuesday, January 25, 2005 10:25 AM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Well, I can say definitively that the hotfix worked. My DNS process is averaging less than 1% of CPU now during full traffic and 12 hours after the last restart with a very heavy config and well over 100,000 messages a day. I saw an article on MS's site showing that their DNS server could handle 9,500 requests per minute running on a single 733 MHz processor (plus other activity), and I'm not doubting that now. The backups in Declude/IMail were definitely being caused by the sluggishness of the DNS queries against this server, so that problem is now fixed as well. With this cleared up, it also appears that the server as a whole is running faster than the previous box despite the downgrade in disk I/O (all other things being the same exact platform). I can't be certain as yet, but it does appear to be about 30% more efficient so far. Windows 2003 might well be worth the money...after Service Pack 2 finally hits the streets. Matt Matt wrote: Thanks Darrell, that definitely sounds like it's the culprit: http://support.microsoft.com/?kbid=830381 This didn't come up in my searches because it is described so generically and I was searching for things like processor utilization and memory leaks. I like the part where the describe the workaround: "There is no suggested workaround. To minimize the effects of the problem, periodically stop and then restart the DNS Server service." The hotfix has been requested, I'll update the list as to whether or not this works. It certainly sounds promising. Matt Darrell ([EMAIL PROTECTED]) wrote: Matt, I seen a few articles about memory leaks in Win2K3 DNS. One specific one comes to mind about a leak when adding zones via scripting. Another one that we ran into (internally) was KB 830381. (Server Responsiveness Degrades and Queries Time Out When You Run the DNS Server Service). Darrell --- Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers. - Original Message - From: "Matt" <[EMAIL PROTECTED]> To: Sent: Monday, January 24, 2005 10:31 PM Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS I found MaxQueProc in the registry and changed that to 60. There is no GUI config for this option. I also looked at the issue with MS DNS 2003. After a restart of DNS, utilization dropped from an average of about 25% to under 1% (I had it in performance monitor)...but then over the next couple of hours, it has crept back up to 10%. I have watched it enough to verify that it's utilization grows consistently over time. Disabling the EDNS thing has no effect. I've found nothing really telling about this in Google, but it looks like a classic memory leak. This installation was fresh and there is hardly any
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Matt- The link http://support.microsoft.com/?kbid=830381 leads to a bunch of pay support resources. Did you have to pay MS for this fix? -Dave - Original Message - From: Matt To: Declude.JunkMail@declude.com Sent: Tuesday, January 25, 2005 2:01 PM Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Yeah, that's what I meant :)I also screwed up the stat for what MS DNS 2003 can apparently handle; it is in fact 9,500 per second and not minute.http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url="">MattJohn Tolmachoff (Lists) wrote: Service Pack 2? For Windows 2003? Service Pack 1 is in beta right now. John Tolmachoff Engineer/Consultant/Owner eServices For You -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of MattSent: Tuesday, January 25, 2005 10:25 AMTo: Declude.JunkMail@declude.comSubject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Well, I can say definitively that the hotfix worked. My DNS process is averaging less than 1% of CPU now during full traffic and 12 hours after the last restart with a very heavy config and well over 100,000 messages a day. I saw an article on MS's site showing that their DNS server could handle 9,500 requests per minute running on a single 733 MHz processor (plus other activity), and I'm not doubting that now.The backups in Declude/IMail were definitely being caused by the sluggishness of the DNS queries against this server, so that problem is now fixed as well.With this cleared up, it also appears that the server as a whole is running faster than the previous box despite the downgrade in disk I/O (all other things being the same exact platform). I can't be certain as yet, but it does appear to be about 30% more efficient so far. Windows 2003 might well be worth the money...after Service Pack 2 finally hits the streets.MattMatt wrote: Thanks Darrell, that definitely sounds like it's the culprit: http://support.microsoft.com/?kbid=830381This didn't come up in my searches because it is described so generically and I was searching for things like processor utilization and memory leaks. I like the part where the describe the workaround: "There is no suggested workaround. To minimize the effects of the problem, periodically stop and then restart the DNS Server service."The hotfix has been requested, I'll update the list as to whether or not this works. It certainly sounds promising.MattDarrell ([EMAIL PROTECTED]) wrote: Matt, I seen a few articles about memory leaks in Win2K3 DNS. One specific onecomes to mind about a leak when adding zones via scripting. Another onethat we ran into (internally) was KB 830381. (Server ResponsivenessDegrades and Queries Time Out When You Run the DNS Server Service). Darrell ---Check out http://www.invariantsystems.com for utilities for Declude AndImail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTGIntegration, and Log Parsers.- Original Message - From: "Matt" <[EMAIL PROTECTED]>To: Sent: Monday, January 24, 2005 10:31 PMSubject: Re: [Declude.JunkMail] Overflow directory and a note about Windows2003 DNS I found MaxQueProc in the registry and changed that to 60. There is noGUI config for this option. I also looked at the issue with MS DNS 2003. After a restart of DNS,utilization dropped from an average of about 25% to under 1% (I had itin performance monitor)...but then over the next couple of hours, it hascrept back up to 10%. I have watched it enough to verify that it'sutilization grows consistently over time. Disabling the EDNS thing hasno effect. I've found nothing really telling about this in Google, butit looks like a classic memory leak. This installation was fresh andthere is hardly anything installed on it. I would be a bit surprised tosee a memory leak in DNS go undetected/unfixed at this point. If anyoneelse has experienced this, or can confirm my findings, please speak up.I was intending on using this server for my Web hosting DNS, but thismay keep me from going there. MattR. Scott Perry wrote: You seemed to indicate that service launched processes count againstthe threads...meaning that smtp32.exe launches declude.exe, whichlaunches F-Prot and McAfee. So would this count for 4 threads (notaccording to Declude, but Windows/IMail)? What about Sniffer andeach external test that I have configured within Declude, would thosecount as well? Unfortunately, we are not aware of
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Matt, We seen the same exact results you seen after we applied the hotfix. I am glad to see it worked for you as well. Darrell ---Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers. - Original Message - From: Matt To: Declude.JunkMail@declude.com Sent: Tuesday, January 25, 2005 1:24 PM Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Well, I can say definitively that the hotfix worked. My DNS process is averaging less than 1% of CPU now during full traffic and 12 hours after the last restart with a very heavy config and well over 100,000 messages a day. I saw an article on MS's site showing that their DNS server could handle 9,500 requests per minute running on a single 733 MHz processor (plus other activity), and I'm not doubting that now.The backups in Declude/IMail were definitely being caused by the sluggishness of the DNS queries against this server, so that problem is now fixed as well.With this cleared up, it also appears that the server as a whole is running faster than the previous box despite the downgrade in disk I/O (all other things being the same exact platform). I can't be certain as yet, but it does appear to be about 30% more efficient so far. Windows 2003 might well be worth the money...after Service Pack 2 finally hits the streets.MattMatt wrote: Thanks Darrell, that definitely sounds like it's the culprit: http://support.microsoft.com/?kbid=830381This didn't come up in my searches because it is described so generically and I was searching for things like processor utilization and memory leaks. I like the part where the describe the workaround: "There is no suggested workaround. To minimize the effects of the problem, periodically stop and then restart the DNS Server service."The hotfix has been requested, I'll update the list as to whether or not this works. It certainly sounds promising.MattDarrell ([EMAIL PROTECTED]) wrote: Matt, I seen a few articles about memory leaks in Win2K3 DNS. One specific one comes to mind about a leak when adding zones via scripting. Another one that we ran into (internally) was KB 830381. (Server Responsiveness Degrades and Queries Time Out When You Run the DNS Server Service). Darrell --- Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers. - Original Message - From: "Matt" <[EMAIL PROTECTED]> To: Sent: Monday, January 24, 2005 10:31 PM Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS I found MaxQueProc in the registry and changed that to 60. There is no GUI config for this option. I also looked at the issue with MS DNS 2003. After a restart of DNS, utilization dropped from an average of about 25% to under 1% (I had it in performance monitor)...but then over the next couple of hours, it has crept back up to 10%. I have watched it enough to verify that it's utilization grows consistently over time. Disabling the EDNS thing has no effect. I've found nothing really telling about this in Google, but it looks like a classic memory leak. This installation was fresh and there is hardly anything installed on it. I would be a bit surprised to see a memory leak in DNS go undetected/unfixed at this point. If anyone else has experienced this, or can confirm my findings, please speak up. I was intending on using this server for my Web hosting DNS, but this may keep me from going there. Matt R. Scott Perry wrote: You seemed to indicate that service launched processes count against the threads...meaning that smtp32.exe launches declude.exe, which launches F-Prot and McAfee. So would this count for 4 threads (not according to Declude, but Windows/IMail)? What about Sniffer and each external test that I have configured within Declude, would those count as well? Unfortunately, we are not aware of a way to determine if a process was started by a service or not. Currently, Declude looks for declude.exe, smtp32.exe, scan.exe, F-Prot.exe processes (and any processes listed in the rarely used DAISYCHAIN option). Note that SMTPD32.exe -- the IMail process/service that starts Declude -- is just a single process, so it will only count once. Message Sniffer and other external tests won't count, since Declude doesn't specifically look for it (but it does indeed count as a service-started process, and could cause the memory limit to be reached). However, there would only b
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Yeah, that's what I meant :) I also screwed up the stat for what MS DNS 2003 can apparently handle; it is in fact 9,500 per second and not minute. http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=""> Matt John Tolmachoff (Lists) wrote: Service Pack 2? For Windows 2003? Service Pack 1 is in beta right now. John Tolmachoff Engineer/Consultant/Owner eServices For You -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Sent: Tuesday, January 25, 2005 10:25 AM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Well, I can say definitively that the hotfix worked. My DNS process is averaging less than 1% of CPU now during full traffic and 12 hours after the last restart with a very heavy config and well over 100,000 messages a day. I saw an article on MS's site showing that their DNS server could handle 9,500 requests per minute running on a single 733 MHz processor (plus other activity), and I'm not doubting that now. The backups in Declude/IMail were definitely being caused by the sluggishness of the DNS queries against this server, so that problem is now fixed as well. With this cleared up, it also appears that the server as a whole is running faster than the previous box despite the downgrade in disk I/O (all other things being the same exact platform). I can't be certain as yet, but it does appear to be about 30% more efficient so far. Windows 2003 might well be worth the money...after Service Pack 2 finally hits the streets. Matt Matt wrote: Thanks Darrell, that definitely sounds like it's the culprit: http://support.microsoft.com/?kbid=830381 This didn't come up in my searches because it is described so generically and I was searching for things like processor utilization and memory leaks. I like the part where the describe the workaround: "There is no suggested workaround. To minimize the effects of the problem, periodically stop and then restart the DNS Server service." The hotfix has been requested, I'll update the list as to whether or not this works. It certainly sounds promising. Matt Darrell ([EMAIL PROTECTED]) wrote: Matt, I seen a few articles about memory leaks in Win2K3 DNS. One specific one comes to mind about a leak when adding zones via scripting. Another one that we ran into (internally) was KB 830381. (Server Responsiveness Degrades and Queries Time Out When You Run the DNS Server Service). Darrell --- Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers. - Original Message - From: "Matt" <[EMAIL PROTECTED]> To: Sent: Monday, January 24, 2005 10:31 PM Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS I found MaxQueProc in the registry and changed that to 60. There is no GUI config for this option. I also looked at the issue with MS DNS 2003. After a restart of DNS, utilization dropped from an average of about 25% to under 1% (I had it in performance monitor)...but then over the next couple of hours, it has crept back up to 10%. I have watched it enough to verify that it's utilization grows consistently over time. Disabling the EDNS thing has no effect. I've found nothing really telling about this in Google, but it looks like a classic memory leak. This installation was fresh and there is hardly anything installed on it. I would be a bit surprised to see a memory leak in DNS go undetected/unfixed at this point. If anyone else has experienced this, or can confirm my findings, please speak up. I was intending on using this server for my Web hosting DNS, but this may keep me from going there. Matt R. Scott Perry wrote: You seemed to indicate that service launched processes count against the threads...meaning that smtp32.exe launches declude.exe, which launches F-Prot and McAfee. So would this count for 4 threads (not according to Declude, but Windows/IMail)? What about Sniffer and each external test that I have configured within Declude, would those count as well? Unfortunately, we are not aware of a way to determine if a process was started by a service or not. Currently, Declude looks for declude.exe, smtp32.exe, scan.exe, F-Prot.exe processes (and any processes listed in the rarely used DAISYCHAIN option).
RE: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Service Pack 2? For Windows 2003? Service Pack 1 is in beta right now. John Tolmachoff Engineer/Consultant/Owner eServices For You -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Tuesday, January 25, 2005 10:25 AM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Well, I can say definitively that the hotfix worked. My DNS process is averaging less than 1% of CPU now during full traffic and 12 hours after the last restart with a very heavy config and well over 100,000 messages a day. I saw an article on MS's site showing that their DNS server could handle 9,500 requests per minute running on a single 733 MHz processor (plus other activity), and I'm not doubting that now. The backups in Declude/IMail were definitely being caused by the sluggishness of the DNS queries against this server, so that problem is now fixed as well. With this cleared up, it also appears that the server as a whole is running faster than the previous box despite the downgrade in disk I/O (all other things being the same exact platform). I can't be certain as yet, but it does appear to be about 30% more efficient so far. Windows 2003 might well be worth the money...after Service Pack 2 finally hits the streets. Matt Matt wrote: Thanks Darrell, that definitely sounds like it's the culprit: http://support.microsoft.com/?kbid=830381 This didn't come up in my searches because it is described so generically and I was searching for things like processor utilization and memory leaks. I like the part where the describe the workaround: "There is no suggested workaround. To minimize the effects of the problem, periodically stop and then restart the DNS Server service." The hotfix has been requested, I'll update the list as to whether or not this works. It certainly sounds promising. Matt Darrell ([EMAIL PROTECTED]) wrote: Matt, I seen a few articles about memory leaks in Win2K3 DNS. One specific onecomes to mind about a leak when adding zones via scripting. Another onethat we ran into (internally) was KB 830381. (Server ResponsivenessDegrades and Queries Time Out When You Run the DNS Server Service). Darrell ---Check out http://www.invariantsystems.com for utilities for Declude AndImail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTGIntegration, and Log Parsers.- Original Message - From: "Matt" <[EMAIL PROTECTED]>To: Sent: Monday, January 24, 2005 10:31 PMSubject: Re: [Declude.JunkMail] Overflow directory and a note about Windows2003 DNS I found MaxQueProc in the registry and changed that to 60. There is noGUI config for this option. I also looked at the issue with MS DNS 2003. After a restart of DNS,utilization dropped from an average of about 25% to under 1% (I had itin performance monitor)...but then over the next couple of hours, it hascrept back up to 10%. I have watched it enough to verify that it'sutilization grows consistently over time. Disabling the EDNS thing hasno effect. I've found nothing really telling about this in Google, butit looks like a classic memory leak. This installation was fresh andthere is hardly anything installed on it. I would be a bit surprised tosee a memory leak in DNS go undetected/unfixed at this point. If anyoneelse has experienced this, or can confirm my findings, please speak up.I was intending on using this server for my Web hosting DNS, but thismay keep me from going there. MattR. Scott Perry wrote: You seemed to indicate that service launched processes count againstthe threads...meaning that smtp32.exe launches declude.exe, whichlaunches F-Prot and McAfee. So would this count for 4 threads (notaccording to Declude, but Windows/IMail)? What about Sniffer andeach external test that I have configured within Declude, would thosecount as well? Unfortunately, we are not aware of a way to determine if a process wasstarted by a service or not. Currently, Declude looks fordeclude.exe, smtp32.exe, scan.exe, F-Prot.exe processes (and anyprocesses listed in the rarely used DAISYCHAIN option). Note that SMTPD32.exe -- the IMail process/service that starts Declude-- is just a single process, so it will only count once. Message Sniffer and other external tests won't count, since Decludedoesn't specifically look for it (but it does indeed count as aservice-started process, and could cause the memory limit to bereached). However, there would only be a maximum of one of them perE-mail (since Declude runs the external tests in serial, not inparallel). I also re-read the following post by Sandy: http://www.mail-archive.com/imail_forum@list.ipswitch.com/msg94576.html It seems to indicate that there is no "thread limit", but somethingelse
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Well, I can say definitively that the hotfix worked. My DNS process is averaging less than 1% of CPU now during full traffic and 12 hours after the last restart with a very heavy config and well over 100,000 messages a day. I saw an article on MS's site showing that their DNS server could handle 9,500 requests per minute running on a single 733 MHz processor (plus other activity), and I'm not doubting that now. The backups in Declude/IMail were definitely being caused by the sluggishness of the DNS queries against this server, so that problem is now fixed as well. With this cleared up, it also appears that the server as a whole is running faster than the previous box despite the downgrade in disk I/O (all other things being the same exact platform). I can't be certain as yet, but it does appear to be about 30% more efficient so far. Windows 2003 might well be worth the money...after Service Pack 2 finally hits the streets. Matt Matt wrote: Thanks Darrell, that definitely sounds like it's the culprit: http://support.microsoft.com/?kbid=830381 This didn't come up in my searches because it is described so generically and I was searching for things like processor utilization and memory leaks. I like the part where the describe the workaround: "There is no suggested workaround. To minimize the effects of the problem, periodically stop and then restart the DNS Server service." The hotfix has been requested, I'll update the list as to whether or not this works. It certainly sounds promising. Matt Darrell ([EMAIL PROTECTED]) wrote: Matt, I seen a few articles about memory leaks in Win2K3 DNS. One specific one comes to mind about a leak when adding zones via scripting. Another one that we ran into (internally) was KB 830381. (Server Responsiveness Degrades and Queries Time Out When You Run the DNS Server Service). Darrell --- Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers. - Original Message - From: "Matt" <[EMAIL PROTECTED]> To: Sent: Monday, January 24, 2005 10:31 PM Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS I found MaxQueProc in the registry and changed that to 60. There is no GUI config for this option. I also looked at the issue with MS DNS 2003. After a restart of DNS, utilization dropped from an average of about 25% to under 1% (I had it in performance monitor)...but then over the next couple of hours, it has crept back up to 10%. I have watched it enough to verify that it's utilization grows consistently over time. Disabling the EDNS thing has no effect. I've found nothing really telling about this in Google, but it looks like a classic memory leak. This installation was fresh and there is hardly anything installed on it. I would be a bit surprised to see a memory leak in DNS go undetected/unfixed at this point. If anyone else has experienced this, or can confirm my findings, please speak up. I was intending on using this server for my Web hosting DNS, but this may keep me from going there. Matt R. Scott Perry wrote: You seemed to indicate that service launched processes count against the threads...meaning that smtp32.exe launches declude.exe, which launches F-Prot and McAfee. So would this count for 4 threads (not according to Declude, but Windows/IMail)? What about Sniffer and each external test that I have configured within Declude, would those count as well? Unfortunately, we are not aware of a way to determine if a process was started by a service or not. Currently, Declude looks for declude.exe, smtp32.exe, scan.exe, F-Prot.exe processes (and any processes listed in the rarely used DAISYCHAIN option). Note that SMTPD32.exe -- the IMail process/service that starts Declude -- is just a single process, so it will only count once. Message Sniffer and other external tests won't count, since Declude doesn't specifically look for it (but it does indeed count as a service-started process, and could cause the memory limit to be reached). However, there would only be a maximum of one of them per E-mail (since Declude runs the external tests in serial, not in parallel). I also re-read the following post by Sandy: http://www.mail-archive.com/imail_forum@list.ipswitch.com/msg94576.html It seems to indicate that there is no "thread limit", but something else instead; a limit of "64 objects per thread". That's not related here. The overflow issue deals with processes, not threads. Processes are what are listed in the "Process" tab in the Task Manager (such as o
RE: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
One way of checking for a work around is to schedule a batch file say hourly to flush the cache. John Tolmachoff Engineer/Consultant/Owner eServices For You -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Monday, January 24, 2005 10:00 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Thanks Darrell, that definitely sounds like it's the culprit: http://support.microsoft.com/?kbid=830381 This didn't come up in my searches because it is described so generically and I was searching for things like processor utilization and memory leaks. I like the part where the describe the workaround: "There is no suggested workaround. To minimize the effects of the problem, periodically stop and then restart the DNS Server service." The hotfix has been requested, I'll update the list as to whether or not this works. It certainly sounds promising. Matt Darrell ([EMAIL PROTECTED]) wrote: Matt, I seen a few articles about memory leaks in Win2K3 DNS. One specific onecomes to mind about a leak when adding zones via scripting. Another onethat we ran into (internally) was KB 830381. (Server ResponsivenessDegrades and Queries Time Out When You Run the DNS Server Service). Darrell ---Check out http://www.invariantsystems.com for utilities for Declude AndImail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTGIntegration, and Log Parsers.- Original Message - From: "Matt" <[EMAIL PROTECTED]>To: Sent: Monday, January 24, 2005 10:31 PMSubject: Re: [Declude.JunkMail] Overflow directory and a note about Windows2003 DNS I found MaxQueProc in the registry and changed that to 60. There is noGUI config for this option. I also looked at the issue with MS DNS 2003. After a restart of DNS,utilization dropped from an average of about 25% to under 1% (I had itin performance monitor)...but then over the next couple of hours, it hascrept back up to 10%. I have watched it enough to verify that it'sutilization grows consistently over time. Disabling the EDNS thing hasno effect. I've found nothing really telling about this in Google, butit looks like a classic memory leak. This installation was fresh andthere is hardly anything installed on it. I would be a bit surprised tosee a memory leak in DNS go undetected/unfixed at this point. If anyoneelse has experienced this, or can confirm my findings, please speak up.I was intending on using this server for my Web hosting DNS, but thismay keep me from going there. MattR. Scott Perry wrote: You seemed to indicate that service launched processes count againstthe threads...meaning that smtp32.exe launches declude.exe, whichlaunches F-Prot and McAfee. So would this count for 4 threads (notaccording to Declude, but Windows/IMail)? What about Sniffer andeach external test that I have configured within Declude, would thosecount as well? Unfortunately, we are not aware of a way to determine if a process wasstarted by a service or not. Currently, Declude looks fordeclude.exe, smtp32.exe, scan.exe, F-Prot.exe processes (and anyprocesses listed in the rarely used DAISYCHAIN option). Note that SMTPD32.exe -- the IMail process/service that starts Declude-- is just a single process, so it will only count once. Message Sniffer and other external tests won't count, since Decludedoesn't specifically look for it (but it does indeed count as aservice-started process, and could cause the memory limit to bereached). However, there would only be a maximum of one of them perE-mail (since Declude runs the external tests in serial, not inparallel). I also re-read the following post by Sandy: http://www.mail-archive.com/imail_forum@list.ipswitch.com/msg94576.html It seems to indicate that there is no "thread limit", but somethingelse instead; a limit of "64 objects per thread". That's not related here. The overflow issue deals with processes, notthreads. Processes are what are listed in the "Process" tab in theTask Manager (such as one SMTPD32.exe process, 0 to 30 or soDeclude.exe processes, etc.). Each process can have from 1 to an(almost) infinite number of threads. I'm not sure how that might apply here. So if I am seeing overflowwith processing power to spare, I should be able to increase thethreads in IMail to a higher number than 60 in order to betterutilize my server's capacity. With memory utilization below 50%, itdoesn't seem like there is much risk in doing this, would that becorrect? Anything referring to "thread" or "threads" in IMail settings is notrelevant to this (IMail v8 introduced one or more "thread" options). Declude JunkMail looks at the Ma
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Thanks Darrell, that definitely sounds like it's the culprit: http://support.microsoft.com/?kbid=830381 This didn't come up in my searches because it is described so generically and I was searching for things like processor utilization and memory leaks. I like the part where the describe the workaround: "There is no suggested workaround. To minimize the effects of the problem, periodically stop and then restart the DNS Server service." The hotfix has been requested, I'll update the list as to whether or not this works. It certainly sounds promising. Matt Darrell ([EMAIL PROTECTED]) wrote: Matt, I seen a few articles about memory leaks in Win2K3 DNS. One specific one comes to mind about a leak when adding zones via scripting. Another one that we ran into (internally) was KB 830381. (Server Responsiveness Degrades and Queries Time Out When You Run the DNS Server Service). Darrell --- Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers. - Original Message - From: "Matt" <[EMAIL PROTECTED]> To: Sent: Monday, January 24, 2005 10:31 PM Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS I found MaxQueProc in the registry and changed that to 60. There is no GUI config for this option. I also looked at the issue with MS DNS 2003. After a restart of DNS, utilization dropped from an average of about 25% to under 1% (I had it in performance monitor)...but then over the next couple of hours, it has crept back up to 10%. I have watched it enough to verify that it's utilization grows consistently over time. Disabling the EDNS thing has no effect. I've found nothing really telling about this in Google, but it looks like a classic memory leak. This installation was fresh and there is hardly anything installed on it. I would be a bit surprised to see a memory leak in DNS go undetected/unfixed at this point. If anyone else has experienced this, or can confirm my findings, please speak up. I was intending on using this server for my Web hosting DNS, but this may keep me from going there. Matt R. Scott Perry wrote: You seemed to indicate that service launched processes count against the threads...meaning that smtp32.exe launches declude.exe, which launches F-Prot and McAfee. So would this count for 4 threads (not according to Declude, but Windows/IMail)? What about Sniffer and each external test that I have configured within Declude, would those count as well? Unfortunately, we are not aware of a way to determine if a process was started by a service or not. Currently, Declude looks for declude.exe, smtp32.exe, scan.exe, F-Prot.exe processes (and any processes listed in the rarely used DAISYCHAIN option). Note that SMTPD32.exe -- the IMail process/service that starts Declude -- is just a single process, so it will only count once. Message Sniffer and other external tests won't count, since Declude doesn't specifically look for it (but it does indeed count as a service-started process, and could cause the memory limit to be reached). However, there would only be a maximum of one of them per E-mail (since Declude runs the external tests in serial, not in parallel). I also re-read the following post by Sandy: http://www.mail-archive.com/imail_forum@list.ipswitch.com/msg94576.html It seems to indicate that there is no "thread limit", but something else instead; a limit of "64 objects per thread". That's not related here. The overflow issue deals with processes, not threads. Processes are what are listed in the "Process" tab in the Task Manager (such as one SMTPD32.exe process, 0 to 30 or so Declude.exe processes, etc.). Each process can have from 1 to an (almost) infinite number of threads. I'm not sure how that might apply here. So if I am seeing overflow with processing power to spare, I should be able to increase the threads in IMail to a higher number than 60 in order to better utilize my server's capacity. With memory utilization below 50%, it doesn't seem like there is much risk in doing this, would that be correct? Anything referring to "thread" or "threads" in IMail settings is not relevant to this (IMail v8 introduced one or more "thread" options). Declude JunkMail looks at the MaxQueProc IMail registry setting (which may also be an advanced setting in IMail Administrator, with a name such as "maximum number of processes"). Any other settings are not used. -Scott
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Matt, I seen a few articles about memory leaks in Win2K3 DNS. One specific one comes to mind about a leak when adding zones via scripting. Another one that we ran into (internally) was KB 830381. (Server Responsiveness Degrades and Queries Time Out When You Run the DNS Server Service). Darrell --- Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers. - Original Message - From: "Matt" <[EMAIL PROTECTED]> To: Sent: Monday, January 24, 2005 10:31 PM Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS > I found MaxQueProc in the registry and changed that to 60. There is no > GUI config for this option. > > I also looked at the issue with MS DNS 2003. After a restart of DNS, > utilization dropped from an average of about 25% to under 1% (I had it > in performance monitor)...but then over the next couple of hours, it has > crept back up to 10%. I have watched it enough to verify that it's > utilization grows consistently over time. Disabling the EDNS thing has > no effect. I've found nothing really telling about this in Google, but > it looks like a classic memory leak. This installation was fresh and > there is hardly anything installed on it. I would be a bit surprised to > see a memory leak in DNS go undetected/unfixed at this point. If anyone > else has experienced this, or can confirm my findings, please speak up. > I was intending on using this server for my Web hosting DNS, but this > may keep me from going there. > > Matt > > > > > R. Scott Perry wrote: > > > > >> You seemed to indicate that service launched processes count against > >> the threads...meaning that smtp32.exe launches declude.exe, which > >> launches F-Prot and McAfee. So would this count for 4 threads (not > >> according to Declude, but Windows/IMail)? What about Sniffer and > >> each external test that I have configured within Declude, would those > >> count as well? > > > > > > Unfortunately, we are not aware of a way to determine if a process was > > started by a service or not. Currently, Declude looks for > > declude.exe, smtp32.exe, scan.exe, F-Prot.exe processes (and any > > processes listed in the rarely used DAISYCHAIN option). > > > > Note that SMTPD32.exe -- the IMail process/service that starts Declude > > -- is just a single process, so it will only count once. > > > > Message Sniffer and other external tests won't count, since Declude > > doesn't specifically look for it (but it does indeed count as a > > service-started process, and could cause the memory limit to be > > reached). However, there would only be a maximum of one of them per > > E-mail (since Declude runs the external tests in serial, not in > > parallel). > > > >> I also re-read the following post by Sandy: > >> > >> > >> http://www.mail-archive.com/imail_forum@list.ipswitch.com/msg94576.html > >> > >> It seems to indicate that there is no "thread limit", but something > >> else instead; a limit of "64 objects per thread". > > > > > > That's not related here. The overflow issue deals with processes, not > > threads. Processes are what are listed in the "Process" tab in the > > Task Manager (such as one SMTPD32.exe process, 0 to 30 or so > > Declude.exe processes, etc.). Each process can have from 1 to an > > (almost) infinite number of threads. > > > >> I'm not sure how that might apply here. So if I am seeing overflow > >> with processing power to spare, I should be able to increase the > >> threads in IMail to a higher number than 60 in order to better > >> utilize my server's capacity. With memory utilization below 50%, it > >> doesn't seem like there is much risk in doing this, would that be > >> correct? > > > > > > Anything referring to "thread" or "threads" in IMail settings is not > > relevant to this (IMail v8 introduced one or more "thread" options). > > > > Declude JunkMail looks at the MaxQueProc IMail registry setting (which > > may also be an advanced setting in IMail Administrator, with a name > > such as "maximum number of processes"). Any other settings are not used. > > > >-Scott > > --- > > Declude JunkMail: The advanced anti-spam solution for IMail > > mailservers
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
I found MaxQueProc in the registry and changed that to 60. There is no GUI config for this option. I also looked at the issue with MS DNS 2003. After a restart of DNS, utilization dropped from an average of about 25% to under 1% (I had it in performance monitor)...but then over the next couple of hours, it has crept back up to 10%. I have watched it enough to verify that it's utilization grows consistently over time. Disabling the EDNS thing has no effect. I've found nothing really telling about this in Google, but it looks like a classic memory leak. This installation was fresh and there is hardly anything installed on it. I would be a bit surprised to see a memory leak in DNS go undetected/unfixed at this point. If anyone else has experienced this, or can confirm my findings, please speak up. I was intending on using this server for my Web hosting DNS, but this may keep me from going there. Matt R. Scott Perry wrote: You seemed to indicate that service launched processes count against the threads...meaning that smtp32.exe launches declude.exe, which launches F-Prot and McAfee. So would this count for 4 threads (not according to Declude, but Windows/IMail)? What about Sniffer and each external test that I have configured within Declude, would those count as well? Unfortunately, we are not aware of a way to determine if a process was started by a service or not. Currently, Declude looks for declude.exe, smtp32.exe, scan.exe, F-Prot.exe processes (and any processes listed in the rarely used DAISYCHAIN option). Note that SMTPD32.exe -- the IMail process/service that starts Declude -- is just a single process, so it will only count once. Message Sniffer and other external tests won't count, since Declude doesn't specifically look for it (but it does indeed count as a service-started process, and could cause the memory limit to be reached). However, there would only be a maximum of one of them per E-mail (since Declude runs the external tests in serial, not in parallel). I also re-read the following post by Sandy: http://www.mail-archive.com/imail_forum@list.ipswitch.com/msg94576.html It seems to indicate that there is no "thread limit", but something else instead; a limit of "64 objects per thread". That's not related here. The overflow issue deals with processes, not threads. Processes are what are listed in the "Process" tab in the Task Manager (such as one SMTPD32.exe process, 0 to 30 or so Declude.exe processes, etc.). Each process can have from 1 to an (almost) infinite number of threads. I'm not sure how that might apply here. So if I am seeing overflow with processing power to spare, I should be able to increase the threads in IMail to a higher number than 60 in order to better utilize my server's capacity. With memory utilization below 50%, it doesn't seem like there is much risk in doing this, would that be correct? Anything referring to "thread" or "threads" in IMail settings is not relevant to this (IMail v8 introduced one or more "thread" options). Declude JunkMail looks at the MaxQueProc IMail registry setting (which may also be an advanced setting in IMail Administrator, with a name such as "maximum number of processes"). Any other settings are not used. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. This outgoing message is guaranteed to be authentic by Message Level users. Guarantee the authenticity of your email @ http://www.messagelevel.com. --- [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. --- [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.
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
You seemed to indicate that service launched processes count against the threads...meaning that smtp32.exe launches declude.exe, which launches F-Prot and McAfee. So would this count for 4 threads (not according to Declude, but Windows/IMail)? What about Sniffer and each external test that I have configured within Declude, would those count as well? Unfortunately, we are not aware of a way to determine if a process was started by a service or not. Currently, Declude looks for declude.exe, smtp32.exe, scan.exe, F-Prot.exe processes (and any processes listed in the rarely used DAISYCHAIN option). Note that SMTPD32.exe -- the IMail process/service that starts Declude -- is just a single process, so it will only count once. Message Sniffer and other external tests won't count, since Declude doesn't specifically look for it (but it does indeed count as a service-started process, and could cause the memory limit to be reached). However, there would only be a maximum of one of them per E-mail (since Declude runs the external tests in serial, not in parallel). I also re-read the following post by Sandy: http://www.mail-archive.com/imail_forum@list.ipswitch.com/msg94576.html It seems to indicate that there is no "thread limit", but something else instead; a limit of "64 objects per thread". That's not related here. The overflow issue deals with processes, not threads. Processes are what are listed in the "Process" tab in the Task Manager (such as one SMTPD32.exe process, 0 to 30 or so Declude.exe processes, etc.). Each process can have from 1 to an (almost) infinite number of threads. I'm not sure how that might apply here. So if I am seeing overflow with processing power to spare, I should be able to increase the threads in IMail to a higher number than 60 in order to better utilize my server's capacity. With memory utilization below 50%, it doesn't seem like there is much risk in doing this, would that be correct? Anything referring to "thread" or "threads" in IMail settings is not relevant to this (IMail v8 introduced one or more "thread" options). Declude JunkMail looks at the MaxQueProc IMail registry setting (which may also be an advanced setting in IMail Administrator, with a name such as "maximum number of processes"). Any other settings are not used. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. This outgoing message is guaranteed to be authentic by Message Level users. Guarantee the authenticity of your email @ http://www.messagelevel.com. --- [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.
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
John, I do recall seeing this stuff, but I came away with the impression that it was only applicable if you were behind a particular type of firewall that had issues with the size of the packets or something to that tune. If this was causing many timeouts, I would have seen a slight increase in spam getting through I would think, but nothing out of the ordinary has occurred that I am aware of. It is possible however that the new capability of the Windows 2003 DNS server is what is causing the extra processor utilization, and I don't think that I benefit from having it on, so I'll try turning it off using the registry hack and then see if it makes any difference. I'm also going to look at what ways if any are available to tune the cache in DNS, thinking that a substantial difference here might also be an issue. Thanks, Matt John Tolmachoff (Lists) wrote: This was covered quite extensively on the Imail list oh probably a year ago. >From my memory (we all know what that means) there are 2 possible issues: 1. If there is more than 1 IP on the server, Imail was sending DNS tests requests (ala Imail Anti-Spam) on one IP and the response was coming back to a different IP in Windows 2003 DNS service. This was a minor problem, and was never known to affect Declude that I can remember. 2. Windows 2003 DNS service added/changed configuration which the end result was the length of the data was greater than it should be and that was causing problems. Again, this is in the Imail archives. If I did not have so much work right now, I would help did them up as I was one of the persons involved in investigating it. Fixes were registry settings. John Tolmachoff Engineer/Consultant/Owner eServices For You -Original Message- From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- [EMAIL PROTECTED]] On Behalf Of Aaron Moreau-Cook Sent: Monday, January 24, 2005 12:02 PM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS I know I'm not aware, care to expand? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of John Tolmachoff (Lists) Sent: Monday, January 24, 2005 11:59 AM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Matt, on the Windows 2003 DNS: You are aware of the time out issues and such aren't you? John Tolmachoff Engineer/Consultant/Owner eServices For You -Original Message- From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- [EMAIL PROTECTED]] On Behalf Of Matt Sent: Monday, January 24, 2005 11:43 AM To: Declude.JunkMail@declude.com Subject: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Scott, Could you please let me know what condition causes E-mail to be left in the overflow directory, and exactly how Declude determines how/when to process such messages. On a side note, I was forced to do a rebuild on a backup server running Windows 2003. The DNS.exe process is a big-time dog compared to that on Windows 2000. I'm seeing DNS.exe reach over 50% of CPU utilization at times, and it never really drops below 10%, and I can't recall ever seeing DNS.exe on Windows 2000 ever go past the low single digits. No Active Directory on either machine, the processor power, memory and mail volume also. The only difference is the RAID card and only three 15K RPM drives in RAID 5 instead of six. Unless there is something unique to my environment, I would stay away from Windows 2003 DNS when used as a caching server with Declude/IMail, or for that matter, any possible high volume use of DNS on that platform. Matt --- [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. --- [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. --- [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. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.J
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Scott, thanks for the explanations. I still have a few follow-ups though if you don't mind. First off, since DNS is acting like such a hog on Windows 2003, I'm going to guess that this is what is slowing down the processing of E-mail and why I am suddenly getting steady overflow. I can resolve that in various ways, but this is a temporary situation since I am going to migrate back to the other box once I rebuild it. DNS will be migrated to a separate server in the coming months...my first foray into Linux. I'm more concerned about the future, and hitting a wall that wasn't necessarily expected, otherwise thinking that I still had plenty of capacity to spare, and hence the additional questions. You seemed to indicate that service launched processes count against the threads...meaning that smtp32.exe launches declude.exe, which launches F-Prot and McAfee. So would this count for 4 threads (not according to Declude, but Windows/IMail)? What about Sniffer and each external test that I have configured within Declude, would those count as well? I also re-read the following post by Sandy: http://www.mail-archive.com/imail_forum@list.ipswitch.com/msg94576.html It seems to indicate that there is no "thread limit", but something else instead; a limit of "64 objects per thread". I'm not sure how that might apply here. So if I am seeing overflow with processing power to spare, I should be able to increase the threads in IMail to a higher number than 60 in order to better utilize my server's capacity. With memory utilization below 50%, it doesn't seem like there is much risk in doing this, would that be correct? I haven't applied any of the registry tweaks, and probably won't on this box since it is only a temporary home. Still good stuff to know about should I ever have to do this again. Thanks, Matt R. Scott Perry wrote: Am I to assume a "first in, first out" type of scenario in the way that it handles the overflow? I believe so, but that is handled by Windows (Declude simply asks Windows for all the files, and whatever Windows returns first gets processed first). I have my server set to 60 delivery threads, up from the default 30. Sandy I believe indicated that 64 was the limit due to the fact that IMail is not multi-threaded or something to that tune. Unfortunately, there is no set limit. Some people have problems with 30, others are fine with 60 or higher. It also depends on any changes made to the registry settings for the "mystery heap" (which gets even weirder; some people see better results by raising the value there, while others see better results by lowering it!). Does having Declude DELETE E-mail go against the thread total? Not with IMail v8 (since IMail v8 uses one process to handle an unlimited number of E-mail deliveries). So using the DELETE action versus another action will have little effect (with IMail v8) on the overflow situation. Also, how should I confirm how many threads are being used by IMail just so that I can rule out the issue with not seeing 60 such files? You would need to count the total number of Declude.exe, SMTP32.exe, and AV processes. Lastly, you indicated multiple things that can go against this number, am I to assume that Declude counts not what IMail is limited by (IMail threads), but instead it just uses this as a guide, so maybe increasing the number in IMail even higher, while it won't have an effect on IMail, it would cause Declude to not overflow, especially when there is processing power to spare? Declude counts (to the best of its ability) the number of service-started processes. That is what IMail (Windows, to be technical) is limited by. Changing the IMail setting will also change the number that Declude uses. Although I'm definitely moving from IMail, I fear hitting a wall before that actually happens. There is definitely more I/O and processor to spare on this box, but the overflow conditions happen every few minutes. Correct. The I/O and processor time aren't relevant here -- they could both be at 0, and the situation could still occur (for example, if 60 E-mails come in simultaneously, and take 30 seconds each to scan due to waiting for DNS packets to come back). -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. This outgoing message is guaranteed to be authentic by Message Level users. Guarantee the authenticity of your email @ http://www.messagelevel.com. --- [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
Re[2]: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Hello Darrell, Monday, January 24, 2005, 5:38:51 PM, you wrote: Dsic> We do the same thing. One thing you can do is fake mail coming in. I use a Dsic> batch file. Dsic> REM THIS WILL CLEAN OUT THE DECLUDE QUEUE Thanks we'll give it a shot. This should be a great help. -- Best regards, Davidmailto:[EMAIL PROTECTED] --- [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.
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
David, We do the same thing. One thing you can do is fake mail coming in. I use a batch file. REM THIS WILL CLEAN OUT THE DECLUDE QUEUE declude x:\imail\spool\Qa6da175e02447716.SMD call x:\imail\cleandq.bat The Q file I referenced does not exist and it does not matter that it does not. Declude will see that there are not 30 processes running and than start to process the mail in the overflow directory. The loop calling the batch file ensures that 30 process stay running. Once the overflow is clean ctrl+c the batch file and move on. Darrell Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, MRTG Integration, and Log Parsers. David Sullivan writes: Declude Queue is nice and was invaluable before the Queue Manager service on Imail. The only problem is this: RSP> than X. At that point, when an E-mail arrives, Declude will start enough RSP> Declude processes to hit the limit of X (each of which scans a single E-mail). DQ requires a continues flow of email in order to clear the /overflow folder. Sending a single message through will not keep the DQ delivery process going. We're still having a number of Imail/PF issues and when a machine gets swamped we switch processing entirely to another box. Then we're stuck with q files in the /overflow folder and no way to get them out. If you copy them into the /spool they don't get scanned by Declude JM or Virus -- Best regards, Davidmailto:[EMAIL PROTECTED] --- [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. --- [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.
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Am I to assume a "first in, first out" type of scenario in the way that it handles the overflow? I believe so, but that is handled by Windows (Declude simply asks Windows for all the files, and whatever Windows returns first gets processed first). I have my server set to 60 delivery threads, up from the default 30. Sandy I believe indicated that 64 was the limit due to the fact that IMail is not multi-threaded or something to that tune. Unfortunately, there is no set limit. Some people have problems with 30, others are fine with 60 or higher. It also depends on any changes made to the registry settings for the "mystery heap" (which gets even weirder; some people see better results by raising the value there, while others see better results by lowering it!). Does having Declude DELETE E-mail go against the thread total? Not with IMail v8 (since IMail v8 uses one process to handle an unlimited number of E-mail deliveries). So using the DELETE action versus another action will have little effect (with IMail v8) on the overflow situation. Also, how should I confirm how many threads are being used by IMail just so that I can rule out the issue with not seeing 60 such files? You would need to count the total number of Declude.exe, SMTP32.exe, and AV processes. Lastly, you indicated multiple things that can go against this number, am I to assume that Declude counts not what IMail is limited by (IMail threads), but instead it just uses this as a guide, so maybe increasing the number in IMail even higher, while it won't have an effect on IMail, it would cause Declude to not overflow, especially when there is processing power to spare? Declude counts (to the best of its ability) the number of service-started processes. That is what IMail (Windows, to be technical) is limited by. Changing the IMail setting will also change the number that Declude uses. Although I'm definitely moving from IMail, I fear hitting a wall before that actually happens. There is definitely more I/O and processor to spare on this box, but the overflow conditions happen every few minutes. Correct. The I/O and processor time aren't relevant here -- they could both be at 0, and the situation could still occur (for example, if 60 E-mails come in simultaneously, and take 30 seconds each to scan due to waiting for DNS packets to come back). -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. This outgoing message is guaranteed to be authentic by Message Level users. Guarantee the authenticity of your email @ http://www.messagelevel.com. --- [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.
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Scott, Am I to assume a "first in, first out" type of scenario in the way that it handles the overflow? I have my server set to 60 delivery threads, up from the default 30. Sandy I believe indicated that 64 was the limit due to the fact that IMail is not multi-threaded or something to that tune. My E-mail backup isn't bad at the moment, just occasional stuff at peak times up to about 100, although the other day when the processors were pegged due to my not having disabled the Indexing Service, I backed it up for about 45 minutes worth. I'm probably averaging about 60% utilization (hourly average) right now. Right now we are deleting about 75% of all E-mail (using the DELETE action). I'm pretty sure that if we are reaching 60 threads, we are only doing so with the totality of messages and not just what we might deliver or ROUTETO/COPYTO. Counting the files in my spool, I am coming up measurably short of 60 Q*.SMD files while I see messages in the overflow (which happens every few minutes). It seems that this would represent the number of threads that are open, apart from what Declude has in overflow. Does having Declude DELETE E-mail go against the thread total? Also, how should I confirm how many threads are being used by IMail just so that I can rule out the issue with not seeing 60 such files? Lastly, you indicated multiple things that can go against this number, am I to assume that Declude counts not what IMail is limited by (IMail threads), but instead it just uses this as a guide, so maybe increasing the number in IMail even higher, while it won't have an effect on IMail, it would cause Declude to not overflow, especially when there is processing power to spare? Although I'm definitely moving from IMail, I fear hitting a wall before that actually happens. There is definitely more I/O and processor to spare on this box, but the overflow conditions happen every few minutes. Thanks, Matt R. Scott Perry wrote: Could you please let me know what condition causes E-mail to be left in the overflow directory, and exactly how Declude determines how/when to process such messages. The short version is that the situation is handled better than if the overflow directory isn't used (many people don't get that). The longer version is that Declude will move E-mail (actually, just the Q*.SMD file) to the overflow directory when Declude detects that there are more than X service-started processes (where X is 30, unless you have IMail set to use a different number of maximum processes). Those can be declude.exe, smtp32.exe, or AV processes. Once this situation occurs, Declude will continue to move E-mails to the overflow directory until the number of service-started processes is less than X. At that point, when an E-mail arrives, Declude will start enough Declude processes to hit the limit of X (each of which scans a single E-mail). -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. This outgoing message is guaranteed to be authentic by Message Level users. Guarantee the authenticity of your email @ http://www.messagelevel.com. --- [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. --- [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.
Re[2]: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Declude Queue is nice and was invaluable before the Queue Manager service on Imail. The only problem is this: RSP> than X. At that point, when an E-mail arrives, Declude will start enough RSP> Declude processes to hit the limit of X (each of which scans a single E-mail). DQ requires a continues flow of email in order to clear the /overflow folder. Sending a single message through will not keep the DQ delivery process going. We're still having a number of Imail/PF issues and when a machine gets swamped we switch processing entirely to another box. Then we're stuck with q files in the /overflow folder and no way to get them out. If you copy them into the /spool they don't get scanned by Declude JM or Virus -- Best regards, Davidmailto:[EMAIL PROTECTED] --- [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.
RE: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
This was covered quite extensively on the Imail list oh probably a year ago. >From my memory (we all know what that means) there are 2 possible issues: 1. If there is more than 1 IP on the server, Imail was sending DNS tests requests (ala Imail Anti-Spam) on one IP and the response was coming back to a different IP in Windows 2003 DNS service. This was a minor problem, and was never known to affect Declude that I can remember. 2. Windows 2003 DNS service added/changed configuration which the end result was the length of the data was greater than it should be and that was causing problems. Again, this is in the Imail archives. If I did not have so much work right now, I would help did them up as I was one of the persons involved in investigating it. Fixes were registry settings. John Tolmachoff Engineer/Consultant/Owner eServices For You > -Original Message- > From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- > [EMAIL PROTECTED] On Behalf Of Aaron Moreau-Cook > Sent: Monday, January 24, 2005 12:02 PM > To: Declude.JunkMail@declude.com > Subject: RE: [Declude.JunkMail] Overflow directory and a note about Windows 2003 > DNS > > I know I'm not aware, care to expand? > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John Tolmachoff > (Lists) > Sent: Monday, January 24, 2005 11:59 AM > To: Declude.JunkMail@declude.com > Subject: RE: [Declude.JunkMail] Overflow directory and a note about Windows > 2003 DNS > > Matt, on the Windows 2003 DNS: You are aware of the time out issues and such > aren't you? > > John Tolmachoff > Engineer/Consultant/Owner > eServices For You > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- > > [EMAIL PROTECTED] On Behalf Of Matt > > Sent: Monday, January 24, 2005 11:43 AM > > To: Declude.JunkMail@declude.com > > Subject: [Declude.JunkMail] Overflow directory and a note about > > Windows > 2003 DNS > > > > Scott, > > > > Could you please let me know what condition causes E-mail to be left > > in the overflow directory, and exactly how Declude determines how/when > > to process such messages. > > > > On a side note, I was forced to do a rebuild on a backup server > > running Windows 2003. The DNS.exe process is a big-time dog compared > > to that on Windows 2000. I'm seeing DNS.exe reach over 50% of CPU > > utilization at times, and it never really drops below 10%, and I can't > > recall ever seeing DNS.exe on Windows 2000 ever go past the low single > > digits. No Active Directory on either machine, the processor power, > > memory and mail volume also. The only difference is the RAID card and > > only three 15K RPM drives in RAID 5 instead of six. Unless there is > > something unique to my environment, I would stay away from Windows > > 2003 DNS when used as a caching server with Declude/IMail, or for that > > matter, any possible high volume use of DNS on that platform. > > > > Matt > > > > --- > > [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. > > --- > [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. > > --- > [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. --- [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.
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Matt- I've been using W2003 on one of my DNS servers for several months now, and I have not experienced what you descibe. Have you checked the DNS event log? It's separate now from the App, Security, and System event logs. Maybe there's a clue there. -Dave Doherty Skywaves, inc. - Original Message - From: Matt To: Declude.JunkMail@declude.com Sent: Monday, January 24, 2005 3:09 PM Subject: Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS My understanding is that this is an issue with just some firewalls and not universal. Please correct me if I am wrong.Thanks,MattJohn Tolmachoff (Lists) wrote: Matt, on the Windows 2003 DNS: You are aware of the time out issues and such aren't you? John Tolmachoff Engineer/Consultant/Owner eServices For You -Original Message- From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- [EMAIL PROTECTED]] On Behalf Of Matt Sent: Monday, January 24, 2005 11:43 AM To: Declude.JunkMail@declude.com Subject: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Scott, Could you please let me know what condition causes E-mail to be left in the overflow directory, and exactly how Declude determines how/when to process such messages. On a side note, I was forced to do a rebuild on a backup server running Windows 2003. The DNS.exe process is a big-time dog compared to that on Windows 2000. I'm seeing DNS.exe reach over 50% of CPU utilization at times, and it never really drops below 10%, and I can't recall ever seeing DNS.exe on Windows 2000 ever go past the low single digits. No Active Directory on either machine, the processor power, memory and mail volume also. The only difference is the RAID card and only three 15K RPM drives in RAID 5 instead of six. Unless there is something unique to my environment, I would stay away from Windows 2003 DNS when used as a caching server with Declude/IMail, or for that matter, any possible high volume use of DNS on that platform. Matt --- [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. --- [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.
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
My understanding is that this is an issue with just some firewalls and not universal. Please correct me if I am wrong. Thanks, Matt John Tolmachoff (Lists) wrote: Matt, on the Windows 2003 DNS: You are aware of the time out issues and such aren't you? John Tolmachoff Engineer/Consultant/Owner eServices For You -Original Message- From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- [EMAIL PROTECTED]] On Behalf Of Matt Sent: Monday, January 24, 2005 11:43 AM To: Declude.JunkMail@declude.com Subject: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Scott, Could you please let me know what condition causes E-mail to be left in the overflow directory, and exactly how Declude determines how/when to process such messages. On a side note, I was forced to do a rebuild on a backup server running Windows 2003. The DNS.exe process is a big-time dog compared to that on Windows 2000. I'm seeing DNS.exe reach over 50% of CPU utilization at times, and it never really drops below 10%, and I can't recall ever seeing DNS.exe on Windows 2000 ever go past the low single digits. No Active Directory on either machine, the processor power, memory and mail volume also. The only difference is the RAID card and only three 15K RPM drives in RAID 5 instead of six. Unless there is something unique to my environment, I would stay away from Windows 2003 DNS when used as a caching server with Declude/IMail, or for that matter, any possible high volume use of DNS on that platform. Matt --- [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. --- [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.
Re: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Could you please let me know what condition causes E-mail to be left in the overflow directory, and exactly how Declude determines how/when to process such messages. The short version is that the situation is handled better than if the overflow directory isn't used (many people don't get that). The longer version is that Declude will move E-mail (actually, just the Q*.SMD file) to the overflow directory when Declude detects that there are more than X service-started processes (where X is 30, unless you have IMail set to use a different number of maximum processes). Those can be declude.exe, smtp32.exe, or AV processes. Once this situation occurs, Declude will continue to move E-mails to the overflow directory until the number of service-started processes is less than X. At that point, when an E-mail arrives, Declude will start enough Declude processes to hit the limit of X (each of which scans a single E-mail). -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. This outgoing message is guaranteed to be authentic by Message Level users. Guarantee the authenticity of your email @ http://www.messagelevel.com. --- [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.
RE: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
I know I'm not aware, care to expand? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Tolmachoff (Lists) Sent: Monday, January 24, 2005 11:59 AM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS Matt, on the Windows 2003 DNS: You are aware of the time out issues and such aren't you? John Tolmachoff Engineer/Consultant/Owner eServices For You > -Original Message- > From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- > [EMAIL PROTECTED] On Behalf Of Matt > Sent: Monday, January 24, 2005 11:43 AM > To: Declude.JunkMail@declude.com > Subject: [Declude.JunkMail] Overflow directory and a note about > Windows 2003 DNS > > Scott, > > Could you please let me know what condition causes E-mail to be left > in the overflow directory, and exactly how Declude determines how/when > to process such messages. > > On a side note, I was forced to do a rebuild on a backup server > running Windows 2003. The DNS.exe process is a big-time dog compared > to that on Windows 2000. I'm seeing DNS.exe reach over 50% of CPU > utilization at times, and it never really drops below 10%, and I can't > recall ever seeing DNS.exe on Windows 2000 ever go past the low single > digits. No Active Directory on either machine, the processor power, > memory and mail volume also. The only difference is the RAID card and > only three 15K RPM drives in RAID 5 instead of six. Unless there is > something unique to my environment, I would stay away from Windows > 2003 DNS when used as a caching server with Declude/IMail, or for that > matter, any possible high volume use of DNS on that platform. > > Matt > > --- > [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. --- [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. --- [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.
RE: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Matt, on the Windows 2003 DNS: You are aware of the time out issues and such aren't you? John Tolmachoff Engineer/Consultant/Owner eServices For You > -Original Message- > From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- > [EMAIL PROTECTED] On Behalf Of Matt > Sent: Monday, January 24, 2005 11:43 AM > To: Declude.JunkMail@declude.com > Subject: [Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS > > Scott, > > Could you please let me know what condition causes E-mail to be left in > the overflow directory, and exactly how Declude determines how/when to > process such messages. > > On a side note, I was forced to do a rebuild on a backup server running > Windows 2003. The DNS.exe process is a big-time dog compared to that on > Windows 2000. I'm seeing DNS.exe reach over 50% of CPU utilization at > times, and it never really drops below 10%, and I can't recall ever > seeing DNS.exe on Windows 2000 ever go past the low single digits. No > Active Directory on either machine, the processor power, memory and mail > volume also. The only difference is the RAID card and only three 15K > RPM drives in RAID 5 instead of six. Unless there is something unique > to my environment, I would stay away from Windows 2003 DNS when used as > a caching server with Declude/IMail, or for that matter, any possible > high volume use of DNS on that platform. > > Matt > > --- > [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. --- [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.
[Declude.JunkMail] Overflow directory and a note about Windows 2003 DNS
Scott, Could you please let me know what condition causes E-mail to be left in the overflow directory, and exactly how Declude determines how/when to process such messages. On a side note, I was forced to do a rebuild on a backup server running Windows 2003. The DNS.exe process is a big-time dog compared to that on Windows 2000. I'm seeing DNS.exe reach over 50% of CPU utilization at times, and it never really drops below 10%, and I can't recall ever seeing DNS.exe on Windows 2000 ever go past the low single digits. No Active Directory on either machine, the processor power, memory and mail volume also. The only difference is the RAID card and only three 15K RPM drives in RAID 5 instead of six. Unless there is something unique to my environment, I would stay away from Windows 2003 DNS when used as a caching server with Declude/IMail, or for that matter, any possible high volume use of DNS on that platform. Matt --- [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.