OUCH I'm farther behind then I thought!! I have 2 lists, one 416 domains,
the other 347 domains. All to be checked. And that's not all!!!! So if two
people would each take a list, I could work on the other 500+.
HELP!!!!
:)
--Chris
>-----Original Message-----
>From: Raymond Dijkxhoorn [mailto:raymond@prolocation.net]
>Sent: Monday, August 02, 2004 2:23 PM
>To: SURBL Discussion list
>Subject: RE: [SURBL-Discuss] FP's in ws.surbl.org
>
>
>Hi Chris,
>
>> >just wondering if anyone else has reported FPs for
>ws.surbl.org, if so
>> >how long did the removal take?
>> >
>> >While I'm here, can anyone else confirm that spam submissions to
>> >http://www.rulesemporium.com/cgi-bin/uribl.cgi?report=1 get read.
>
>> They ABSOLUTELY get read. Usually quite quickly. However
>they all need to
>> be hand checked. Currently I'm 236 submissions behind for
>just that. About
>> 400 submissions behind on another. Soooo much to do!
>
>If there is a way to help you on this, let us know.
>
>Bye,
>Raymond.
>_______________________________________________
>Discuss mailing list
>Discuss(a)lists.surbl.org
>http://lists.surbl.org/mailman/listinfo/discuss
>
>-----Original Message-----
>From: Jeff Chan [mailto:jeffc@surbl.org]
>Sent: Friday, July 30, 2004 3:32 AM
>To: SURBL Discussion list
>Subject: Re: [SURBL-Discuss] Please beta test ms.surbl.org - data from
>MailSecurity
>
>
>On Friday, July 30, 2004, 12:05:52 AM, Raymond Dijkxhoorn wrote:
>>> This released list has been developed from actual spam
>recieved since
>>> the SURBL effort started. I don't doubt there are a lot of
>double ups
>>> with ws.surbl.org however.
>>>
>>> > As a seperate list i would so far say, uhm, not really
>worth the efford,
>>> > as a extra list of domains for WS, i think its worth it.
>>>
>>> Sure - kinda what I was originally intending anyway :)
>
>> Sounds like a plan! :)
>
>>> The list is developed from messages which slip through existing
>>> SURBL's and other custom SA rulesets - addmittedly less and less are
>>> getting through, but we do keep on top of it. It is
>current, but may
>>> also be a different sampling of messages to those you see.
>>>
>>> Expiry of listings is something we're still working on, but are a
>>> little loathe to do because we've recently noticed a spate of
>>> "recycled" domain names.
>
>> Ok, great. It would be a nice addition to WS i think... Anyone ?
>
>Sounds good to me. Anyone else?
>
>If so, Chris please consider pulling these into WS.
>
>Jeff C.
1) Send me the -different- domains that aren't already listed and I will
blast them right into WS. I'll do it in such a way I can track FPs back to
them.
2) How will we handle new additions? Submit them to who?
3) When will we have an SURBL contributors BBQ? Soon I hope, I'm hungry!
--Chris
I'm updating the SRUBL Lists about about ws, and may have lost
track of all the data sources now going into it:
http://www.surbl.org/lists.html#ws
> ws.surbl.org - sa-blacklist and other domains
> ws.surbl.org has entries from three SpamAssassin rulesets: Bill
> Stearns' sa-blacklist, BigEvil.cf from Chris Santerre and his
> SARE cohorts, and Paul Barbeau's MidEvil.cf. ws.surbl.org also
> has entries from additional spam URI domain lists such as
> MailSecurity's formely proprietary SURBL lists, data from Joe
> Wein's jwSpamSpy Windows POP mail spam-filtering agent, plus
> some other manual lists, mostly maintained by Chris.
Chris, Bill and Raymond, am I forgetting any that we should be
crediting publically?
Jeff C.
>-----Original Message-----
>From: Jeff Chan [mailto:jeffc@surbl.org]
>Sent: Monday, August 02, 2004 6:00 AM
>To: SURBL Discuss
>Subject: [SURBL-Discuss] What data sources are in ws now? :-)
>
>
>I'm updating the SRUBL Lists about about ws, and may have lost
>track of all the data sources now going into it:
>
> http://www.surbl.org/lists.html#ws
>
>> ws.surbl.org - sa-blacklist and other domains
>
>> ws.surbl.org has entries from three SpamAssassin rulesets: Bill
>> Stearns' sa-blacklist, BigEvil.cf from Chris Santerre and his
>> SARE cohorts, and Paul Barbeau's MidEvil.cf. ws.surbl.org also
>> has entries from additional spam URI domain lists such as
>> MailSecurity's formely proprietary SURBL lists, data from Joe
>> Wein's jwSpamSpy Windows POP mail spam-filtering agent, plus
>> some other manual lists, mostly maintained by Chris.
>
>Chris, Bill and Raymond, am I forgetting any that we should be
>crediting publically?
>
>Jeff C.
Yeah that is good. I'm still getting new 6dos (ds) submissions. I hope to
check those today. I would love to send someone a few 100 to check, if
anyone volunteers to split this with me. I'm falling behind due to real work
bogging me down. :(
--Chris
I'm making a flyer to distribute at the CEAS spam conference next
week and would appreciate any feedback on it please:
http://www.surbl.org/flyer.html
The audience should be mostly academics and some industry and
Internet types who work on fighting spam. The conference
appears to be mostly about technical and some legal theories
for identifying and fighting spam. Here's the program:
http://www.ceas.cc/acceptedpapers.htm
Please send me your comments, improvements, suggestions,
typos, errors, grammar, etc.
Jeff C.
Thanks to Raymond's efforts a couple new data sources are going
into ws.surbl.org:
1. MailSecurity's own SURBL lists of about 2200 entries
found in spam.
2. Joe Wein's list from his spam filter for pop mailboxes
Windows client application jwSpamSpy:
http://www.joewein.de/sw/jwSpamSpy/
Before I announce this more widely I thought I would ask if
anyone else is noticing improved spam detection and/or any
changes in FPs. Adding these two seems to have boosted
Raymond's spam detection results with ws.surbl.org above
sbl-xbl.spamhaus.org:
> the hitrate on my own setup went up on WS with around 6%.
>
> Here's my todays top 10:
>
> SpamAssassin tag hits: (top 100)
> #1 115259 BAYES_99
> #2 89993 WS_URI_RBL
> #3 88006 RCVD_IN_SBL+XBL
> #4 85157 HTML_MESSAGE
> #5 81296 RCVD_IN_BL_SPAMCOP_NET
> #6 80990 OUTBLAZE_URI_RBL
> #7 67765 RCVD_IN_SORBS
> #8 65982 SPAMCOP_URI_RBL
> #9 61878 ABUSEBUTLER_URI_RBL
> #10 53390 RCVD_IN_DSBL
We're particularly concerned about FPs, so please report any
that you find. Posting them to this discussion list is fine
IMO. Every FP is very important to eliminate and understand
and correct the source of.
Jeff C.