This is a reminder that we will be adding JP as a new list within multi.surbl.org, as described in the previous announcement:
http://lists.surbl.org/pipermail/announce/2004-September/000077.html on Monday September 27th. JP will have the bitmask value of 64, which means about half of the WS records will have results that increase by 64. We'll probably make the change around close of business U.S. East Coast time or around 22:00 UTC/GMT. For now, JP records will continue to be included in WS, but when SpamAssassin 3.1 gets released, the JP data will come out of WS and these two will become separate lists within multi. Please update your programs accordingly. SpamAssassin users won't need to make any changes to keep using WS, but should probably add JP to their configurations now so that they will be ready for the future change, and also to gain the significant benefits of the separate JP list now: http://www.surbl.org/quickstart.html __ jp - jwSpamSpy + Prolocation data source Joe Wein's jwSpamSpy program is used both by Joe's own systems and also Raymond Dijkxhoorn and his colleagues at Prolocation to process more than 300,000 likely spams per day. The resulting list has a very good spam detection rate around 80% and a very low false positive rate below 0.02%. This data is only available in the combined list multi.surbl.org. An SA 2.63 and 2.64 rule and score using SpamCopURI 0.22 or later looks like this: uri JP_URI_RBL eval:check_spamcop_uri_rbl('multi.surbl.org','127.0.0.0+64') describe JP_URI_RBL URI's domain appears in JP at http://www.surbl.org/lists.html tflags JP_URI_RBL net score JP_URI_RBL 4.0 An SA 3.0 rule and score using URIBL's urirhssub looks like this: urirhssub URIBL_JP_SURBL multi.surbl.org. A 64 header URIBL_JP_SURBL eval:check_uridnsbl('URIBL_JP_SURBL') describe URIBL_JP_SURBL Contains a URL listed in JP at http://www.surbl.org/lists.html tflags URIBL_JP_SURBL net score URIBL_JP_SURBL 4.0 __ JP has approximately the same spam detection and false positive rates as OB and should probably be scored accordingly. The data are not the same however since JP uses different data sources and Joe Wein's processing algorithms and inclusion policies. Jeff C.
