Using Declude JunkMail Pro v2.0.6.16 from 2005-05-25 on IMail v8.14 plus hotfixes on a dual 3.0 GHz Pentium 4 Xeon Proliant with hyperthreading on. There is no on-access antivirus software installed, and no defragmentation, no indexing or other type of disk tasks were running.
I re-queued a message that was initially detected as spam and had modified my Declude filters so that the message would be accepted. I copied (not moved) the D*.SMD file to the spool folder, and then the Q*.SMD file to the spool\overflow folder. In this way, the message is re-scanned by Declude and if not held, it is then delivered by IMail. Messages were backlogged with multiple declude.exe processes running and occasionally using CPU (according to Task Manager). Collectively, this made CPU usage quite high. But messages were not being delivered inbound. I used my firewall to shut off new inbound messages, then paused each declude.exe process and trying to then allow a single instance to run. No joy. I killed all the declude.exe processes and then sent an internal mail to wake up the queuing and overflow processing. No joy, same behaviour. I looked at the logs, now that they wouldn't be clogged with unrelated lines caused by new inbound messages. The performance problem was because there were as many as 5 attempts per second at locking the Q*.SMD file, as per the Declude log, and ditto for the IMail log at about the same rate. Sample Declude log entry: 01/18/2006 00:10:56 Q1E4CBFE900D412F6 Cumulative action(s) taken on this email = LOG WARN [LAST ACTION=WARN] 01/18/2006 00:11:03 Q1E4CBFE900D412F6 WARNING: Could not unlock D:\IMAIL\SPOOL\_1E4CBFE900D412F6.~MD due to error #183. 01/18/2006 00:11:06 Q1E4CBFE900D412F6 Could not lock D:\IMAIL\SPOOL\Q1E4CBFE900D412F6.SMD: 183. 01/18/2006 00:11:07 Q1E4CBFE900D412F6 Could not lock D:\IMAIL\SPOOL\Q1E4CBFE900D412F6.SMD: 183. 01/18/2006 00:11:07 Q1E4CBFE900D412F6 Could not lock D:\IMAIL\SPOOL\Q1E4CBFE900D412F6.SMD: 183. Sample IMail log entry: 01:18 00:10 SMTP-(0000000000000000) Info - Adding Queue file D:\IMail\spool\Q1E4CBFE900D412F6.SMD 01:18 00:11 SMTP-(1e4cbfe900d412f6) processing D:\IMail\spool\Q1E4CBFE900D412F6.SMD 01:18 00:11 SMTP-(1e4cbfe900d412f6) [E] lock file exists for D:\IMail\spool\Q1E4CBFE900D412F6.SMD I killed all the declude processes again, and shut down the IMail SMTP service, then deleted the extra _*.~MD file. I restarted the SMTP service and sent another local message to wake up the message processing. Joy! I'm providing this writeup here in hopes that it may be a useful troubleshooting story for others. I'm providing the logs to Declude Support in case they see a good reason to modify their "retry behaviour" in the circumstance the logs indicate. Andrew. --- [This E-mail was scanned for viruses by Declude EVA 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.
