"Theo Van Dinter" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]

>On Fri, Nov 10, 2006 at 11:31:31PM -0500, Debbie D wrote:
>> Is sa-update something built in or is it an plug-in??
>
>It's a script that comes with 3.1.
>
>> I ran sa-update && service spamassassin restart
>> and was told spamassassin is an unknown service (dur I knew that)
>
>Ok.  replace "service spamassassin restart" with the appropriate command 
>for
>your machine.
>
>> BUT.. I see neither directory has updated files:
>> /usr/share/spamassassin
>> /etc/mail/spamassassin
>
>Correct.
>
>> Now I ran sa-update -D
>
>:)
>
>> and poking more I see it did bring down the latest cf files in
>> /var/lib/spamassassin/3.001007/updates_spamassassin_org
>
>Yep.
>
>> I have verified manually that at least one rule set has changed since I 
>> last
>> upgraded on Oct 11th..
>> 7733 Nov 10 22:53 25_uribl.cf
>> 6738 Oct 11 22:35 /usr/share/spamassassin/25_uribl.cf
>
>Yep.  80_additional.cf is a new file too.
>
>> So now my next question is.. am I missing something here to have these
>> downloaded rule sets in effect?? The FAQ say I should have to do nothing 
>> but
>
>Nope.
>
>> but somehow I don't think that's right.. I never told SA to look for 
>> rules
>> in this new directory and even if I did then it would be reading the rule
>> sets twice and causing a huge load issue..
>
>SA knows to look there by itself (see "perldoc spamassassin"), and it's not
>reading anything twice.  SA uses the local state dir
>(/var/lib/spamassassin/...) instead of the default rules dir
>(/usr/share/spamassassin).


OK thanks Theo..  what would be the best way for the to triple verify indeed 
it is picking up these new rules?? I'll set this to cron today on a weekly 
basic I think.. is that frequent enough??

And I assume as these folders start creating themselv'es with the new update 
SA knows enough to look at the lestest set only???




Reply via email to