Matt Kettler wrote:
That's an amavis thing, but I presume it means there is no score (ie: SA
did not completely analyze the message, so no score was computed).
This could mean message was not fed to spamassassin (due to hard
whitelist or bypass_spam_checks), or amavis timed-out the spamassassin
process (which is very likely to happen if your sa_timeout is less than
120, and you are using bayes).
That said, you'd have to ask someone who knows amavisd-new. I don't. But
that's my best educated guess. I hope it helps some.
Thanks Matt. You could be right. I don't know. I will ask on Amavis list
as Theo suggested.
M
M.Lewis wrote:
I've seen a couple of mails come through lately with score=x. Perhaps
there have been some coming in all along like that and I haven't
noticed it.
What does score=x mean?
Thanks,
Mike
X-Virus-Scanned: amavisd-new at cajuninc.com
X-Spam-Score: -
X-Spam-Level:
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
Received: from moe.cajuninc.com ([127.0.0.1])
by localhost (moe.cajuninc.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id uJfhQbv7NXdm for <[EMAIL PROTECTED]>;
Tue, 3 Oct 2006 10:58:26 -0500 (EST)
Received: from moe.cajuninc.com (moe.cajuninc.com [127.0.0.1])
by moe.cajuninc.com (Postfix) with ESMTP id A602F640189
for <[EMAIL PROTECTED]>; Tue, 3 Oct 2006 10:58:07 -0500 (EST)
--
As far as we know, our computer has never had an undetected error. -
Weisert
23:25:01 up 13 days, 4:59, 8 users, load average: 0.07, 0.24, 0.39
Linux Registered User #241685 http://counter.li.org
