On Monday 08 March 2004 03:46 am, Justin Mason wrote: > (a) the over-monolithic nature of SpamAssassin, compared to a more > flexible model where spam-detection techniques can be "plugged in" > and "plugged out" as admins desire. E.g. in a future rev we could > make plugins out of more parts of SpamAssassin, and an admin > could turn off Razor, Pyzor, or DNS tests without affecting others > easily, by tweaking their plugin config.
So then, will we be breaking up Eval.pm (and other stuff) into plugins? That might be nice architecture wise, since then code for a single set of tests that's scattered among several .pm files could be consolidated into a single plugin file. -- Give a man a match, and he'll be warm for a minute, but set him on fire, and he'll be warm for the rest of his life. Advanced SPAM filtering software: http://spamassassin.org
