OK Looks like someone (lol I'm nominated, I guess) needs to put his foot down and set a new name for sa.surbl.org, our RBL version of Bill Stearns' sa-blacklist SA ruleset.
I suggested "sb", though that's slightly confusing with sc. Bill suggested ws or sb would work for him. Does anyone else have any comments or idea?
We should change this soon before too many people start coding in "sa.surbl.org".
Please comment if you have any. ;-)
Thanks,
Jeff C.
On Mon, 12 Apr 2004, Jeff Chan wrote:
OK Looks like someone (lol I'm nominated, I guess) needs to put his foot down and set a new name for sa.surbl.org, our RBL version of Bill Stearns' sa-blacklist SA ruleset.
Is this DNSBL different from other RHSBLs? If not why reinvent the wheel? rhsbl.surbl.org sounds good to me, though unless use is to be somehow restricted to just sa there should be a distinction between sender domains (user@example.com) and host domains (mx1.example.com). For that I use sender.rhsbl...com and client.rhsbl...com, saving ip.rbl...com for the RBL.
On Monday, April 12, 2004, 5:05:09 PM, Ram Ram wrote:
On Mon, 12 Apr 2004, Jeff Chan wrote:
OK Looks like someone (lol I'm nominated, I guess) needs to put his foot down and set a new name for sa.surbl.org, our RBL version of Bill Stearns' sa-blacklist SA ruleset.
Is this DNSBL different from other RHSBLs? If not why reinvent the wheel? rhsbl.surbl.org sounds good to me, though unless use is to be somehow restricted to just sa there should be a distinction between sender domains (user@example.com) and host domains (mx1.example.com). For that I use sender.rhsbl...com and client.rhsbl...com, saving ip.rbl...com for the RBL.
Currently we have two RBL:
sc.surbl.org - domains from SpamCop URIs sa.surbl.org - domains from Bill's sa-blacklist
Both are domain-type RBLs intended for use as RHSBLs (rbls that contain domains instead of numbers) but for checking message body URIs. This is really a new use for domain-type RBLs which in past had been used against senders. SURBL is about blocking based on web servers mentioned in messages.
We're simply trying to change the name "sa" because some SpamAssassin developers thought it implied support from SpamAssassin. Bill's list was meant to work with SpamAssassin, but is made by him and not that community specifically.
Jeff C.
On Monday, April 12, 2004, 5:21:40 PM, Jeff Chan wrote:
Bill's list was meant to work with SpamAssassin, but is made by him and not that community specifically.
Needless to say :-) Bill's list in RBL form becomes useable far beyond SpamAssassin. As an RBL it can be used with any program that can resolve names in an RBL and parse message body URIs into domains. That would include future milters, etc.
So who has some alternate name suggestions instead of "sa.surbl.org," or would sb or ws be ok?
Jeff C.
Good evening, Jeff,
On Mon, 12 Apr 2004, Jeff Chan wrote:
On Monday, April 12, 2004, 5:21:40 PM, Jeff Chan wrote:
Bill's list was meant to work with SpamAssassin, but is made by him and not that community specifically.
Needless to say :-) Bill's list in RBL form becomes useable far beyond SpamAssassin. As an RBL it can be used with any program that can resolve names in an RBL and parse message body URIs into domains. That would include future milters, etc.
So who has some alternate name suggestions instead of "sa.surbl.org," or would sb or ws be ok?
In the end, it really doesn't matter. It could be called floogleglooble.surbl.org and it would still have the same content. Let's make this last call for opinions. Jeff, unless you hear from anyone else with a strong opinion, let's pick. I vote we move away from the s* that's a little too close to the sc.surbl.org; we'll be fielding confused user questions. Lets change the name to ws.surbl.org. We'll need to continue to put the list out as sa.surbl.org for a week or so after changing the instructions on www.surbl.org _and_ announcing it to the discuss and announce lists _and_ switching over all secondaries. Then we can simply stop answering queries on that domain. Cheers, - Bill
--------------------------------------------------------------------------- Boucher's Observation: He who blows his own horn always plays the music several octaves higher than originally written. (Courtesy of "Brett W. McCoy" bmccoy@chapelperilous.net) -------------------------------------------------------------------------- William Stearns (wstearns@pobox.com). Mason, Buildkernel, freedups, p0f, rsync-backup, ssh-keyinstall, dns-check, more at: http://www.stearns.org --------------------------------------------------------------------------
On Monday, April 12, 2004, 7:27:12 PM, William Stearns wrote:
On Mon, 12 Apr 2004, Jeff Chan wrote:
On Monday, April 12, 2004, 5:21:40 PM, Jeff Chan wrote:
Bill's list was meant to work with SpamAssassin, but is made by him and not that community specifically.
Needless to say :-) Bill's list in RBL form becomes useable far beyond SpamAssassin. As an RBL it can be used with any program that can resolve names in an RBL and parse message body URIs into domains. That would include future milters, etc.
So who has some alternate name suggestions instead of "sa.surbl.org," or would sb or ws be ok?
In the end, it really doesn't matter. It could be calledfloogleglooble.surbl.org and it would still have the same content. Let's make this last call for opinions. Jeff, unless you hear from anyone else with a strong opinion, let's pick. I vote we move away from the s* that's a little too close to the sc.surbl.org; we'll be fielding confused user questions. Lets change the name to ws.surbl.org. We'll need to continue to put the list out as sa.surbl.org for a week or so after changing the instructions on www.surbl.org _and_ announcing it to the discuss and announce lists _and_ switching over all secondaries. Then we can simply stop answering queries on that domain.
Thanks Bill. ws sounds good to me. Sounds different from sc and hopefully from "be" for BigEvil. I agree with your migration plan in general, but we may want to set up ws and run it in parallel with sa on the secondaries for the week or so.
Any other comments anyone? Good ideas are always welcomed.
Jeff C.
floogleglooble.surbl.org
HAR! Thanks for the big giggle. But seriously I actually think this might be a good name for this stuff! 8*)
Make it obscure enough to work!
Now on a more serious note. Do those of us secondaries need to make changes for the zones we get?
I'm off to work.
-Doc
On Monday, April 12, 2004, 8:19:53 PM, Doc Schneider wrote:
floogleglooble.surbl.org
;-) (Bill's point is right though. The name of the list doesn't really matter; it's the content that counts.)
Now on a more serious note. Do those of us secondaries need to make changes for the zones we get?
Yes, if we change the name of the list or add lists, the secondaries and rsync users will need to make corresponding changes in their name servers and rsync servers.
sa.surbl.org is changing to ws.surbl.org. For now we'll probably ask all the secondaries and rsync mirrors to add the ws zone, i.e., to carry all three of:
sc.surbl.org sa.surbl.org ws.surbl.org
with sa to go away in a week or so as we get SURBL users get moved from it and over to ws.
If this sounds ok to everyone, I'll post an announcement to zones and announce. Anyone with any comments please speak up. (I suppose the deafening silence is a hidden plea for some leadership. ;-)
Jeff C.
-
Doc Schneider -
Jeff Chan -
Ram -
William Stearns