On Fri 11 Sep 2009 01:27:11 PM CEST, 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).
do not edit this file, use some user files to overwride contense
if i remember 50_user... is in this same dir, why ?, what happend when
you update, will you love to see your edits go to dev-null ? :)
But i wonder why the spamassassin configfiles are not used. Is
there a switch in amavis to override this?
spamassassin 2>&1 -D --lint | less
cf files are read on all this paths, no other dirs or file can be edit
with configs
--
xpoint
