----- Original Message -----
From: Michael Scheidell
To: Grant Peel
Cc: users@spamassassin.apache.org
Sent: Friday, July 23, 2010 4:40 PM
Subject: Re: sa-update
On 7/23/10 4:28 PM, Grant Peel wrote:
I have a brand new build of FreeBSD 8.0 p#3
Spamassassin installed from ports:
constellation# spamassassin -V
SpamAssassin version 3.2.5
running on Perl version 5.8.9
start over, upgrade your ports tree.
cd /usr/ports
make update
no way of knowing what you have.
SA is 3.3.1
perl is 5.10.(something)
--
Michael Scheidell, CTO
Phone: 561-999-5000, x 1259
> | SECNAP Network Security Corporation
a.. Certified SNORT Integrator
b.. 2008-9 Hot Company Award Winner, World Executive Alliance
c.. Five-Star Partner Program 2009, VARBusiness
d.. Best in Email Security,2010: Network Products Guide
e.. King of Spam Filters, SC Magazine 2008
------------------------------------------------------------------------------
This email has been scanned and certified safe by SpammerTrap®.
For Information please see http://www.secnap.com/products/spammertrap/
------------------------------------------------------------------------------
I used the ports update method Micheal mentioned above (on my dev box that
was used to make the FreeBSD build I am currently using)
cd /usr/ports
make update.
then changed to the /usr/ports/mail/p5-Mail-SpamAssassin directory
cd /usr/ports/mail/p5-Mail-SpamAssassin
make config (changed nothing)
make
make deinstall
make reinstall
answered Y when asked if I wanted to download the new rules
Then found the new /var/db/spamassassin did exist,
Now I am assuming that whenever sa-update is run, the new rules will be put
in there and that my new site configs will be in
/usr/local/etc/mail/spamassassin, and that the users overrides in
/home/<domain>/.spamassassin/user_prefs will still work.
Thanks to all the help you all.
I conclude that when I updated FreeBSD from 8.0 release to 8.0 p#3 that thats
when things broke. (ports not updated correctly).
Learn something new every day!
-Grant
