Daniel J McDonald wrote: > On Fri, 2010-01-29 at 09:18 -0500, Bowie Bailey wrote: > >> McDonald, Dan wrote: >> >>> Please excuse the top-post. This truly brain-damaged mua does not >>> allow me to edit the body. >>> >>> Easiest way to disable whitelists is: >>> >>> grep -E score\ RCVD.+- >>> /var/lib/spamassassin/updates_spamassassin_org/50_scores.cf | cut -d\ >>> -f1-3 > /etc/mail/spamassassin/no-whitelists.cf >>> >> Nice command line magic there! It took me a bit to figure out how it >> worked. >> > > It helps that whitelists are disabled in ruleset #1, so we can count on > a zero in that position. > > As a one-liner, it is something that can be tacked on the end of a > script that calls sa-update (or in the middle, if you follow up your > sa-update with an sa-compile). Just watch out for the two spaces in the > cut command `cut -d\ -f1-3` > > >> I never would have thought of doing it that way. >> > > cut is one of my favorite tools. >
It is more the searching for a negative score to identify the whitelists that I thought was interesting. I probably would have been trying to figure out a text pattern in the rule names. It did take me a bit to figure out where the zero at the end was coming from! :) -- Bowie
