>This may be overly obvious, but any CPU load could be minimized if RegEx tests were only conducted >on email that flunks other preliminary tests. Don't know if SpamChk works that way or not.
I would only do that if there were CPU usage problems in to begin with. In some cases a particular regexp line might be the only rule keeping a piece of spam out. And if you were to design your expressions carefully you could likely cut out a LOT of comparisons from those always growing blacklist files. Actually come to think of it, test pruning like you mentioned could sure cut down a lot of redundancy. I've noticed that the headers declude adds sometimes contain more than one test which should have individually pushed that particular message over the line and into the spam mailbox. You could probably cut down a lot of CPU overhead by optimizing in both directions, quitting the spam test process as soon as a message has enough weight to fail and only running certain tests after others have failed. (Or if others have not failed?) Maybe for some sort of high traffic mode? Rob Salmond Ontario Die Company (519)-576-8950 ext. 132 --- [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.
