You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "Rose, Bobby" <br...@med.wayne.edu> on 2008/12/01 17:35:16 UTC
RE: New version of iXhash plugin available
Has anyone who switched to 1.5 of iXHash received any hits? I haven't seen any since switching. One thing that I've noticed is if I pass the same message thru SA using the old iXhash, the hash is computed via Method 1 and 2, if I use 1.5 of iXhash, it's only computed using method 2
On one box I have SA with 1.5 and another I have SA and 1.01 and the box with 1.01 version has tripped about 5 messages since switching it back.
-----Original Message-----
From: Dirk Bonengel [mailto:dirk.bonengel@gmx.de]
Sent: Saturday, November 29, 2008 8:55 AM
To: Arthur Dent; users@spamassassin.apache.org
Subject: Re: New version of iXhash plugin available
Arthur Dent schrieb:
[
CUT]
> Hmmm.. OK I tried another one. This one actually triggered iXhash when I
> got
> it originally. You can see the original mail (including headers showing
> iXhash
> report) here:
>
> http://pastebin.ca/1269211
>
> Running it through now it doesn't generate the error that the
> other message did, BUT... it doesn't trigger iXhash anymore!
>
>
That mail's somewhat older, isn't it? So it may simple have been removed
from Ctyme's (and the other's) data. It doesn't trigger here as well.
> Here's the debug output:
>
> [mark@mydomain SpamSamples]$ spamassassin -D IXHASH < watchtv.txt
> [15993] dbg: IXHASH: Using iXhash plugin
> [15993] dbg: IXHASH: IxHash querying ctyme.ixhash.net
> [15993] dbg: IXHASH: Hash value #1 not computed, requirements not met
> [15993] dbg: IXHASH: Computed hash-value
> e82057ad6c568847f62357498f0dd4db via
> method 2, using perl exclusively
> [15993] dbg: IXHASH: Now checking
> e82057ad6c568847f62357498f0dd4db.ctyme.ixhash.net
> [15993] dbg: IXHASH: Hash value #3 not computed, requirements not met
> [15993] dbg: IXHASH: IxHash querying hosteurope.ixhash.net
> [15993] dbg: IXHASH: Hash value #1 not computed, requirements not met
> [15993] dbg: IXHASH: Now checking
> e82057ad6c568847f62357498f0dd4db.hosteurope.ixhash.net
> [15993] dbg: IXHASH: Hash value for method #2 found in metadata,
> re-using that
> one
> [15993] dbg: IXHASH: Now checking
> e82057ad6c568847f62357498f0dd4db.hosteurope.ixhash.net
> [15993] dbg: IXHASH: Hash value #3 not computed, requirements not met
> [15993] dbg: IXHASH: IxHash querying generic.ixhash.net
> [15993] dbg: IXHASH: Hash value #1 not computed, requirements not met
> [15993] dbg: IXHASH: Now checking
> e82057ad6c568847f62357498f0dd4db.generic.ixhash.net
> [15993] dbg: IXHASH: Hash value for method #2 found in metadata,
> re-using that
> one
> [15993] dbg: IXHASH: Now checking
> e82057ad6c568847f62357498f0dd4db.generic.ixhash.net
> [15993] dbg: IXHASH: Hash value #3 not computed, requirements not met
> [15993] dbg: IXHASH: IxHash querying ix.dnsbl.manitu.net
> [15993] dbg: IXHASH: Hash value #1 not computed, requirements not met
> [15993] dbg: IXHASH: Now checking
> e82057ad6c568847f62357498f0dd4db.ix.dnsbl.manitu.net
> [15993] dbg: IXHASH: Hash value for method #2 found in metadata,
> re-using that
> one
> [15993] dbg: IXHASH: Now checking
> e82057ad6c568847f62357498f0dd4db.ix.dnsbl.manitu.net
> [15993] dbg: IXHASH: Hash value #3 not computed, requirements not met
> From ... [Headers and spam report removed]....
>
>
This all looks OK to me.
Just keep an eye to your spam flow and see if you get any hits (that
would most likely hit @ ix.dnsbl.manitu.net - Heise's list would be the
biggest one)
Re: New version of iXhash plugin available
Posted by Bill Landry <bi...@inetmsg.com>.
Rose, Bobby wrote:
> Has anyone who switched to 1.5 of iXHash received any hits? I haven't seen any since switching. One thing that I've noticed is if I pass the same message thru SA using the old iXhash, the hash is computed via Method 1 and 2, if I use 1.5 of iXhash, it's only computed using method 2
>
> On one box I have SA with 1.5 and another I have SA and 1.01 and the box with 1.01 version has tripped about 5 messages since switching it back.
I found the same to be true here (the new version of iXhash detects
nothing) and have reverted back to the previous version.
Bill
Re: New version of iXhash plugin available
Posted by Marc Perkel <ma...@perkel.com>.
I noticed this morning that I also had 0 ixhash hits. Is something wrong?
Rose, Bobby wrote:
> Has anyone who switched to 1.5 of iXHash received any hits? I haven't seen any since switching. One thing that I've noticed is if I pass the same message thru SA using the old iXhash, the hash is computed via Method 1 and 2, if I use 1.5 of iXhash, it's only computed using method 2
>
> On one box I have SA with 1.5 and another I have SA and 1.01 and the box with 1.01 version has tripped about 5 messages since switching it back.
>
> -----Original Message-----
> From: Dirk Bonengel [mailto:dirk.bonengel@gmx.de]
> Sent: Saturday, November 29, 2008 8:55 AM
> To: Arthur Dent; users@spamassassin.apache.org
> Subject: Re: New version of iXhash plugin available
>
> Arthur Dent schrieb:
> [
> CUT]
>
>> Hmmm.. OK I tried another one. This one actually triggered iXhash when I
>> got
>> it originally. You can see the original mail (including headers showing
>> iXhash
>> report) here:
>>
>> http://pastebin.ca/1269211
>>
>> Running it through now it doesn't generate the error that the
>> other message did, BUT... it doesn't trigger iXhash anymore!
>>
>>
>>
> That mail's somewhat older, isn't it? So it may simple have been removed
> from Ctyme's (and the other's) data. It doesn't trigger here as well.
>
>
>> Here's the debug output:
>>
>> [mark@mydomain SpamSamples]$ spamassassin -D IXHASH < watchtv.txt
>> [15993] dbg: IXHASH: Using iXhash plugin
>> [15993] dbg: IXHASH: IxHash querying ctyme.ixhash.net
>> [15993] dbg: IXHASH: Hash value #1 not computed, requirements not met
>> [15993] dbg: IXHASH: Computed hash-value
>> e82057ad6c568847f62357498f0dd4db via
>> method 2, using perl exclusively
>> [15993] dbg: IXHASH: Now checking
>> e82057ad6c568847f62357498f0dd4db.ctyme.ixhash.net
>> [15993] dbg: IXHASH: Hash value #3 not computed, requirements not met
>> [15993] dbg: IXHASH: IxHash querying hosteurope.ixhash.net
>> [15993] dbg: IXHASH: Hash value #1 not computed, requirements not met
>> [15993] dbg: IXHASH: Now checking
>> e82057ad6c568847f62357498f0dd4db.hosteurope.ixhash.net
>> [15993] dbg: IXHASH: Hash value for method #2 found in metadata,
>> re-using that
>> one
>> [15993] dbg: IXHASH: Now checking
>> e82057ad6c568847f62357498f0dd4db.hosteurope.ixhash.net
>> [15993] dbg: IXHASH: Hash value #3 not computed, requirements not met
>> [15993] dbg: IXHASH: IxHash querying generic.ixhash.net
>> [15993] dbg: IXHASH: Hash value #1 not computed, requirements not met
>> [15993] dbg: IXHASH: Now checking
>> e82057ad6c568847f62357498f0dd4db.generic.ixhash.net
>> [15993] dbg: IXHASH: Hash value for method #2 found in metadata,
>> re-using that
>> one
>> [15993] dbg: IXHASH: Now checking
>> e82057ad6c568847f62357498f0dd4db.generic.ixhash.net
>> [15993] dbg: IXHASH: Hash value #3 not computed, requirements not met
>> [15993] dbg: IXHASH: IxHash querying ix.dnsbl.manitu.net
>> [15993] dbg: IXHASH: Hash value #1 not computed, requirements not met
>> [15993] dbg: IXHASH: Now checking
>> e82057ad6c568847f62357498f0dd4db.ix.dnsbl.manitu.net
>> [15993] dbg: IXHASH: Hash value for method #2 found in metadata,
>> re-using that
>> one
>> [15993] dbg: IXHASH: Now checking
>> e82057ad6c568847f62357498f0dd4db.ix.dnsbl.manitu.net
>> [15993] dbg: IXHASH: Hash value #3 not computed, requirements not met
>> From ... [Headers and spam report removed]....
>>
>>
>>
> This all looks OK to me.
> Just keep an eye to your spam flow and see if you get any hits (that
> would most likely hit @ ix.dnsbl.manitu.net - Heise's list would be the
> biggest one)
>
>
>
>