Date: Wed, 14 Mar 2007 13:00:10 GMT From: Michael Scheidell <scheidell@secnap.net> To: perl@FreeBSD.org Subject: Re: ports/108934: mail/p5-Mail-SpamAssassin: spamassassin uses /var/lib/spamassassin directory but /var/lib doesn't exist on FreeBSD Message-ID: <200703141300.l2ED0AGg037978@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/108934; it has been noted by GNATS. From: Michael Scheidell <scheidell@secnap.net> To: Matus UHLAR - fantomas <uhlar@fantomas.sk> Cc: bug-followup@FreeBSD.org Subject: Re: ports/108934: mail/p5-Mail-SpamAssassin: spamassassin uses /var/lib/spamassassin directory but /var/lib doesn't exist on FreeBSD Date: Wed, 14 Mar 2007 08:53:38 -0400 Matus UHLAR - fantomas wrote: > run sa-update. It will create > /var/lib/spamassassin/<version>/updates_spamassassin_org/ directory, where > it puts updated rules, if it founds them. spamassassin and spamd later check > these rules instead of those in /usr/local/share/spamassassin/50_scores.cf > > You may need older installation of spamassassin to verify this, I'm not sure > that 3.1.8 has some updates, but I was able to update rules for 3.1.7 at > least twice. > > I think some of this was discussed on SpamAssassin list. If you actually let sa-update put the files in /var/lib/spamassassin, it REPLACES original files. I think the suggestion was to run sa-update like this: sa-update --updatedir /usr/local/share/spamassassin my suggestion to patch sa-update to do that was not met with enthusiasm. try the above, things should work better, and I will look at patching sa-update for the ports only. ----------------------------------------------------------------- This email has been scanned and certified safe by SpammerTrap(tm) For Information please see http://www.spammertrap.com -----------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200703141300.l2ED0AGg037978>