>-----Original Message-----
>From: Alex Broens [mailto:surbl@alexb.ch]
>Sent: Thursday, September 30, 2004 3:35 PM
>To: SURBL Discussion list
>Subject: Re: [SURBL-Discuss] FP: smithbarney.com
>
>
>Rob McEwen wrote:
>> FP: smithbarney.com
>>
>> (followup comments)
>>
>> I was trying to think... how did this one get on there? It
>seems like it
>> just barely missed the various institutional-based whitelists.
>>
>> I did a search of this on alexa.com and their site is ranked
>just inside the
>> top 20,000 web sites.
>>
>> SEE:
>> http://www.alexa.com/data/details/?url=smithbarney.com
>>
>> Then I thought, wouldn't it be interesting to run the top
>20,000 Alexa sites
>> against SURBL... double-check whichever of these are
>currently getting
>> "caught" by SURBL. Remove any which should be removed, (I'm
>sure at least a
>> few would remain in SURBL??). Then whitelist all of the 20k
>that haven't
>> been specifically determined as needing to remain in SURBL.
>
>Guys......
>SURBL is used by the world, not only the US
>
>Alexa.com doesn't have the best of reputations on this side of
>the pond.
>
>Their Privacy Policy is dubious:
>--------------
>ALEXA'S TOOLBAR SERVICE COLLECTS AND STORES INFORMATION ABOUT THE WEB
>PAGES YOU VIEW, THE DATA YOU ENTER IN ONLINE FORMS AND SEARCH FIELDS,
>AND, WITH VERSIONS 5.0 AND HIGHER, THE PRODUCTS YOU PURCHASE ONLINE
>WHILE USING THE TOOLBAR SERVICE. ALTHOUGH ALEXA DOES NOT ATTEMPT TO
>ANALYZE WEB USAGE DATA TO DETERMINE THE IDENTITY OF ANY ALEXA
>USER, SOME
>INFORMATION COLLECTED BY THE TOOLBAR SERVICE IS PERSONALLY
>IDENTIFIABLE.
>ALEXA AGGREGATES AND ANALYZES THE INFORMATION IT COLLECTS TO
>IMPROVE ITS
>SERVICE AND TO PREPARE REPORTS ABOUT AGGREGATE WEB USAGE AND SHOPPING
>HABITS.
>---------------
>more @ http://pages.alexa.com/help/privacy.html
>
>
>Pls don't force whitelisting more than necessary, or put these domains
>in your site's whitelist but spare us whitelisting their associates as
>much as possible
>
>Alex
I agree. smithbarney should NEVER have been added! Whitelist them. Flogg the
person that added them.
--Chris (*brakes out the ridding crop*)
RE: Most often "hit" SURBL domains
>From time to time, ideas float around about how we can take some pressure
off of the SURBL name servers. Recently, most commonly queried URIs that are
NOT (and should not) be blocked were mentioned in the hopes that people
would "whitelist" these locally so their mail servers would stop querying
SURBL for stuff like microsoft.com, ebay.com, etc.
I have a similar idea. Would it be possible to have a running list of the
top 20 (or so... 50? 100?) most often queried URI's that are blocked by
SURBL (and which should be blocked)? This way, we could take additional
pressure off SURBL DNS servers by blacklisting these domains locally BEFORE
doing SURBL checking on such messages?
I have a feeling that this has already been requested and implemented??
Rob McEwen
I remember there was some excitement that blogers had code to check links
posted against SURBL. Is that still being used? I figured that would be
bigger news.
Chris Santerre
System Admin and SARE Ninja
http://www.rulesemporium.comhttp://www.surbl.org
'It is not the strongest of the species that survives,
not the most intelligent, but the one most responsive to change.'
Charles Darwin
>-----Original Message-----
>From: Rob McEwen [mailto:rob@powerviewsystems.com]
>Sent: Wednesday, September 29, 2004 7:42 PM
>To: 'SURBL Discussion list'
>Subject: [SURBL-Discuss] Most often "hit" SURBL domains
>
>
>RE: Most often "hit" SURBL domains
>
>>From time to time, ideas float around about how we can take
>some pressure
>off of the SURBL name servers. Recently, most commonly queried
>URIs that are
>NOT (and should not) be blocked were mentioned in the hopes that people
>would "whitelist" these locally so their mail servers would
>stop querying
>SURBL for stuff like microsoft.com, ebay.com, etc.
>
>I have a similar idea. Would it be possible to have a running
>list of the
>top 20 (or so... 50? 100?) most often queried URI's that are blocked by
>SURBL (and which should be blocked)? This way, we could take additional
>pressure off SURBL DNS servers by blacklisting these domains
>locally BEFORE
>doing SURBL checking on such messages?
>
>I have a feeling that this has already been requested and implemented??
>
Could this be done in a host file?
0.0.0.0 aol.com.ws.surbl.org
Would something like that work?
--Chris
>-----Original Message-----
>From: David Hooton [mailto:david.hooton@gmail.com]
>Sent: Thursday, September 30, 2004 9:23 AM
>To: Jeff Chan; SURBL Discussion list
>Subject: Re: [SURBL-Discuss] Fwd: quickinspirations.com
>
>
>On Wed, 29 Sep 2004 16:54:22 -0700, Jeff Chan <jeffc(a)surbl.org> wrote:
>> This was the original report send to the whitelist(a)surbl.org
>> address. Note that it included no examples, no explanation, no
>> reasons, etc.
>>
>> That's why it's nice include some of those, eh?
>>
>> Jeff C.
>> __
>>
>> This is a forwarded message
>> From: Bitz <bitoy(a)lawin.pinoy.org>
>> To: whitelist(a)surbl.org
>> Date: Friday, July 30, 2004, 5:17:43 PM
>> Subject: quickinspirations.com
>>
>> ===8<==============Original message text===============
>> quickinspirations.com
>>
>> ===8<===========End of original message text===========
>
>Perhaps people who request domains to be delisted but provide no
>evidence should just be permanently lists? :p
>
LOL. Should we at least rethink this kind of domain? Some people are going
to scream "Legit!" because they don't know they were fooled.
I'm not asking for this domain to be changed right now. I'm asking more for
people to start thinking about these kind of legit looking signup spams.
Keep the seed in the back of your mind, as we may see more of this.
--Chris
This was the original report send to the whitelist(a)surbl.org
address. Note that it included no examples, no explanation, no
reasons, etc.
That's why it's nice include some of those, eh?
Jeff C.
__
This is a forwarded message
From: Bitz <bitoy(a)lawin.pinoy.org>
To: whitelist(a)surbl.org
Date: Friday, July 30, 2004, 5:17:43 PM
Subject: quickinspirations.com
===8<==============Original message text===============
quickinspirations.com
===8<===========End of original message text===========
--
Jeff Chan
mailto:whitelist@surbl.org
http://www.surbl.org/
At 16:14 2004-09-29 -0400, Chris Santerre wrote:
>Did you just create a new term?
>
>"Fisuf Spam"
:-)
>Works for me! I think I had a "discussion" about this domain with Jeff
>before. Which is why I rang a bell. I think this may be one of the ones that
>started the whole UC debate.
>
>Hmmm.... could more Fisuf Spam be around the corner?
In my opinion - apparently (according to some definitions) legitimate
emails that people have actually signed up for, that are obviously *only*
sent out by known spammers to people tricked into entering their adress, or
someone elses on a web site, that have *no* real purpose except to send
spam - should be classified as spam, *not ham*. Even if people have signed
up for the spam.
Patrik
While I always read how reliable OB should be, of the few WL requests
I've triggered, all except 1 were from OB.
These were pretty ugly ones indeed, an Adobe child site, a Genuine
abused Webmail site, etc, etc.
juts wondering....
Alex
This is a request for folks to please test the MailPolice
fraud list and jp.surbl.org:
MailPolice Fraud list with SpamCopURI:
uri MP_URI_RBL
eval:check_spamcop_uri_rbl('fraud.rhs.mailpolice.com','127.0.0.2')
describe MP_URI_RBL URI's domain appears in MailPolice fraud list
tflags MP_URI_RBL net
score MP_URI_RBL 3.0
And for SA 3.0 with the URIDNSBL plug-in:
urirhsbl URIBL_MP fraud.rhs.mailpolice.com. A
header URIBL_MP eval:check_uridnsbl('URIBL_MP')
describe URIBL_MP URI's domain appears in MailPolice fraud list
tflags URIBL_MP net
score URIBL_MP 3.0
(Note that the above is a separate, external list, so it can't
be used like multi.)
JP SA 2.63 and 2.64 rule and score using SpamCopURI 0.22 or later:
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
JP SA 3.0 rule and score using URIBL's urirhssub:
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
In particular we'd like to hear about any false positives
on either list. If the MailPolice fraud data looks good,
we'll add it to PH, but we need your help in testing it.
You can test these on hand selected test corpora or live
mail, but please try not to melt the MailPolice name
servers. ;-)
Please give these a try and let us know what you find. Note
that you'll probably want to remove the MailPolice fraud list
after testing as a separate list if we add it to PH.
Jeff C.
--
"If it appears in hams, then don't list it."