You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "Gary W. Smith" <ga...@primeexalia.com> on 2004/11/08 03:56:40 UTC
multi.surbl.org confusion
I've noticed while looking into some items for Sa 3.X that
multi.surbl.org takes a bitmask flag. I've noticed that the sample
contains bitmask 64 for JP as the source.
Does this mean that it only hit's JP?
The documentation is a little short on the exact usage of these. I'm
just curious before implementing this and removing the other three that
I have in place (sc, ws and ob).
Gary
Re: multi.surbl.org confusion
Posted by Jeff Chan <je...@surbl.org>.
On Sunday, November 7, 2004, 6:56:40 PM, Gary Smith wrote:
> I've noticed while looking into some items for Sa 3.X that
> multi.surbl.org takes a bitmask flag. I've noticed that the sample
> contains bitmask 64 for JP as the source.
> Does this mean that it only hit's JP?
> The documentation is a little short on the exact usage of these. I'm
> just curious before implementing this and removing the other three that
> I have in place (sc, ws and ob).
> Gary
Each bit position represents a different list. If the bit in the
64 position is set then that means a record is on the JP list.
In rules, the 64 bit means to use the JP data. The other lists
use different bits. SC uses the 2 bit, etc. If a given domain
is on both JP and SC and no others then it gets a value of 64 + 2
or 66. This is similar to how the OPM RBL works:
http://opm.blitzed.org/info
We recommend using SC, WS, OB, JP, etc. Generally speaking
you'll detect more spam if you don't take any out.
Jeff C.
--
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/