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] logging options for junkmail...
We want to change our logging options so that non-spam emails are not logged. You can add a line LOG_OK NONE to the \IMail\Declude\global.cfg file, and Declude won't record information about non-spams. -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] Whitelist
Is WHITELIST on the global.cfg specific to Declude JunkMail or is it also taken into account by Declude Hijack ? --- 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] Whitelist
Is WHITELIST on the global.cfg specific to Declude JunkMail or is it also taken into account by Declude Hijack ? It is specific to Declude JunkMail. For Declude Hijack, you can use ALLOWIP 127.0.0.1 in \IMail\Declude\hijack.cfg. -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
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 .
