On Thu, Mar 16, 2006 at 04:14:53PM -0700, Philip Prindeville wrote: > Is there an easy way to get the list of all the debug facilities?
Not really, it's dynamic based on what you're doing. If you use just "-D" and not specify any facilities you'll enable them all. You'll see lines such as: [7517] dbg: rules: running body-text per-line regexp tests; score so far=1.866 [7517] dbg: uri: running uri tests; score so far=1.866 dbg is the level (dbg (debug) is typical), and the next word is the facility. Common ones are config, rules, uri, plugin, check, etc. > Okay, so I need to add: > ok_languages en fr > loadplugin Mail::SpamAssassin::Plugin::TextCat Yes, you'll want to just uncomment the loadplugin file in the v310.pre file. > I also added the plugin in bugid 4255 as TVD.pm, and added: > loadplugin Mail::SpamAssassin::Plugin::TVD > but I'm wondering what else is needed. I think you need to spend some time reading the documentation and the wiki. :) As for that plugin, as with any rule-focused plugin, you enable the plugin (typically in a .pre file) and then add in rules that call the functions from the plugin. I put some information in the bug about what needs to be done to enable it's usage. It's worth noting that the 4255 plugin is meant for development and not general usage yet, so I wouldn't enable it for production use without developing some accurate rules first (it's worth noting that after some work I put in a version of the plugin w/ some rules this afternoon for the nightly testing run which do work well on my corpus... so hopefully something will come of all this.) -- Randomly Generated Tagline: Knock Knock, Who's there? Kosh. Kosh who? Gesundheit. - Sheridan on Babylon 5
pgpma0m19HLWm.pgp
Description: PGP signature
