I have developed a hypothesis, which could explain eventually this strange
phenomenon:
spamassassin reads the configuration files directly, but not spamd ---
during installation the rules were compiled by the Debian postinstall
script into a format, which is read exclusively by spamd during launch
Watch out for following rule, as mentioned working fine with direct
invocation of the spamassassin script, but even after putting it in the
/usr/share/spamassassin 20_head_tests.cf and 50_scores.cf files (did so
for pure desparation and testing; I know, that this is a no-no) it is
consequently igno
I run amavisd-new and spamassassin 2.60 (backports to Debian Woody
GNU/Linux from the unstable branch) on a sever at office and at my own one
at home, where I write this at now (clamav is used solely at office
additionally for virus/worm scanning) with the postfix MTA (stable woody
version).
The p