Initially, when I released spamcopuri I decided to pretty much ignore
whether the TLD was a country code or not. This results in about
twice as many queries as necessary, but guaranteed you would get
hits if the domain was listed.
Now that people are pointing this to other RBL's beside just surbl,
should we continue to do second and third level queries? Or just
the query that we assume to be necessary? My concern is that not
all RBLs will process the domains according to a list such as
http://www.bestregistrar.com/help/ccTLD.htm. I suppose the worst
case scenario is we end up getting a miss when we should be getting
a hit because one side presumes that say TLD .za has a subdomain 'foo',
when the server doesn't. The server side would expect a second level, while
the client would do a third level query (this is why I wanted the wildcard
records). I guess this really isn't that great a consequence considering
the savings and the fact that this shouldn't occur very often.
I will go ahead and make this change if everyone is comfortable with the
known risk.
thanks,
--eric
Got a question.
How is the best way to use all the surbl.org zone with SA?
uri SPAMCOP_URI_RBL
eval:check_spamcop_uri_rbl('sc.surbl.org','127.0.0.2')
describe SPAMCOP_URI_RBL URI's domain appears in spamcop database
at sc.surbl.org
tflags SPAMCOP_URI_RBL net
score SPAMCOP_URI_RBL 3.0
uri SPAMCOP_URI_RBL
eval:check_spamcop_uri_rbl('be.surbl.org','127.0.0.2')
describe SPAMCOP_URI_RBL URI's domain appears in spamcop database
at be.surbl.org
tflags SPAMCOP_URI_RBL net
score SPAMCOP_URI_RBL 3.0
uri SPAMCOP_URI_RBL
eval:check_spamcop_uri_rbl('ws.surbl.org','127.0.0.2')
describe SPAMCOP_URI_RBL URI's domain appears in spamcop database
at ws.surbl.org
tflags SPAMCOP_URI_RBL net
score SPAMCOP_URI_RBL 3.0
Or do I need to change something? I just have it now doing the sc zones,
but would like to have it parse through them all.
Thanks,
--
-Doc
---
MomNDoc Online Consultants
http://www.maddoc.net/
momndoc(a)maddoc.net
> -----Original Message-----
> From: Jeff Chan [mailto:jeffc@surbl.org]
> Sent: Wednesday, April 21, 2004 9:54 AM
> To: Chris Santerre
> Cc: SURBL Discussion list
> Subject: Re: [SURBL-Discuss] BigEvil + MidEvil as SURBL
>
>
> > 2) Where would I send updates? As single domains, or a txt
> list? How would I
> > remove an FP?
>
> In case it's not clear, FPs will come out of be.surbl.org
> automatically when they come out of bigevil.cf and midevil.cf.
>
> If you need to manually whitelist a domain, just send a message
> to us at whitelist at surbl dot org and we'll do that ASAP.
>
> Jeff C.
Now that I see how you are doing this, let me just reiterate....FREAKIN
KEWL!!!
Well then, I see what I have to do with Paul. And This is so so very cool!
--Chris
Just release 0.12 to fix a test some users may have had errors with
during make test. No real need to grab this unless you want a clean make
test.
--eric
Trying to install 0.11 over an existing (and working) 0.10 installation
on a redhat 9 box.
make test gives the following errors (all other tests are ok):
| t/open_redirect....NOK 5# Failed test (t/open_redirect.t at line 43)
| t/open_redirect....ok 7/7# Looks like you failed 1 tests of 7.
| t/open_redirect....dubious
| Test returned status 1 (wstat 256, 0x100)
| DIED. FAILED test 5
| Failed 1/7 tests, 85.71% okay
Any ideas?
John.
--
-- Over 2400 webcams from ski resorts around the world - www.snoweye.com
-- Translate your technical documents and web pages - www.tradoc.fr
> -----Original Message-----
> From: Jeff Chan [mailto:jeffc@surbl.org]
> Sent: Wednesday, April 21, 2004 7:47 AM
> To: SURBL Discussion list; Chris Santerre
> Subject: Re: [SURBL-Discuss] BigEvil + MidEvil as SURBL
>
>
> On Wednesday, April 21, 2004, 4:35:41 AM, Raymond Dijkxhoorn wrote:
> > Hi!
>
> >> BigEvil is a fairly slowly moving list. Paul Barbeau's MidEvil
> >> is quicker moving and gets new domains usually before Chris can
> >> get them into BE. In that sense ME is a feeder of changes into
> >> BE. Since they are closely related, I merged them into a single
> >> be.surbl.org. I hope Chris and Paul agree that's appropriate.
> >>
> >> What I'd like to know is what TTLs I should use on the BE data.
> >> Probably it depends on how often ME is typically updated. So...
> >> how often does ME get updated Paul? :-)
> >>
> >> Also I'd like feedback on the TXT message. I've got the
> >> placeholder:
> >>
> >> "Blocked in BigEvil. See: http://www.rulesemporium.com/"
> >>
> >> but would like feedback on it.
>
> > Do we get a different value on looking up? For example:
>
> > 127.0.0.2 for BE and 127.0.0.3 for ME ?
>
> > We should start doing that also to get the combined list going.
>
> Currently we will have them lumped together (i.e. it's
> all .2 without differentiation as to the source). As I
> understand it that may be appropriate since ME is meant
> to be essentially updates to BE. I think of them as the
> same list, especially since Chris eventually merges the
> ME (update) entries into BE. I kind of short circuit that
> process by merging them for them before turning them into
> be.surbl.org. Hopefully that's ok.
>
> Lists with greater differences such as ws and sc probably
> should get different A or TXT records when we eventually
> combine them.
>
> FWIW even if we offer a combined list, the individual
> ones will probably still be available, like SBL, XBL &
> SBL-XBL at spamhaus.
>
> Jeff C.
>
> P.S. Chris please sign up for the SURBL Discussion and
> Announce lists if you can: http://lists.surbl.org/
>
I already am ;)
Yeah, usually I update BigEvil a lot more often. I'm dealing with a lot of
projects now. Some are even work related ;) And then some are beta testing a
new game :-) Paul and I are still working out how we can merge ME and BE
together without a lot of work. But I have no problems at all combining the
ME and BE together and letting Paul add just as much as me. He knows my
basic criteria for checking the domains.
A few things off the top of my head. Sorry if they have been discussed, I
have a LOT of email to read :)
1) BigEvil wildcards. Not sure how you would handle these. Something like
evil\d{2,4}spam\.com is a general wildcard. Some of those domains don't even
exhist. Not sure how SURBL will handle that.
2) Where would I send updates? As single domains, or a txt list? How would I
remove an FP?
3) What is the quickest way to check a domain against the other SURBL lists?
Basically I see no reason to duplicate the listings. *gulp* and on a
Windowze machine? (Don't ask!)
4) Has there been any talk with the sendmail people? It would be interesting
to actually block at the MTA level based on an evil URL. I realise the
inherent dangers in this ;)
--Chris
[forwarded response from announce list]
Chris Santerre wrote:
> The ONLY complaint anyone ever had with Stearn's list was the overhead. With
> it setup this way, there is no stopping him!! :)
>
> Great job by Bill and Jeff!
>
> --Chris (Yeah I know,....the list.) :-)
[snip]
>>Wow, I implemented this yesterday and, after about 18 hours,
>>this rule was
>>#4 in my list of most-used rules! Good job, guys!
[snap]
I'm getting most excellent spam catching here.
For a while was only catching 70-80% but now am catchng closer to 95+%
Still have the odd one slipping through.
Which reminds me I need to grab a new bigevil 8*)
And even though Bill Stearns list does take a bit f overhead I am still
using it and a whole slug of other rules as well as wc.surbl.org. But
the surbl is the one that is now doing the most catching.
-Doc
On Tuesday, April 20, 2004, 6:10:30 PM, Bill Landry wrote:
> ----- Original Message -----
> From: "Jeff Chan" <jeffc(a)surbl.org>
>> So the quick answer is they'll probably not be combined.
>>
>> However we probably will offer a combined version of Bill's
>> list and Chris' BigEvil list since they are more similar in
>> character.
> Jeff, why not one DNS query that supports multiple result codes:
> test: somedomain.com.sc.surbl.org
> results:
> 127.0.0.2 = Spamcop
> 127.0.0.3 = WS List
> 127.0.0.4 = BigEvil List
> 127.0.0.5 = etc...
> Same thing multi-test RBLs like AHBL, Sorbs, Blars, FiveTen, NJABL and
> others do.
Yes, we may end up doing that in a combined list.
Jeff C.
Chris Santerre forwarded me a script from Gary Funck called
expand_regexp.pl which apparently is designed to expand SA
regexps into domains. I used that on BigEvil and MidEvil to
turn them into an SURBL, be.surbl.org, but I want to get a
couple details sorted out before turning it live.
BigEvil is a fairly slowly moving list. Paul Barbeau's MidEvil
is quicker moving and gets new domains usually before Chris can
get them into BE. In that sense ME is a feeder of changes into
BE. Since they are closely related, I merged them into a single
be.surbl.org. I hope Chris and Paul agree that's appropriate.
What I'd like to know is what TTLs I should use on the BE data.
Probably it depends on how often ME is typically updated. So...
how often does ME get updated Paul? :-)
Also I'd like feedback on the TXT message. I've got the
placeholder:
"Blocked in BigEvil. See: http://www.rulesemporium.com/"
but would like feedback on it.
TIA & Cheers!
Jeff C.
--
Jeff Chan
mailto:jeffc@surbl.org-nospam
http://www.surbl.org/
> Hi Scott,
> Multiple A records can result from a single query:
>
> > % nslookup www.yahoo.com
>
> > Name: www.yahoo.akadns.net
> > Addresses: 216.109.117.207, 216.109.118.75,
> 216.109.118.66, 216.109.118.77
> > 216.109.118.73, 216.109.117.205, 216.109.117.204,
> 216.109.118.70
> > Aliases: www.yahoo.com
>
> And they should all come from the locally cached copy of the zone
> file, so they're fast.
>
> A single bit masked A record would be smaller but require a little
> more application CPU to decode. Multiple A records may be faster
> but they're bulkier. I find the multiple A records more readable.
> It's one of those classic tradeoffs.
>
> Jeff C.
>
So desu ka.
I would have thought that a bit masked record was faster, as you already have all the data you need with the first call. From then on bitwise CPU operations would be umpteen times faster than performing slower DNS callouts, even if they are cached. I am assuming, however, that perhaps the Spamassassin code 'caches' the first A record lookup for bitwise operations...I am not too familiar with the eval-rbl workings. It may be that it performs subsequent DNS lookups in either case? The only way to speed that up would be to load the first lookup into a variable for use in later bitwise calculations...
Anyway keep up the good work all,
cheers
Scott