Hi Kevin McGrail,

    Was there any response on the dev list about this?  I am not
subscribed to it.

I notice that RCVD_IN_MSPIKE_WL is listed in the updates:

# find -exec grep MSPIKE_WL \{\} \; -ls
meta RCVD_IN_MSPIKE_WL        RCVD_IN_MSPIKE_H5 || RCVD_IN_MSPIKE_H4 ||
RCVD_IN_MSPIKE_H3
describe RCVD_IN_MSPIKE_WL    Mailspike good senders
tflags RCVD_IN_MSPIKE_WL    nice net
131305    4 -rw-r--r--   1 root     root         2609 Feb 16 06:53
./3.003001/updates_spamassassin_org/20_mailspike.cf
score RCVD_IN_MSPIKE_WL                     0.001 -0.010 0.001 -0.010
131619   12 -rw-r--r--   1 root     root        11362 Feb 16 06:53
./3.003001/updates_spamassassin_org/72_scores.cf
  score RCVD_IN_MSPIKE_WL      -0.01
131604   48 -rw-r--r--   1 root     root        48281 Feb 16 06:53
./3.003001/updates_spamassassin_org/50_scores.cf


... but spamassassin throws message back:
Feb 16 10:05:01.084 [10573] warn: config: SpamAssassin failed to parse
line, no value provided for "body", skipping: body
Feb 16 10:05:01.289 [10573] dbg: config: warning: score set for
non-existent rule *RCVD_IN_MSPIKE_WL*


I did not change it ;)
# grep MSPIKE_WL /etc/spamassassin/local.cf
# echo $?
1
#

The rules are there in
./3.003001/updates_spamassassin_org/20_mailspike.cf
./3.003001/updates_spamassassin_org/72_scores.cf
./3.003001/updates_spamassassin_org/50_scores.cf

I can see scrore for example:
score RCVD_IN_MSPIKE_L4      0.001 0.001 0.001 0.001
score RCVD_IN_MSPIKE_L4      1.7


For the time being I want to work out whether this is a error on the
server, or came via an update.




On 03/02/12 20:39, Kevin A. McGrail wrote:
> Can anyone else test with 3.3.1 to see if we are publishing something
> that is breaking on 3.3.1?  I would guess it might have to do with the
> version eval stuff we've been trying to push out.
>
> On 2/3/2012 2:35 PM, Simon Loewenthal wrote:
>>  
>> Yep, fails on standard rules.
>>
>> ( Excuse the slightly messy copy and paste, but I am using ConnectBot on a 
>> smartphone whilst travelling on train.  )
>>
>> # spamassasin -C `pwd` --lint
>> eb  3 20:27:53.349 [19929] warn: config: SpamAssassin failed to parse line, 
>> no
>> value provided for "body", skipping: body 
>> eb  3 20:27:56.862 [19929] warn: lint: 1 issues detected, please rerun with 
>> debug enabled for more information
>>
>>
>> --
>> Dogs are tough. 
>> I've been interrogating this one for hours and he still won't tell me who's 
>> a good boy. 
>>   simon@klunky / .co.uk / .org
>>
>> "Kevin A. McGrail" <kmcgr...@pccc.com> wrote:
>>
>>> On 2/3/2012 2:13 PM, Simon Loewenthal wrote:
>>>> Version 3.3.1 on Debian Squeeze
>>> Are the standard rules throwing any errors with lint?
>>>
>>> For example, spamassassin -C 
>>> /var/lib/spamassassin/3.003001/updates_spamassassin_org --lint
>>>
>>> regards,
>>> KAM
>
>
> -- 
> *Kevin A. McGrail*
> President
>
> Peregrine Computer Consultants Corporation
> 3927 Old Lee Highway, Suite 102-C
> Fairfax, VA 22030-2422
>
> http://www.pccc.com/
>
> 703-359-9700 x50 / 800-823-8402 (Toll-Free)
> 703-359-8451 (fax)
> kmcgr...@pccc.com <mailto:kmcgr...@pccc.com>
>
>


-- 
             PGP is optional: 4BA78604
             simon @ klunky  .     org
             simon @ klunky  .   co.uk
        I won't accept your confidentiality
        agreement, and your Emails are kept.
                       ~Ö¿Ö~

Reply via email to