Re: [Declude.JunkMail] Declude Woes

[Darin Cox]

I believe the MaxQueueProc key should be    HKLM\System\CurrentControlSet\Services\SMTPD32\Parameters\MaxQueProc Darin.     ----- Original Message ----- From: Matt To: Declude.JunkMail@declude.com Sent: Thursday, July 28, 2005 2:44 PM Subject: Re: [Declude.JunkMail] Declude Woes My understanding is that IMail 8.15 HF2 and everything before it is limited to just 64 threads based on the fact that it is not multi-threaded like 8.20 now is.  I believe that the default setting in IMail is less than 64 and can be increased.  There is also a timeout setting that should be changed to only 60 seconds or less to free up dead connections, and some other tweaks that can be made.  If IMail hits this limit, it won't allow new connections to be made.  Pre-2.06 versions of Declude also used to reference this setting (MaxQueProc) as the limit that determined when to send messages into overflow, but 2.06 now uses a new configuration setting that you put into a Declude.cfg file (a new file). With that said, Declude won't be able to process 64 E-mails simultaneously on any dual processor server available today because there just simply isn't enough juice available.  Most will note that when messages are growing in Overflow that CPU utilization should be redlined at 100%.  If not, tweaking the settings can help, but this is most likely something that Declude is calling that is non-responsive such as DNS, an external app, or a virus scanner, but this is generally not the case.  So increasing the number of threads will have a negligible impact on a default installation as far as the volume of overflowed messages go.  Generally Overflow is triggered on huge message volume, especially stuff that needs to be virus scanned.  When something happens that backs up my server, I generally turn off my second virus scanner in order to catch up.  On my system, McAfee, even though it is more efficient than all but three others, is by far the biggest CPU user, and it makes a big difference to turn it off while backed up. Anyway, here's a list of the registry hacks for both IMail and Windows 2003 (might apply to Windows 2000 also): Clearing TIME_WAIT sockets more quickly: ========================================================================= HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpTimedWaitDelay Data type REG_DWORD Range 0x1E 0x12C (30–300 seconds) Default value 0xF0 (240 seconds = 4 minutes) Set To 30 Allocating more outbound (client) sockets: ========================================================================= HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort Data type REG_DWORD Range 5,000–65,534 Default value 5000 Set To 65534 IMail ========================================================================= HKLM\SYSTEM\CurrentControlSet\Services\Parameters\MaxQueProc Data type REG_DWORD Default value 30 Set To 60 Matt Glenn \ WCNet wrote: I had the same situation with Overflow and Spool getting overloaded. Increasing the number of SMTP process in IMail to 90 keeps it clear except under extreme situations. IMail 7.15. G.Z. ----- Original Message ----- From: "Will" <[EMAIL PROTECTED]> To: <Declude.JunkMail@declude.com> Sent: Thursday, July 28, 2005 8:35 AM Subject: [Declude.JunkMail] Declude Woes A number of years ago I purchased Declude and ultimately abandoned it due to the crippling problem that would leave our spool directory overfilled with mail and a mail server that was delivering mail late. Sometimes up to 24 to 48 hours late in the worst cases. Last year I decided to give Declude a chance again and repurchased the software upgrade. It's been over a year now and I still have the same problem. It's killing me. Declude will create an overflow directory and mail will just pile up, customers will get angry, and we look the fool. I have spoken with Declude support about this and they had me change a value in my virus.cfg to "MAXATONCE 1". I still see a number of declude.exe processes when the overflow directory comes into use and the overflow directory is never used when I disable Declude. Right now, my mail server is a couple hours behind with over a hundred thousand messages in cue. I have disabled Declude so the server can catch up, but I still want antivirus and spam protection. I am all out of ideas and resources. I had thought the antivirus was taking too long to process at one point and my last concern was that DNS resolution was not fast enough for the SPAM tests, however, when enabled, the Imail integrated black lists resolve fast enough that I do not see this problem. Does anyone have any suggestions? Or better yet experience with this issue and know of a cause or resolution. I've grown to fear the overflow directory and I would have thrown out Declude already if not for the lack of chatter about this issue on the list. Will --- 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. -- ===================================================== MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ =====================================================