[SURBL-Discuss] Re: Which rules are replaces by *.surbl.org?

Jeff Chan jeffc at surbl.org
Sat Jun 12 22:28:26 CEST 2004

On Saturday, June 12, 2004, 7:56:15 PM, ian list) wrote:
> On Sat, 12 Jun 2004, Jeff Chan wrote:

>> In other words the domains from BigEvil and MidEvil that can be
>> listed without many wildcards go into ws.surbl.org and the
>> domains that need more wildcards (too many to be practically
>> enumerated) will end up in BigEvil.cf .
>> Chris may not be ready to do the latter yet, but the former is
>> already in place as of a few days ago.  We're watching it all
>> run for a while before announcing officially.

> Thanks for info Jeff, one question, for us who rsync the zones off your
> servers, will the be.surbl.org.bind/be.surbl.org.rbldsnd files disappear ?
> Does this mean we need to reconfigure our bind/rbldnsd if BE disappears
> and transforms back into a .cf ?

We had lots of difficulty reaching people and getting them
to stop using sa.surbl.org when we simply wanted to rename that
list to ws.surbl.org, and that was early on, so I suspect
be.surbl.org may live on but with essentially no content.  be's
been around longer so it would be harder to get it out of configs
out there.  But the useable content from be is now in ws.

Ideally if folks want every function, they should:

0.  Use sc.surbl.org

1.  Use ws.surbl.org (which now has the be.surbl.org domains)

2.  *Not* use be.surbl.org (which is now redundant)

3.  Use BigEvil.cf (and perhaps MidEvil.cf also, depending
on how Chris and Paul work things out.)

That said, not every one chooses to use every component.
The choice is up to them.

To summarize the changes, the relatively fixed domains from
be are now in ws, and the heavily wildcarded domains will
end up only in BigEvil.cf.  So to get the original BigEvil
functionality one would continue to use BigEvil.cf and add
ws.surbl.org.  (That would also add the sa-blacklist domains
for someone who was only using BigEvil before.)

I hope this makes sense.  Please let me know otherwise.  :-)

Jeff C.

More information about the Discuss mailing list