On Mar 1, 2011, at 9:50 AM, Karsten Bräckelmann wrote:
On Tue, 2011-03-01 at 09:28 -0800, macke...@animalhead.com wrote:
On Mar 1, 2011, at 6:35 AM, Karsten Bräckelmann wrote:
Since an upgrade. Sounds like the new SA installation actually
uses a
different site-config dir -- and probably prefix altogether.
The spamassassin(1) man page will tell you, section Configuration
Files.
Note that in the same list of paths also is a version tagged one,
just
in case you're looking at the old man page.
I grepped all the files/direcs noted in SPAMASSASSIN(1) and
Mail::SpamAssassin::Conf(3), the former included
/var/db/spamassassin/3.003001 in its "default" list and
/usr/local/etc/mail/spamassassin in its "site-specific" list
(the latter is where my local.cf with report_safe 0 is located)
Running spamassassin with the -D debug switch also will tell you the
correct path.
animalhead:~ $ spamassassin -D
Mar 1 09:12:23.566 [68051] dbg: logger: adding facilities: all
Mar 1 09:12:23.566 [68051] dbg: logger: logging level is DBG
Mar 1 09:12:23.566 [68051] dbg: generic: SpamAssassin version 3.3.1
Mar 1 09:12:23.566 [68051] dbg: generic: Perl 5.010001, PREFIX=/usr/
local, DEF_RULES_DIR=/usr/local/share/spamassassin, LOCAL_RULES_DIR=/
etc/mail/spamassassin, LOCAL_STATE_DIR=/var/lib/spamassassin
^^^^^^^^^^^^^^^^^^^^^
There's a severe difference to the man-pages you just quoted.
How did you install SA? It appears you ended up with two different
installations, though both being 3.3.1.
Installing SA 3.3.1 via CPAN cleared up problems from a failed attempt
by our hosting provider to update something on the server (they never
said exactly what), which left SA inoperative. (It cleared up problems
except for this one -- how SA tagged spam.) The original SA install
years ago was using a script from our hosting provider.
[...]
Mar 1 09:12:23.605 [68051] dbg: dns: is Net::DNS::Resolver
available? yes
Mar 1 09:12:23.605 [68051] dbg: dns: Net::DNS version: 0.66
At this point, spamassassin waits for input on STDIN. Run the
debugging
with lint, which uses an internal mail. The command below will grep
out
the site-config directory used.
spamassassin -D --lint 2>&1 | grep "site rules"
animalhead:~ $ spamassassin -D --lint 2>&1 | grep "site rules"
Mar 2 07:33:27.529 [75068] dbg: config: using "/etc/mail/
spamassassin" for site rules pre files
Mar 2 07:33:27.566 [75068] dbg: config: using "/etc/mail/
spamassassin" for site rules dir
animalhead:~ $ sudo find /etc -name "local.cf"
/etc/mail/spamassassin/local.cf
animalhead:~ $ sudo find /usr -name "local.cf"
/usr/local/etc/mail/spamassassin/local.cf
So I edited etc/mail/spamassassin/local.cf to include report_safe 0.
Probably all will be well now.
This problem may go back further than the 3.1.1 install. I have a vague
memory of trying to tweak some scoring coefficients years ago, without
SA noticing those changes.
A plain 'spamassassin --lint' does not generate any warnings, right?
Right.
Thanks very much,
cmac
