![](https://seccdn.libravatar.org/avatar/a3920b39aac5d5c0159ebafab456f824.jpg?s=120&d=mm&r=g)
Patrick Shanahan wrote:
* Stefan Suurmeijer
[06-04-04 08:42]: Heh, valid q, I usually only RTFM as a last resort. Did do it though, -D adds no info since the message somehow never gets to spamd. Startup seems normal, only something about no dbs found, selecting ruleset 0.
Sounds like spamassassin has nothing to compare to the email to rate it. Did you run a series of *good* emails thru 'sa-learn --ham' and a series of known *spam* thru 'sa-learn --spam' to build a database?
No. But that's not the problem, the problem is that it doesn't process it, even when compared to an empty ruleset (which wouldn't happen since there is a default ruleset added in the install) it should process the mail and add the headers, albeit that then all scores would be zero.
also, what parameters are you using when starting spamd?
Suse default: -d -c -a -L Worked fine on the old server so I saw no reason to change it.
But you are the only administrator of spamassassin? You do not allow other users to configure/define spamassassin? I would remove -c and -a.
Yup, it's my personal machine. No one else has access to the configuration. -c and -a seem very useful. I want to be able to use a .spamassassin file per user and auto-whitelist.
from 'man spamassassin':
INSTALLATION The spamassassin command is part of the Mail::SpamAssassin Perl module. Install this as a normal Perl module, using "perl -MCPAN -e shell", or by hand.
For further details on how to install, please read the "INSTALL" file from the SpamAssassin distribution.
Been there, done that. I tried a force install Mail::SpamAssassin through CPAN just to make sure that it wasn't some missing file that was causing this. Compiled without a glitch but didn't change a thing. Why does this always happen on a Friday? Stefan