A) A small number of larger filer files vs a lot of smaller files
B) Doesn't make any significant difference if you use the SKIPIFWEIGHT
option at
the beginning even though it would still have to open the file to check the
SKIPIFWEIGHT setting.
C) A small number of larger files ordered in the config file ordered from
lightest processing most likely to hit to heaviest processing less likely to
hit
D) Alot of smaller files ordered in the config file from ordered from
lightest processing most likely to hit to heaviest processing less likely to
hit
I would think C or D would be the best option.
I would agree.
Specifically, you would want BODY (or ANYWHERE) filters to only be used after everything else was handled. Those are the most CPU intensive filters.
The last question is what, in number of lines, would be a large filter file. 500, 1000, 2000, 5000, 10,000
That depends on what your concerns are about the large files. As far as Declude is concerned, a single large file of 10,000 lines would be (very slightly) more efficient than say 10 files with 1,000 lines each. But the difference should be almost negligible.
-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 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.
