autolearn=failed ---- after upgrade to 3.11

[Steven Manross <st...@manross.net>]

X-Spam-Status: No, score=-2.6 required=5.0
tests=AWL=0.023,BAYES_00=-2.599 
 autolearn=failed version=3.1.1
 
It seems that since upgrading to 3.11 last night, the
autolearn=yes|no|failed always shows up as failed (on all messages).
 
Did I miss something?
 
As well, the headers added by SA (and me [through SA] for MsgID) are now
showing at the top of the headers from the original message as opposed
to near (or at) the bottom (on all messages)..
 
The upgrade seemed to work fine (previous version was 3.02)..  all tests
came back good...  Spam tagging still works great.  The following
headers are from a mail from this list.

I used the InstallingOnWindows WIKI as a guide for the upgrade.

I am using SA 3.11 running on W2K/Exchange 2000 via a PerlScript tied
into Exchange's SMTP engine.

Steven
 
----
 
Microsoft Mail Internet Headers Version 2.0
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on 
 xxxxxxx.xxxxxxx.xxx
X-Spam-MsgId: 1142265031.319183
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 required=5.0
tests=AWL=-1.200,BAYES_00=-2.599,
 RCVD_NUMERIC_HELO=1.5,STOCK_ALERT=2.2,UPPERCASE_25_50=0 autolearn=no 
 version=3.1.1
thread-index: AcZGtdsYoUOdErI8Rl6JuDuKQc06bA==
Received: from mail.apache.org ([209.237.227.199]) by
xxxxxxx.xxxxxxxxxx.xxx with Microsoft SMTPSVC(5.0.2195.6713); Mon, 13
Mar 2006 08:50:30 -0700
Received: (qmail 86421 invoked by uid 500); 13 Mar 2006 15:50:20 -0000
Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
List-Help: <ma...@spamassassin.apache.org>
List-Unsubscribe: <ma...@spamassassin.apache.org>
List-Post: <ma...@spamassassin.apache.org>
List-Id: <users.spamassassin.apache.org>
Content-Class: urn:content-classes:message
Delivered-To: mailing list users@spamassassin.apache.org
Importance: normal
Priority: normal
Received: (qmail 86412 invoked by uid 99); 13 Mar 2006 15:50:20 -0000
Received: from xxxxxxx.xxxxxxx.org (HELO xxxxx.xxxxxxxxx.org)
(nnn.nnn.nnn.nn)    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Mar
2006 07:50:20 -0800
X-ASF-Spam-Status: No, hits=3.6
required=10.0tests=FORGED_HOTMAIL_RCVD2,RCVD_NUMERIC_HELO,SPF_HELO_PASS,
SPF_PASS,STOCK_ALERT,UPPERCASE_25_50
Received-SPF: pass (xxxxxx.xxxxxxxx.org: domain of
xxxxxxxxxxxxxx@xxxxxxxxx designates nn.nn.nnn.n as permitted sender)
Received: from [nn.nn.nnn.n] (HELO xxxx.xxxxx.org) (nn.nn.nnn.n)    by
apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Mar 2006 07:50:18 -0800
Received: from list by xxxxx.xxxxxxx.org with local (Exim 4.43) id
1FIpHi-0007S0-07 for users@spamassassin.apache.org; Mon, 13 Mar 2006
16:48:40 +0100
Received: from 15.198.28.205 ([nn.nnn.nn.nnn])        by main.gmane.org
with esmtp (Gmexim 0.1 (Debian))        id 1AlnuQ-0007hv-00        for
<us...@spamassassin.apache.org>; Mon, 13 Mar 2006 16:48:37 +0100
Received: from xxxxxxxxxxxx by nn.nnn.nnn.nnn with local (Gmexim 0.1
(Debian))        id 1AlnuQ-0007hv-00        for
<us...@spamassassin.apache.org>; Mon, 13 Mar 2006 16:48:37 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: <us...@spamassassin.apache.org>
From: "xxxxxxxxx xxxxxxxxxxxx" <xx...@xxxxxxx>
Subject:  Re: encoded spam that got thru
Date:  Mon, 13 Mar 2006 16:47:23 +0100
Lines: 81
Message-ID: <xx...@xxxxxxxxxxxxxxxx.org>
References:  <xx...@xxxxxxxxxxxx.org>
X-Complaints-To: xxxxxxx@xxxxxxxxxx.org
X-Gmane-NNTP-Posting-Host: 15.198.28.205
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
X-RFC2646: Format=Flowed; Original
Sender: "news" <xx...@xxxxxxxxxxxx.org>
X-Virus-Checked: Checked by ClamAV on apache.org
Return-Path:
<us...@spamassassin.apache.org>
X-OriginalArrivalTime: 13 Mar 2006 15:50:30.0389 (UTC)
FILETIME=[DB004250:01C646B5]
 

 

Re: autolearn=failed ---- after upgrade to 3.11

[Matt Kettler <mk...@evi-inc.com>]

Steven Manross wrote:
> X-Spam-Status: No, score=-2.6 required=5.0
> tests=AWL=0.023,BAYES_00=-2.599 
>  autolearn=failed version=3.1.1
>  
> It seems that since upgrading to 3.11 last night, the
> autolearn=yes|no|failed always shows up as failed (on all messages).
>  
> Did I miss something?

Generally "Failed" means that SA somehow can't access the bayes database to
write to it.

Have you tried sa-learn --sync and then sa-learn --dump magic to see if those
tools find the bayes database correctly?

What about spamassassin --lint to check for config-file errors?