I had a problem very similar to this, now corrected. Along the way I encountered some peculiarities. They may or may not be bugs, and may or may not be related to this report. I believe the problem was triggered by an unsuccessful run of sa-update, and corrected by a successful one.
I'm running a new system, Debian testing, 2.6.16 stock kernel. spamassassin has been on it for a few weeks, so it's possible it may have gone throught some upgrades. Today was the first time I tried to use it. 1. as root, ran sa-update. I got an error referring to SHA1 and a failure notice. 2. started spamd, running as user mail. I notice that although I set the user as mail in /etc/default/spamassassin, one of the spamd processes ran as root. Also the socket and spamd.pid files were owned as root. 3. I invoked spamc as user mail from exim ACL's. 4. Every mail I scanned a) had a score of 0 b) said "(no report template found)" for the spam report 5. I su'd to mail and ran spamassassin -D from there. Like the output at the top of this bug, mine referred to /var/lib/spamassassin/3.001001 and did not show any substantive rules files. 6. Also, it reported that it was autolearning (as ham) the item with a score of 0, since that was < than the threshhold of .1. 7. I reran sa-update as root. This time it completed without error. 8. reran spamassassin -D as mail. This time it showed a whole bunch of rules file, and I got some hits and a non-zero score. I also got a real report. Peculiarities remaining: * original failure of sa-update (item 1). I think I saw this same first-time failure of sa-update on another system. My theory is that this led to problems noted in 4a, 4b, and 5. All but 4b appear in the original problem report. * some processes and files from spamd are root (item 2). Presumably this has something to do with start-stop-daemon. Configuration error on my part? Something that should be documented? * autolearn as ham on 0 score (item 6). I thought some docs said the threshold was negative for ham. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
