> -----Original Message----- > From: dar...@chaosreigns.com [mailto:dar...@chaosreigns.com] > Sent: Friday, May 06, 2011 11:48 AM > To: users@spamassassin.apache.org > Subject: Re: Dumb questions > > On 05/06, Greg Lentz wrote: > > We are currently running SpamAssassin 3.2.4 on Mac OS 10.4.11 with > a third > > Yup, upgrading to 3.3.1 would be good. "Rule updates for 3.2.x > effectively > stopped late 2008." > > Start by making sure you have good backups.
Backups of what? I would probably just make copies of the whatever directories I was going to upgrade over in case I failed miserably. > > 1. How can I determine where the running version of spamassassin is > > located? > > That's not a very easy question to answer, given all the possibilities > of MTAs (mail server software) and path configurations. One of your best > options may be to run something like: > > find / -name spamassassin > > Which should find any instance of spamassassin on your machine. This I actually had done. This is what is returned after I go into superuser mode. /private/etc/mail/spamassassin /usr/bin/spamassassin /usr/local/bin/spamassassin /usr/local/share/spamassassin /usr/share/spamassasssin If I type ps -aux, I can see an entry for /usr/local/bin/spamd with some paramaters after it and I see some spamd child entries as well.cd > > > 2. Where are the rules for spamassassin located? > > /var/lib/spamassassin/ I don't have a lib directory in my var directory. Could be a peculiarity to OS X, which doesn't always keep the Unix stuff in the same locations. > > > 3. Where are updates to rules logged (I suspect I haven’t actually > > received a rules update in over a year. > > I don't think there are logs, other than possibly emails resulting from > running sa-update from cron. Well, since it looks like SA 3.2 hasn't been getting rules for a couple of years, that probably isn't as critical at the moment. -- Greg Lentz
