sa-update question

[Scott Silva]

on 9/27/2007 1:33 PM Jay Chandler spake the following:
> Anthony Peacock wrote:
>> Hi,
>>
> 
>>
>> "# The rules created by the "sa-update" tool are searched for here.
>> # This directory contains the 3.001001/updates_spamassassin_org
>> # directory structure beneath it.
>> # Only un-comment this setting once you have proved that the sa-update
>> # cron job has run successfully and has created a directory structure 
>> under
>> # the spamassassin directory within this one and has put some *.cf 
>> files in
>> # there. Otherwise it will ignore all your current rules!
>> # The default location may be /var/opt on Solaris systems.
>> SpamAssassin Local State Dir = # /var/lib/spamassassin"
>>
>> Basically, SA on its own knows to use the newer rules in the 
>> /var/lib... hierachy over and above any others.  This initially caused 
>> problems in MailScanner, but Julian very quickly made MailScanner work 
>> by default in this setup.  Can't remember the version that this 
>> changed in, but it was a while ago.
> 
> Fantastic!
> 
> And even though there are several "version" directories underneath it, 
> it knows where to go?
> 
> 
When you upgrade spamassassin, you can usually get rid of the older versions 
update directories if you want to free the space. The upgrade doe not remove 
them, nor does sa-update.

-- 
MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!