From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED] > > 1) My install of FreeBSD 6.2 doesn't have /var/lib, let along > > /var/lib/spamassassin, so I used an --updatedir of > > /usr/local/etc/mail/spamassassin/sa-updates, which seems to > work. Is this > > reasonable, or will it conflict with anything? Local.cf and > the .pre and > > other files reside in the parent directory. > > That's probably not a good place for it (in a sub directory > of the site > config directory). I believe the config code will recurse into the > subdirectory and load everything a second time (once as local state > data, then again as the local site config) and cause number 2 below...
rm -rf /usr/local/etc/mail/spamassassin/sa-updates mkdir /home/vscan/sa-updates > > 2) I get some interesting output while running 'sa-update > --updatedir > > /usr/local/etc/mail/spamassassin/sa-updates --channelfile > > /home/vscan/sare-sa-update-channels.txt --gpgkey 856AA88A', > and having a > > channelfile that specifies a number of 70_sare rules. Things like: > > > > 'Subroutine __SARE_SUB_OBFU_LQUOT_head_test redefined at > > /tmp/.spamassassin966SSGKUttmp/200512270000.cf, rule > __SARE_SUB_OBFU_LQUOT, > > line 6.' > > > > show up. Anything to be worried about? > > Yes. Either you've got SARE rules already in > /usr/local/etc/mail/spamassassin (from a manually update or Rule du > Jour) or the config code is recursing into the sa-updates > sub-dir. I've > move the sa-updates somewhere else (if you don't want to use > the default > of /var/lib/spamassassin). $ sa-update --updatedir /home/vscan/sa-updates --channelfile /home/vscan/sare-sa-update-channels.txt --gpgkey 856AA88A $ Works like a champ. Thanks for the help. Kurt
