After reading the archives (thanks all!) for most of the afternoon, I'm still on the fence with what to expect from Declude.  I run an ISP that gets over 100k emails inbound a day, and the hardware handles it nicely.   SMTP normally never claims more than 20% of available cpus for both in and outbound traffic. 

Here are the questions I've made sofar:

Given the above info, what can I expect the overall processor 'hit' to be on incoming filtering only? 

Does Declude utilize more processing power if I use more checks? 

Are checks run simultaneously, or linearly?

I've read that smtp32.exe is replaced by declude.exe.  Does Declude utilize multi-processors? 

Does declude.exe run as a single process, or in a one-spawned-per-message sort (similar to smtp32.exe).

Can I use an "allow this message to process, but save a copy for further review" type action?

Does the HOLD action allow for easy respooling of an offending message? 

Does an imail serverwide or domainwide filter process the message before or after declude does?

Do you have (or can you suggest) any suggested configs (paid and non-fee) that have a low count of 'real' messages being trapped?

Do you have (or can you suggest) a list of "these hosts must be whitelisted to keep your users from killing you", or similar?

What (if any) are the known issues with integrating with McAfee's SMTP Virus Scan (not on same machine) ?

 

Thanks to all,

 

John

Reply via email to