RE: [Declude.JunkMail] Declude Crashing
I disabled autoreview and was then able to capture the emails that appear to be crashing Declude. They all seem to have one thing in common. The .hdr file has an unusual space as follows: Written [EMAIL PROTECTED] cmdspc: true helo: 17-94-189-190.cab.prima.net.ar The space between written and the email address doesn't seem to typically appear in SmarterMail's .hdr files however the emails that are crashing Declude appear to consistently have it. I do have a ticket open with Declude so hopefully they can help me out. Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darrell ([EMAIL PROTECTED]) Sent: Saturday, August 02, 2008 5:17 PM To: declude.junkmail@declude.com Subject: Re: [Declude.JunkMail] Declude Crashing Do you have autoreview enabled? If so when Declude crashes on restart it will copy the files (work dir) back into the proc for processing. These types of crashes are most likely assuming no changes to your system a result of a bad message. If you disable autoreview and the crashes stop you can slowly copy the messages from the review folder into the proc to find which is the message that crashes Declude. Darrell Mark Strother wrote: For the past few hours we've had a real problem with Declude crashing and I can't figure it out. We're using SmarterMail 4.1 and Declude 4.1.14A. I've disabled all external plugins and filters and disabled the viruschecking so it's not related to that. I've cleared out all the queued messages, restarted everything and it crashes again within minutes. I've done that several times. Once I managed to get Declude running for about 10 minutes but then it crashed again. I'm not sure what else to do. For now I've had to disable Declude. I've turned up all logging to the highest level and don't see anything of note except 'Error in envelope file'. Can anyone provide some help or point in the right direction? We've been running Declude for 2 or so years and we do see the occasional crash but typically Windows restarts the service and everything is fine. In the case it just crashes over and over. Mark --- 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. -- -- 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. --- 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] Declude Crashing
For the past few hours we've had a real problem with Declude crashing and I can't figure it out. We're using SmarterMail 4.1 and Declude 4.1.14A. I've disabled all external plugins and filters and disabled the viruschecking so it's not related to that. I've cleared out all the queued messages, restarted everything and it crashes again within minutes. I've done that several times. Once I managed to get Declude running for about 10 minutes but then it crashed again. I'm not sure what else to do. For now I've had to disable Declude. I've turned up all logging to the highest level and don't see anything of note except 'Error in envelope file'. Can anyone provide some help or point in the right direction? We've been running Declude for 2 or so years and we do see the occasional crash but typically Windows restarts the service and everything is fine. In the case it just crashes over and over. Mark --- 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] Declude Crashing
Mark, Sounds like a 'killer message'. It would help to post the contents of the HDR file associated with that log line as Declude may be dying on parsing a value in that HDR file. I've noted more common crashes of DecludeProc recently myself, but we are behind an Alligate gateway so much of the badly formated E-mail dies there. That certainly adds to the stability of Declude and also the mail server in some cases. Anything that looks at E-mail must have the ability to survive something unexpected. Matt Mark Strother wrote: For the past few hours we've had a real problem with Declude crashing and I can't figure it out. We're using SmarterMail 4.1 and Declude 4.1.14A. I've disabled all external plugins and filters and disabled the viruschecking so it's not related to that. I've cleared out all the queued messages, restarted everything and it crashes again within minutes. I've done that several times. Once I managed to get Declude running for about 10 minutes but then it crashed again. I'm not sure what else to do. For now I've had to disable Declude. I've turned up all logging to the highest level and don't see anything of note except 'Error in envelope file'. Can anyone provide some help or point in the right direction? We've been running Declude for 2 or so years and we do see the occasional crash but typically Windows restarts the service and everything is fine. In the case it just crashes over and over. Mark --- 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] Declude Crashing
Do you have autoreview enabled? If so when Declude crashes on restart it will copy the files (work dir) back into the proc for processing. These types of crashes are most likely assuming no changes to your system a result of a bad message. If you disable autoreview and the crashes stop you can slowly copy the messages from the review folder into the proc to find which is the message that crashes Declude. Darrell Mark Strother wrote: For the past few hours we’ve had a real problem with Declude crashing and I can’t figure it out. We’re using SmarterMail 4.1 and Declude 4.1.14A. I’ve disabled all external plugins and filters and disabled the viruschecking so it’s not related to that. I’ve cleared out all the queued messages, restarted everything and it crashes again within minutes. I’ve done that several times. Once I managed to get Declude running for about 10 minutes but then it crashed again. I’m not sure what else to do. For now I’ve had to disable Declude. I’ve turned up all logging to the highest level and don’t see anything of note except ‘Error in envelope file’. Can anyone provide some help or point in the right direction? We’ve been running Declude for 2 or so years and we do see the occasional crash but typically Windows restarts the service and everything is fine. In the case it just crashes over and over. Mark --- 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. -- -- 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. --- 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] Declude Crashing
Thanks Darrell. That's good advice. I did have autoreview enabled. I've disabled it so hopefully I can catch a few of the bad messages shortly. I'll keep the list posted. Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darrell ([EMAIL PROTECTED]) Sent: Saturday, August 02, 2008 5:17 PM To: declude.junkmail@declude.com Subject: Re: [Declude.JunkMail] Declude Crashing Do you have autoreview enabled? If so when Declude crashes on restart it will copy the files (work dir) back into the proc for processing. These types of crashes are most likely assuming no changes to your system a result of a bad message. If you disable autoreview and the crashes stop you can slowly copy the messages from the review folder into the proc to find which is the message that crashes Declude. Darrell Mark Strother wrote: For the past few hours we've had a real problem with Declude crashing and I can't figure it out. We're using SmarterMail 4.1 and Declude 4.1.14A. I've disabled all external plugins and filters and disabled the viruschecking so it's not related to that. I've cleared out all the queued messages, restarted everything and it crashes again within minutes. I've done that several times. Once I managed to get Declude running for about 10 minutes but then it crashed again. I'm not sure what else to do. For now I've had to disable Declude. I've turned up all logging to the highest level and don't see anything of note except 'Error in envelope file'. Can anyone provide some help or point in the right direction? We've been running Declude for 2 or so years and we do see the occasional crash but typically Windows restarts the service and everything is fine. In the case it just crashes over and over. Mark --- 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. -- -- 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. --- 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] Declude crashing and taking up 99% CPU
I have tried my best to help with this issue, research, testing, etc. During a normal business day, declude is awesome - working very nicely as advertised and very reliable. Perhaps, on an email server with less traffic, some declude customers wouldn't even know of any reliability issues. I think I have narrowed down the issue with our declude operation. During a normal time period, we do pass a ton of emails, but during the moments when the flood gates open and spam flows in, this causes many declude.exe's to run. Some use 99% of the CPU, while others simply use up memory. In my opinion, an opinion from a non-programmer, I would think that there should only be one declude.exe running (as a service perhaps). In the event that declude can't handle a High Surge of Spam, then declude should pass the junk mail on to imail for normal processing. With Imail limiting smtp32.exe to just 30 instances (configurable by the registry), this would not cause a problem with the desktop heap. You could even trim down the smtp32.exe count to 10. Then, when the flood gates open, the mail will just be a little slow, but reliable. I think this would make a more reliable server. Again, I am only TRYING to help and give ideas. My intent is not to step on anyones toes. I will keep looking at the list to see when they have this problem fixed, but we can't continue to provide poor uptime on our mail server. I do want to add one final note, my hats off to Scott for a great product design and truely remarkable tech support. I honestly don't know when he sleeps. Outstanding work ethics Scott!!! Travis Sullivan --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
I have tried my best to help with this issue, research, testing, etc. During a normal business day, declude is awesome - working very nicely as advertised and very reliable. Perhaps, on an email server with less traffic, some declude customers wouldn't even know of any reliability issues. From the information we have gathered so far, the 99% CPU issue only affects Declude JunkMail on v1.24 and higher, on highish volume systems (our mail server processes about 3,000 E-mails on an average day, and we haven't seen the problem even once here). During a normal time period, we do pass a ton of emails, but during the moments when the flood gates open and spam flows in, this causes many declude.exe's to run. Some use 99% of the CPU, while others simply use up memory. In my opinion, an opinion from a non-programmer, I would think that there should only be one declude.exe running (as a service perhaps). That's actually an IMail limitation. Most programs do work that way -- there is one process that handles all requests. However, IMail is set up to start a new process for each E-mail that needs to be delivered. It seems pretty inefficient (actually, a terrible design now that the Microsoft heap issue has been identified), but they chose it for a reason. Declude is stuck with that architecture -- IMail will start one declude.exe process for each E-mail, no matter what. Note that without Declude running, IMail will start one smtp32.exe process for each E-mail. Note that the 99% CPU issue was not reported before v1.24. In the event that declude can't handle a High Surge of Spam, then declude should pass the junk mail on to imail for normal processing. I haven't yet seen Declude not be able to handle high volumes of spam. It's survived spam attacks, where a spammer will try to send through 100,000's of E-mails. With Imail limiting smtp32.exe to just 30 instances (configurable by the registry), this would not cause a problem with the desktop heap. You could even trim down the smtp32.exe count to 10. Then, when the flood gates open, the mail will just be a little slow, but reliable. This is a separate issue, and again an IMail issue. This is the problem that causes the DLL initialization failure crashes with IMail, and causes mail delivery to be sooo slow when there is overflow (E-mail arriving when all processes are being used). We are working on a way to minimize this problem, where Declude will take over the limiting of the number of processes running at once, and will create a separate queue for E-mail that hasn't been attempted yet (normally, IMail just puts the mail in the spool, which should just contain E-mail that couldn't be delivered on the first attempt). Then, as soon as there are free processes available, Declude will start things back up again with multiple processes (rather than waiting 1/2 hour or so for the next queue run, which only starts up 1 process). That should help reduce the DLL initialization problem, as well as the IMail slow mail delivery of overflow. It's not going to be perfect, since IMail can start several new processes on the same timeslice, which means that all of those processes will start before they have a chance to stop themselves. So, for example, if Windows will let you run 35 server-started processes before running out of their mystery heap, and IMail can start up to 10 processes on one timeslice, Declude would have to start the overflow procedure after 25 processes. If it let the 26th in, then IMail could create 10 more before Declude next had a chance to see how many processes were in memory, which would pass the 35 process limit, and crash the server. I think this would make a more reliable server. Again, I am only TRYING to help and give ideas. My intent is not to step on anyones toes. That's not a problem, ideas are what makes improvements possible. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
RE: [Declude.JunkMail] Declude crashing and taking up 99% CPU
There is a tweak for this in declude. You can set the maximum number of decludes that will run at one time. This helps set limits in cases like this. _M | -Original Message- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED]]On Behalf Of Travis Sullivan | Sent: Tuesday, September 25, 2001 10:25 AM | To: [EMAIL PROTECTED] | Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU | | | I have tried my best to help with this issue, research, testing, etc. | During a normal business day, declude is awesome - working very nicely as | advertised and very reliable. Perhaps, on an email server with less | traffic, some declude customers wouldn't even know of any reliability | issues. I think I have narrowed down the issue with our declude | operation. | | During a normal time period, we do pass a ton of emails, but during the | moments when the flood gates open and spam flows in, this causes many | declude.exe's to run. Some use 99% of the CPU, while others simply use up | memory. In my opinion, an opinion from a non-programmer, I would | think that | there should only be one declude.exe running (as a service | perhaps). In the | event that declude can't handle a High Surge of Spam, then | declude should | pass the junk mail on to imail for normal processing. | | With Imail limiting smtp32.exe to just 30 instances (configurable by the | registry), this would not cause a problem with the desktop heap. | You could | even trim down the smtp32.exe count to 10. Then, when the flood | gates open, | the mail will just be a little slow, but reliable. | | I think this would make a more reliable server. Again, I am only | TRYING to | help and give ideas. My intent is not to step on anyones toes. | I will keep | looking at the list to see when they have this problem fixed, but we can't | continue to provide poor uptime on our mail server. | | I do want to add one final note, my hats off to Scott for a great product | design and truely remarkable tech support. I honestly don't know when he | sleeps. Outstanding work ethics Scott!!! | | Travis Sullivan | | | --- | | 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. You can E-mail | [EMAIL PROTECTED] for assistance. You can visit our web | site at 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
RE: [Declude.JunkMail] Declude crashing and taking up 99% CPU
There is a tweak for this in declude. You can set the maximum number of decludes that will run at one time. This helps set limits in cases like this. Actually, the MAXATONCE option only affects the number of virus scanner processes that are started. It does not affect the number of declude.exe's that are started. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
RE: [Declude.JunkMail] Declude crashing and taking up 99% CPU
Hey Scott, Just throwing an idea out there, since most spam mail hits multiple addresses in the same server, often as seperate messages, how about a failed message cache that could automatically fail a message if it failed in the last hour or some other configurable time span? It would probably have to rely on a weghted combo match of several headers since they sometimes use different senders or servers, and I've even seen them add the recipients name or email in the subject and/or the body. This would help in that you are not completely reprocessing the same spam message hundreds possibly thousands of times on high volume servers. The only drawback I can think of might be the extra resources to manage the cache if it got huge. Another thought, it could also be useful for the AV side. Chuck Frolick ArgoNet, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry Sent: Tuesday, September 25, 2001 9:45 AM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU I have tried my best to help with this issue, research, testing, etc. During a normal business day, declude is awesome - working very nicely as advertised and very reliable. Perhaps, on an email server with less traffic, some declude customers wouldn't even know of any reliability issues. From the information we have gathered so far, the 99% CPU issue only affects Declude JunkMail on v1.24 and higher, on highish volume systems (our mail server processes about 3,000 E-mails on an average day, and we haven't seen the problem even once here). During a normal time period, we do pass a ton of emails, but during the moments when the flood gates open and spam flows in, this causes many declude.exe's to run. Some use 99% of the CPU, while others simply use up memory. In my opinion, an opinion from a non-programmer, I would think that there should only be one declude.exe running (as a service perhaps). That's actually an IMail limitation. Most programs do work that way -- there is one process that handles all requests. However, IMail is set up to start a new process for each E-mail that needs to be delivered. It seems pretty inefficient (actually, a terrible design now that the Microsoft heap issue has been identified), but they chose it for a reason. Declude is stuck with that architecture -- IMail will start one declude.exe process for each E-mail, no matter what. Note that without Declude running, IMail will start one smtp32.exe process for each E-mail. Note that the 99% CPU issue was not reported before v1.24. In the event that declude can't handle a High Surge of Spam, then declude should pass the junk mail on to imail for normal processing. I haven't yet seen Declude not be able to handle high volumes of spam. It's survived spam attacks, where a spammer will try to send through 100,000's of E-mails. With Imail limiting smtp32.exe to just 30 instances (configurable by the registry), this would not cause a problem with the desktop heap. You could even trim down the smtp32.exe count to 10. Then, when the flood gates open, the mail will just be a little slow, but reliable. This is a separate issue, and again an IMail issue. This is the problem that causes the DLL initialization failure crashes with IMail, and causes mail delivery to be sooo slow when there is overflow (E-mail arriving when all processes are being used). We are working on a way to minimize this problem, where Declude will take over the limiting of the number of processes running at once, and will create a separate queue for E-mail that hasn't been attempted yet (normally, IMail just puts the mail in the spool, which should just contain E-mail that couldn't be delivered on the first attempt). Then, as soon as there are free processes available, Declude will start things back up again with multiple processes (rather than waiting 1/2 hour or so for the next queue run, which only starts up 1 process). That should help reduce the DLL initialization problem, as well as the IMail slow mail delivery of overflow. It's not going to be perfect, since IMail can start several new processes on the same timeslice, which means that all of those processes will start before they have a chance to stop themselves. So, for example, if Windows will let you run 35 server-started processes before running out of their mystery heap, and IMail can start up to 10 processes on one timeslice, Declude would have to start the overflow procedure after 25 processes. If it let the 26th in, then IMail could create 10 more before Declude next had a chance to see how many processes were in memory, which would pass the 35 process limit, and crash the server. I think this would make a more reliable server. Again, I am only TRYING to help and give ideas. My intent is not to step on anyones toes. That's not a problem, ideas are what makes improvements possible
RE: [Declude.JunkMail] Declude crashing and taking up 99% CPU
I stand corrected, but the purpose is the same. Thanks, _M | -Original Message- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry | Sent: Tuesday, September 25, 2001 11:16 AM | To: [EMAIL PROTECTED] | Subject: RE: [Declude.JunkMail] Declude crashing and taking up 99% CPU | | | | There is a tweak for this in declude. You can set the maximum number of | decludes that will run at one time. This helps set limits in cases like | this. | | Actually, the MAXATONCE option only affects the number of virus scanner | processes that are started. It does not affect the number of | declude.exe's | that are started. | -Scott | | --- | | 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. You can E-mail | [EMAIL PROTECTED] for assistance. You can visit our web | site at 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
We now have a new interim declude.exe online, at http://www.declude.com/release/126/declude.exe . This one is based on 1.25a, except that the DNS engine has been modified to make sure that infinite loops are not possible. Right now, the most likely reason for the 99% CPU usage seems to be during DNS queries, since the DNS engine changed quite a bit between 1.20 and 1.25a. If the 99% CPU usage is indeed caused by a problem with the DNS engine, this will take care of it. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
should we use this even if we don't have the 99% cpu problem? - Original Message - From: R. Scott Perry [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, September 25, 2001 6:44 PM Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU We now have a new interim declude.exe online, at http://www.declude.com/release/126/declude.exe . This one is based on 1.25a, except that the DNS engine has been modified to make sure that infinite loops are not possible. Right now, the most likely reason for the 99% CPU usage seems to be during DNS queries, since the DNS engine changed quite a bit between 1.20 and 1.25a. If the 99% CPU usage is indeed caused by a problem with the DNS engine, this will take care of it. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
should we use this even if we don't have the 99% cpu problem? No, you should not. The interim release should only be used by people who are experiencing that problem. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
What are the major differences between 1.23 and 1.24+ If 1.23 fixes our problem, then I want to downgrade. Travis --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
I downgraded from v1.25a to v1.24. This morning, 20 minutes ago, Declude was at 99% utilization. - Original Message - As I've stated several times: I'm not getting an error message, no files are being created and no event log messages. (I'll double check my gigantic log files to be sure of the first..) It appears that there are 3 separate issues (you're seeing #1): [1] 100% CPU usage, that appears to have started between v1.20 and 1.25a. This has been narrowed down to several possible areas of code where this is happening. No C:\Declude.gp? file is created. --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
FYI- We now have an interim release available online at http://www.declude.com/release/126/declude.exe that adds a new configuration option PIDDEBUG ON, that should signifcantly help in tracking down the 99% CPU problem. When that line is added to the global.cfg file, Declude will save a file in the spool directory with the PID (Process ID) of the Declude process, and will save full debugging information to that file. As soon as the Declude process ends, the file will be deleted. Then, if there is a process using up all the CPU time (or even if it isn't using up CPU time, but is not ending), it will be easy to send us the information we can use to track down the problem. If you open Task Manager, and look at the processes, there will be a column named PID. If you see declude.exe375 ..., the PID is 375. You would then look for \IMail\spool\375.pid. That file will contain the debug information. Note that this will record the same information as LOGLEVEL DEBUG, but prevent your regular log file from getting cluttered with all the debug information. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
Scott, I don't remember having any problems with 1.24. - Original Message - From: R. Scott Perry [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 17, 2001 5:13 PM Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU As I've stated several times: I'm not getting an error message, no files are being created and no event log messages. (I'll double check my gigantic log files to be sure of the first..) It appears that there are 3 separate issues (you're seeing #1): [1] 100% CPU usage, that appears to have started between v1.20 and 1.25a. This has been narrowed down to several possible areas of code where this is happening. No C:\Declude.gp? file is created. [2] A crash, where a C:\Declude.gp? file is created. This is happening somewhere within the spam testing section of the code, but it is hard to pinpoint exactly where this is happening. and [3] The known C142 issue with user32.dll initializing, because of the low system heap or whatever Microsoft is calling it. This one can happen with just about any version of IMail, with or without Declude, because of IMail's architecture. There is no way to fix this, but we are trying to find a way to make this less noticeable when Declude is used with IMail, however. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
Actually, I take that back. There might be a problem with 1.24 but not with 1.23. - Original Message - From: Frank [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, September 18, 2001 9:48 AM Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU Scott, I don't remember having any problems with 1.24. - Original Message - From: R. Scott Perry [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 17, 2001 5:13 PM Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU As I've stated several times: I'm not getting an error message, no files are being created and no event log messages. (I'll double check my gigantic log files to be sure of the first..) It appears that there are 3 separate issues (you're seeing #1): [1] 100% CPU usage, that appears to have started between v1.20 and 1.25a. This has been narrowed down to several possible areas of code where this is happening. No C:\Declude.gp? file is created. [2] A crash, where a C:\Declude.gp? file is created. This is happening somewhere within the spam testing section of the code, but it is hard to pinpoint exactly where this is happening. and [3] The known C142 issue with user32.dll initializing, because of the low system heap or whatever Microsoft is calling it. This one can happen with just about any version of IMail, with or without Declude, because of IMail's architecture. There is no way to fix this, but we are trying to find a way to make this less noticeable when Declude is used with IMail, however. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
RE: [Declude.JunkMail] Declude crashing and taking up 99% CPU
My problems also began after upgrading to 1.25a, before the upgrade Declude never crashed. Now I need 2 reboots a day to keep my mail working. Do you recall which version you were running before that? If I can find out which version introduced this problem, it will be easier to find out what caused it. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
As I've stated several times: I'm not getting an error message, no files are being created and no event log messages. (I'll double check my gigantic log files to be sure of the first..) Our prior version was v1.20 - Original Message - From: R. Scott Perry [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, September 15, 2001 9:53 PM Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU Where can we find v1.24 or below of Declude? You can download the previous public release at http://www.declude.com/release/120/declude.exe . --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
As I've stated several times: I'm not getting an error message, no files are being created and no event log messages. (I'll double check my gigantic log files to be sure of the first..) It appears that there are 3 separate issues (you're seeing #1): [1] 100% CPU usage, that appears to have started between v1.20 and 1.25a. This has been narrowed down to several possible areas of code where this is happening. No C:\Declude.gp? file is created. [2] A crash, where a C:\Declude.gp? file is created. This is happening somewhere within the spam testing section of the code, but it is hard to pinpoint exactly where this is happening. and [3] The known C142 issue with user32.dll initializing, because of the low system heap or whatever Microsoft is calling it. This one can happen with just about any version of IMail, with or without Declude, because of IMail's architecture. There is no way to fix this, but we are trying to find a way to make this less noticeable when Declude is used with IMail, however. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
We are also have a problem with Declude recently. It doesn't crash our system per say but it causes our system to go to 100% CPU utilization, memory usage goes way up and SMTP timesout (even though there are a lot of STMP Declude processes showing up). We have had to reboot our mail server once a day because of this. - Original Message - From: R. Scott Perry [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 12, 2001 10:24 PM Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU other similar information? What *exactly* does the error message say, the complete text of it? I can't recall ever seeing NT/2000 report a crash without at least the memory address that the crash occurred at. user32.dll is the main text of the message. There is just the pop up window reporting that user32.dll has failed. What you describe cannot be distinguished with the Microsoft Too-many-service-started-processes problem. Unless I get the exact text of the message, I'll have to assume that that is the problem. The links are http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q142676 and http://support.microsoft.com/directory/article.asp?ID=kb;en-us;Q126962 . There are several sources of this problem. One is that Microsoft has an apparently undocumented type of memory that it allocates to (again, apparently) all processes. It apparently allocates a certain amount of memory to each process, which can differ based on whether the process was started normally or through a service. Microsoft says it allocates this memory to force ill-behaved programs from consuming too much resources -- but doesn't explain why it allocates all those precious resources even if they are not needed. It sounds like they are used for GUI stuff (icons, palettes, mouse pointers, etc.) that aren't used in most services anyways. So this problem can exist with any programs. The reason it is so apparent in IMail (with or without Declude) is that IMail [1] runs as a service and [2] creates a new process (rather than thread) for each E-mail that needs to be delivered. The problem gets even worse with Declude creating extra processes for the virus scanning. We are trying to find a way to prevent this problem, which may or may not be possible to do (it may only be possible to offload it, so that it can only happen once the smtp32.exe process is started, for example). However, this is a difficult process since Microsoft is referring to undocumented memory (their 1gig MSDN knowledge base references to desktop heap, the term they use for this type of memory, only brings up articles about this problem, no documentation of the memory type). -Scott --- Declude: Anti-virus, Anti-spam and Anti-hijacking solutions for IMail. 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
If anyone has any further advise, I am eagerly, but patiently, waiting. It seems like there aren't many (although there are some) programs that encounter this problem. The real solution would be for Ipswitch not to start a new process for each E-mail delivery. But, the earliest that could happen in 8.x, which is probably quite a ways off. In the meantime, we are going to be working on a solution. However, it may be a while, as we are shorthanded right now. We have started working on ways to limit processes, but unfortunately it doesn't look like we will be able to do it properly (limit them when desktop heap is low, since there appears to be no way to find out how much desktop heap is being used). Again, maybe a newer version of Imail is better??? We use 5.09. Also, is this problem apparent in windows 2000? I've seen this happen on 6.x, and heard of it happening on 7.x. I've only seen it happen on Windows 2000, so that likely will not help. If you are using lots of mailing lists, you might want to try doubling the number of recipients per E-mail that IMail recommends. There is a chance that could help in the meantime. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
We are also have a problem with Declude recently. It doesn't crash our system per say but it causes our system to go to 100% CPU utilization, memory usage goes way up and SMTP timesout (even though there are a lot of STMP Declude processes showing up). We haven't seen that here, but have had several reports of this, and are investigating it. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
RE: [Declude.JunkMail] Declude crashing and taking up 99% CPU
Hello, As far as I can see there is no declude.gp2 file. I just e-mailed the declude.gp1 file to [EMAIL PROTECTED] -- Regards, Terrence Koeman Technical Director/Administrator MediaMonks B.V. (www.mediamonks.nl) Please quote all replies in correspondence. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry Sent: Tuesday, September 11, 2001 14:59 To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU Hello, since I upgraded to declude 1.25a sometimes the following happens: 1. Declude logs something like this: 09/11/2001 04:18:48 Q743b0de (Error 5 at 77fcb9b1 v1.25a) 09/11/2001 04:18:48 Q743b0de (log part 1 saved as C:\declude.gp1) 09/11/2001 04:18:48 Q743b0de (Error 5 at 77fcb892 v1.25a) 09/11/2001 04:18:48 Q743b0de (log part 1 saved as C:\declude.gp1) If you E-mail us the declude.gp1 and declude.gp2 files, we can find out what is causing this. Those are not text files, and almost always have non-viewable portions in them. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com . smime.p7s
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
other similar information? What *exactly* does the error message say, the complete text of it? I can't recall ever seeing NT/2000 report a crash without at least the memory address that the crash occurred at. user32.dll is the main text of the message. There is just the pop up window reporting that user32.dll has failed. What you describe cannot be distinguished with the Microsoft Too-many-service-started-processes problem. Unless I get the exact text of the message, I'll have to assume that that is the problem. The links are http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q142676 and http://support.microsoft.com/directory/article.asp?ID=kb;en-us;Q126962 . There are several sources of this problem. One is that Microsoft has an apparently undocumented type of memory that it allocates to (again, apparently) all processes. It apparently allocates a certain amount of memory to each process, which can differ based on whether the process was started normally or through a service. Microsoft says it allocates this memory to force ill-behaved programs from consuming too much resources -- but doesn't explain why it allocates all those precious resources even if they are not needed. It sounds like they are used for GUI stuff (icons, palettes, mouse pointers, etc.) that aren't used in most services anyways. So this problem can exist with any programs. The reason it is so apparent in IMail (with or without Declude) is that IMail [1] runs as a service and [2] creates a new process (rather than thread) for each E-mail that needs to be delivered. The problem gets even worse with Declude creating extra processes for the virus scanning. We are trying to find a way to prevent this problem, which may or may not be possible to do (it may only be possible to offload it, so that it can only happen once the smtp32.exe process is started, for example). However, this is a difficult process since Microsoft is referring to undocumented memory (their 1gig MSDN knowledge base references to desktop heap, the term they use for this type of memory, only brings up articles about this problem, no documentation of the memory type). -Scott --- Declude: Anti-virus, Anti-spam and Anti-hijacking solutions for IMail. 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
Hello, since I upgraded to declude 1.25a sometimes the following happens: 1. Declude logs something like this: 09/11/2001 04:18:48 Q743b0de (Error 5 at 77fcb9b1 v1.25a) 09/11/2001 04:18:48 Q743b0de (log part 1 saved as C:\declude.gp1) 09/11/2001 04:18:48 Q743b0de (Error 5 at 77fcb892 v1.25a) 09/11/2001 04:18:48 Q743b0de (log part 1 saved as C:\declude.gp1) If you E-mail us the declude.gp1 and declude.gp2 files, we can find out what is causing this. Those are not text files, and almost always have non-viewable portions in them. -Scott --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
