MM> Here's an idea: keep the whitelist but make a separate MM> default_whitelist_from directive that acts the same as whitelist_from but MM> can have its own score, and use default_whitelist_from in 60_whitelist.cf. MM> That way (a) anyone can turn off the default whitelist with a single score MM> entry in a preference file, and (b) spam reports will refer to the "default MM> whitelist" so it's easy to diagnose when cases like this happen.
Sounds smart. I think I'm more leaning towards just commenting out all the entries in 60_whitelist.cf and sticking some explanation for why the entries are disabled, plus maybe something in the README. C _______________________________________________________________ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
