On Friday September 11 2009 13:27:11 franc wrote: > Yes, i restarted spamassassin, and now i found out, that amavis is handling > some configurations in 20-debian_defaults, here i can put some blacklist > (with amavis notation of course).
This is independent from SpamAssassin. > But i wonder why the spamassassin configfiles are not used. Is there a > switch in amavis to override this? The SpamAssassin config files are observed at the default SpamAssassin paths. Check that directories used by SpamAssassin are what you expect them to be - start as: 'amavisd debug-sa' and check the SA log soon after a start. > Spamfiltering is working: i have Spam-Tags in my mailheaders. But maybe not > from spamassassin? > I read: X-Spam-Score, X-Spam-Flag, X-Spam-Level, X-Spam-Status Flags, and > X-Virus-Scanned: Debian amavisd-new at ew6.org > > And Spam is moved automatically to the .Spam Folder. Good. Make sure your rules are working: - check syntax: # su vscan -c 'spamassassin --lint' - check your rules on a test mail, be sure to run it under the same user as amavisd will run under: # su vscan -c 'spamassassin -t <test.msg' Mark
