James Lay wrote: > On Mon, 13 Nov 2006 09:54:11 -0700 > James Lay <[EMAIL PROTECTED]> wrote: > > > On Mon, 13 Nov 2006 11:07:32 -0500 > > Bowie Bailey <[EMAIL PROTECTED]> wrote: > > > > > James Lay wrote: > > > > Hello All! > > > > > > > > So....I'm thinking about trying sa-update. My rules are > > > > in /etc/mail/spamassassin. Are there any gotchas or things I > > > > need to be wary of before I plunge ahead? Just curious as I > > > > see a lot of traffic on this topic in here. Thanks. > > > > > > There was a problem with sa-update on SA 3.1.6, but as long as you > > > are running 3.1.7, everything should be good. > > > > > > There was an issue initially with sa-update creating the > > > directory, but not downloading the files the first time you ran > > > it, but I think that has been fixed now. > > > > > > Just run sa-update (no options needed) and then restart spamd. > > > > Hrmm....so now I > > have /var/lib/spamassassin/3.001007/updates_spamassassin_org. Why > > does sa-update put them there since it reads and uses them > > from /etc/mail/spamassassin? > > Ok so after checking the mod times in /usr/share/spamassassin I see > all my files were updated. So /var/lib/spamassassin... will hold a > copy of the updated files?
After running sa-update, you will have three rule directories. /usr/share/spamassassin will hold the default rules that were installed with SA. /var/lib/spamassassin/... will hold the updated rules that are downloaded by sa-update. /etc/mail/spamassassin holds your custom rules and add-on rulesets. SA will use the updated rules if the directory exists. You should not change the files in the first two directories. They will be overwritten when you update. -- Bowie
