> 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,
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 behavi
On Thursday 12 October 2006 04:05, Giampaolo Tomassoni wrote:
> :(
>
> One week ago if I would report a mail as spam to razor, they would soon
> report as such at the very next spamassassin -t.
>
> Now they don't...
>
> Is that I sent something they know it is not spam, or is something else?
Well
:(
One week ago if I would report a mail as spam to razor, they would soon report
as such at the very next spamassassin -t.
Now they don't...
Is that I sent something they know it is not spam, or is something else?
---
Giampaolo Tomassoni - IT Consultant
Piazza
:(
One week ago if I would report a mail as spam to razor, they would soon report
as such at the very next spamassassin -t.
Now they don't...
Is that I sent something they know it is not spam, or is something else?
---
Giampaolo Tomassoni - IT Consultant
Piazza
