[RFCI-Discuss] Yahoo Listing

[Brian W. Antoine]

At 02:54 PM 10/9/2002, you wrote:

>On Wednesday, October 9, 2002, at 04:05  PM, Brian W. Antoine wrote:
>>   I used NOC in a more generic sense I guess.  Yeah, that number is only
>>supposed to get you to somebody responsible for the network and I usually
>>consider that somebody in the NOC.  If I'm calling about a DOS attack,
>>somebody issuing a ticket number ain't going to cut it. :)
>
>fine, let's list 0.0.0.0/0
>
>You have a UU.NET dialup customer DOS'ing you. You call UU.NET, do you 
>think you're going to get to talk to someone immediately who will make it 
>stop? No, you're going to get someone to open a ticket to (hopefully) 
>resolve it.

   I won't get to talk to the NOC because they could care less about me.
If the person in charge of CNN.COM called them, he might get a different
response.  I don't personally believe that difference should exist, but
it does.

   It's all about money.  Most large networks will probably care less about
an rfc-ignorant listing until it starts costing them money.  So what if a
few small personal networks bounce the occasional message.  Now if AOL or
EarthLink suddenly started bouncing stuff, they'd sit up and take notice.

   The only other way to get their attention is by getting their own customers
to jump on them, and I just went through that with a customer of UUNet.  This
last week after UUNet got a /16 listed in ipwhois and I couldn't get email
from a company inside that block.  I wrote the company, got them to raise
hell with UUNet, and a week later the listing got taken care (hopefully with
help from the customer I prodded).  I noticed the company also took care of
their own personal listings at the same time, so I guess I caught more than
one bird with that stone. :)

   Related to that issue, would this list be a decent place to discuss sendmail
configuration issues when using DNSBL's?