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.
