On Sun, 16 Feb 2003, Don Hammond wrote:
This is a little long, but maybe another example will help.
Thanks very much for the examples!
My spamchkrc currently has 40 spam tests.
I have 29 checks on the Message-ID alone! :)
Following are a couple of the more straightforward recipes.
Very interesting. I'm particularily intriqued by the counting recipes.
May I contact you later for more details? (I'm not very well versed, yet,
in the scoring method.)
Having a separate rcfile to cumulate variables and scores means I don't
have to duplicate the same code over and over (except for the common
variable assignments and INCLUDERC). It's much easier for maintenance.
I was wondering about maintenance.
As has been mentioned by others, the recipes in spamchkrc can be
ordered for performance or anything else your heart desires. One of
these days I want to test if performance is optimized by having the
least costly (header searches) before the more costly (body search)
recipes, or if it's better to have the most frequently matched recipes,
regardless of processing "cost", before the others.
My philosophy (up to this current evolution) was to have the most
frequently hit recipes up front; as that took out the most messages
sooner. It also tends to make some recipes redundant (or unused). I tend
to keep them around anyway. If they don't get used, they don't hurt
anything; and they may catch something that sneaks through the others.
How does one set up the various scores for a recipe? I mean, what
determines if a hit amounts to 2 or 1.38 or whatever?
- fleet -
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail