On Tue, Mar 07, 2006 at 10:07:53AM -0800, John Myers wrote: > I don't understand this term "code-tied." It seems to me that all of > the rules are code-tied, since they all depend on what is in the code.
In the end, sure. The way we've been using the phrase, "code-tied" means something that requires "eval:", which means EvalTests and rule plugins. Generally the code that these rules depend on are only made available through full code releases, and therefore the rules are tied to the code. The "standard" rules are all based on regular expressions, and while they're eventually executed as code, they are generally considered simple text string matching and not something more complicated that requires writing perl or calling out to third-party code, etc. These can generally be used on any version of SpamAssassin, and are not specific to any one release/branch. In short, you're correct in saying that everything is code in the end. When it comes down to it, the body/header/etc rules aren't any different from other code, beyond the fact that they have the same API for ages. So from a strictly "what is code and what isn't" POV, they're all code. Generally it's a "text match" versus "something more complicated" differentiation. -- Randomly Generated Tagline: "L: And stop saying Okay, okay? M: Okay. L: Good." - The Professional
pgpCXyG3N6swK.pgp
Description: PGP signature
