On Thu, Oct 12, 2006 at 08:24:11PM -0800, John Andersen wrote: > I sometimes wonder if 3.1.5 broke something in razor report because > that is when I first noticed it seemed to be ineffective to report.
I'm not quite sure why people think SA changed or is broken. If you're
seeing different behavior, it's far more likely that something changed
on the Razor side, but they're a different project so you'd have to talk
to them. :)
As is usually the answer, if you're interested in knowing what's going on, run
with -D (and in this case, the reporter facility), and you can see the razor
agent debug output. ie:
$ spamassassin -r -D reporter < message
[...]
Oct 13 10:50:43.803625 report[512]: [ 5] mail 1.0, eng 4: Server accepted
report.
Oct 13 10:50:43.803734 report[512]: [ 5] mail 1.1, eng 4: Server accepted
report.
[...]
Oct 13 10:55:09.407839 report[740]: [ 5] report: mail 1, 0: Server accepted
report.
[...]
--
Randomly Selected Tagline:
"When all else fails, pour a pint of Guinness in the gas tank, advance the
spark 20 degrees, cry "God Save the Queen!", and pull the starter knob."
- MG "Series MGA" Workshop Manual
pgpSDRV9qXi6O.pgp
Description: PGP signature
