On Fri, 26 Jan 2007 13:54:03 +0000, Ben Wylie
<[EMAIL PROTECTED]> wrote:

>I recommend the KAM rules list which can be found here:
>http://www.peregrinehw.com/downloads/SpamAssassin/contrib/KAM.cf
>This catches the drugs names in these emails.
>
>Cheers,
>Ben
>
>Nigel Frankcom wrote:
>> On Thu, 25 Jan 2007 20:16:42 -0500, Matt Kettler
>> <[EMAIL PROTECTED]> wrote:
>> 
>>> Nigel Frankcom wrote:
>>>> Debug results are available on: 
>>>> http://dev.blue-canoe.net/spam/spam01.txt
>>>> http://dev.blue-canoe.net/spam/debug1.txt
>>>>
>>>> http://dev.blue-canoe.net/spam/spam02.txt
>>>> http://dev.blue-canoe.net/spam/debug2.txt
>>>>
>>>> http://dev.blue-canoe.net/spam/spam03.txt
>>>> http://dev.blue-canoe.net/spam/debug3.txt
>>>>
>>>> http://dev.blue-canoe.net/spam/spam04.txt
>>>> http://dev.blue-canoe.net/spam/debug4.txt
>>>>
>>>> Make of them what you will, I think I need more beer before that lot
>>>> makes much sense :-D
>>>>
>>>> Kind regards
>>>>
>>>> Nigel
>>>>   
>>> Sorry Nigel. Andy steered you a bit wrong and those debug outputs are
>>> useless.. You need "-D bayes" not just "-D".
>>>
>>> Try it again with:
>>>
>>> spamassassin -D bayes < message1 2> debug1.txt
>>>
>>> Instead of
>>> spamassassin -D -t < message1 2> debug1.txt
>>>
>> 
>> Files redone... a little more informative this time round :-D
>> 
>>  http://dev.blue-canoe.net/spam/spam01.txt
>>  http://dev.blue-canoe.net/spam/debug1.txt
>> 
>>  http://dev.blue-canoe.net/spam/spam02.txt
>>  http://dev.blue-canoe.net/spam/debug2.txt
>> 
>>  http://dev.blue-canoe.net/spam/spam03.txt
>>  http://dev.blue-canoe.net/spam/debug3.txt
>> 
>>  http://dev.blue-canoe.net/spam/spam04.txt
>>  http://dev.blue-canoe.net/spam/debug4.txt
>> 

Thanks Ben,

Training seems to have resolved the short term problem, I'll pull a
copy of that rule and if the problem strikes again I'll run it in.

Kind regards

Nigel

Reply via email to