On Tue, 7 Jan 2003, Steve Thomas wrote: > There's a couple of ways you could do this. You could write a rule that > assigned a negative score, such as: > > header SUBJECT_FOOBAR Subject =~ /FOOBAR/ > describe SUBJECT_FOOBAR Subject contains FOOBAR > score SUBJECT_FOOBAR -100.0 > > OR... > > you add a condition to your procmail recipe: > > :0fw > * < 256000 > * !^Subject:.*FOOBAR > | /usr/bin/spamc
Thanks! The negative rule works well. I now have a much better understanding of how to write and implement such rules. One thing that hung me up was the fact that /etc/mail/spamassassin/local.cf (the global local preference file on Red Hat 8.0) is only read upon initial startup of the SpamAssassin daemon, whereas ~/.spamassassin/user_prefs (the per-user local config file) is read on each iteration of spamc. To help me remember this in the future, I added the following commented text to my /etc/mail/spamassassin/local.cf file: [...begin quote...] # This file is ONLY read on initial startup of SpamAssassin! # On Red Hat 8.0, try '/sbin/service spamassassin restart' in order to # re-start SA and re-read this file. [...end quote...] > I'd opt for the second choice to reduce the overhead of unnecessarily > running the message through SA. It wouldn't hurt to also add the custom > rule, but in theory it shouldn't ever "hit". > > HTH, > Steve I don't mind the performance hit, as we have only ~40 users. Our priority is doing each task well, and your sample negative rule fits the bill. Thanks again. -- Graham Freeman Manager of Information Technology Far Western Anthropological Research Group, Inc. +1 530 756 3941 ext 111 [EMAIL PROTECTED] ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
