On Fri, 31 Jul 2015 12:38:00 -0700 Ian Zimmerman wrote: > I run spamassassin -r from cron nightly. Last night I got this > output: > > Jul 30 23:00:11.830 [31065] warn: reporter: no reporting methods > available, so couldn't report > Jul 30 23:00:11.830 [31065] warn: spamassassin: warning, unable to > report message > Jul 30 23:00:11.830 [31065] warn: spamassassin: for more information, > re-run with -D option to > see debug output > > I tried to follow the instructions and run > > spamassassin -D -r `ls spam`
If the problem persists, I'd run spamassassin -r one spam at a time until you get the error and then run spamassassin -D -r on that particular spam. > The only external reporting method I'm aware of that should be active > is Razor. Running razor-report `ls spam` works normally as expected. I think the error message is a bit misleading. According to the documentation a plugin can set two flags, one to say that reporting is available and another to say it completed successfully. In all the plugins that support reporting, both flags are set in the same place. So "no reporting methods available" really means that no plugin succeeded in reporting one of the spams. In your case that just means that a razor report failed. > I'd also > like to clarify more generally what spamassassin -r does. From a > recent thread here I learned that it also does the equivalent of > sa-learn --spam. Right? So presumably it doesn't consider this a > "reporting method" or how could it be not available? Reporting is separate from learning.
