SA Bugzilla – Bug 4341
reporting broken?
Last modified: 2005-05-19 11:10:56 UTC
I've (I think) got dcc/pyzor/razor installed and configured; however, when I try to report I get : [20604] warn: reporter: no reporting methods available, so couldn't report [20604] warn: spamassassin: warning, unable to report message I'm running on a slackware-10.1 i686. (A maybe related issue is that spamassassin won't parse the following lines from /etc/mail/spamassassin/local.cf (even after I uncomment them :)) # Enable or disable network checks #skip_rbl_checks 0 #use_razor2 1 #use_dcc 1 #use_pyzor 1 # pyzor options # pyzor_options --homedir /etc/mail/spamassassin These aren't relevant but also don't parse if uncommented # Mail using languages used in these country codes will not be marked # as being possibly spam in a foreign language. # - english french hebrew yiddish # ok_languages en fr he yi # Mail using locales used in these country codes will not be marked # as being possibly spam in a foreign language. # ok_locales en I will attach the debug output after committing this.
Created attachment 2877 [details] Debug output
Did you enable any of the reporting modules in your init.pre file?
(In reply to comment #2) > Did you enable any of the reporting modules in your init.pre file? I was going to ask the same thing, but based on the debug output, the only plugins that are enabled are: [20604] dbg: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC [20604] dbg: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC [20604] dbg: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC DCC, Pyzor, and Razor are all plugins in 3.1, so make sure your init.pre is setup correctly.
Thanks for the comments. That of course was the problem. Seems that make install doesn't overwrite the old configuration files (as it shouldn't, although having .new versions populating the install directories might be useful). I also found the discussion of init.pre in README a bit weak. It tells you that you have to enable something, but not quite how. In all fairness though, I'd simply missed the comment entirely. Close this one (it wasn't a bug).
*** This bug has been marked as a duplicate of 4314 ***