>>Good to know. Tried it before I fixed the directives in >> /etc/mail/spamassassin/local.cf but got no output, which I guess >> confirms it's not looking there by default for it's config file. > > Not necessarily. However, you haven't tried another of my earlier > suggestions, yet, which would do a better job of confirming where the > configuration files are being read from. Use spamassassin -D. Try > spamassassin -D --lint, for instance. Among other things, I saw > something like the following on 2.64 on FreeBSD that I installed just > for you :-) > > debug: using "/usr/local/share/spamassassin" for default rules dir > debug: using "/usr/local/etc/mail/spamassassin" for site rules dir > debug: using "/staff/ryan/.spamassassin" for user state dir > debug: using "/staff/ryan/.spamassassin/user_prefs" for user prefs file Aha, here's my debug output for file locations (Mac OS 10.3.4):
Aug 30 10:54:01 xserve1 spamd[13769]: debug: using "/Library/Perl/share/spamassassin" for default rules dir Aug 30 10:54:01 xserve1 spamd[13769]: debug: using "/Library/Perl/etc/mail/spamassassin" for site rules dir So here's the correct command for startup (till I can rebuild with the correct paths): /usr/local/bin/spamd -d --pidfile /var/run/spamd.pid -u spamd --siteconfigpath=/etc/mail/spamassassin -- Randall Perry sysTame Xserve Web Hosting/Co-location Website Design/Development WebObjects Hosting Mac Consulting/Sales http://www.systame.com/
