patrickbaer wrote:
Dear Lord, I am going nuts! I promised my colleagues a new filter three days
ago. Now they are drowning in spam and I have no idea about what's going on!
I have this test-machine with a fresh installation of postfix, spamassassin
and amavisd and it works like a charme. I have a catch rate of no less than
99.6% on this machine and not a single false negative!
Now on the crappy live box, absolutely NOTHING works as it should. I just
tried, in my despair, to apply a custom rule, but no way it will accept
them! Added it to local.cf, no work. Added a new file to
/var/lib/spamassassin.../20_test.cf, no work. Spamassassin parses the rule,
yes, but it doesn't apply the score!
Pleeeeeeeeease, what the hell is going on there and how can I find out how
to solve it? I have no idea where to go from here any more...
the first thing is to clam down. then try to explain in a way that _we_
understand what problem you have. saying "nothing works" is meaningless.
if a spam message is missed, then save it to a file. Please save an
unalatered message (if your mailer or an internal exchange modifies the
message, it is useless). then post a copy somewhere so that we can test
it on our systems (try pastebin, or use your own web server). also run
'spamassassin -t < message.file' on both servers (please use the same
message file) and see the results. once again, use an unmodified message
(it's ok if few headers are added by amavisd-new or your MTA/MDA after
filtering).
if AWL is causing you problems, disable it and _restart_ amavisd-new.
when you train SA, make sure you train it as the same user that
amavisd-new uses. if using mysql for Bayes, force a single user:
bayes_sql_override_username spamassassin
(do this in your local.cf).
when you modify a rule, a .cf or a .pre file, you need to reload
amavisd-new. if you use sa-compile, run it before reloading amavisd-new
or testing.
