Hi,
The obvious answer is to look at what is different between the two boxes.
You then need to work out which bit of the email pathway is not working.
It might be that spamassassin is working like a charm, but some other
part of the chain is not doing its job.
You should understand that spamassassin only scans and scores a message,
it does not do anything about removing, archiving etc. In your case
that should be done by amavisd.
If it is a problem with amavisd or postfix you will be better served
asking in mailing lists related to those pieces of software.
But to test spamassassin, run the following command from a command line:
spamassassin --lint --debug
and look for errors.
Then, get an example email with full headers in a text file and feed it
in to spamassassin manually, like:
spamassassin --test < test-email.eml
If you get any errors from either of these people here will probably be
able to help you out.
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...
--
Anthony Peacock
CHIME, Royal Free & University College Medical School
WWW: http://www.chime.ucl.ac.uk/~rmhiajp/
Study Health Informatics - Modular Postgraduate Degree
http://www.chime.ucl.ac.uk/study-health-informatics/
