Jay is correct. I was a policy enforcement manager for a 'tier 1' for
awhile and I dreaded the spam routine every day along with the anti
spam fanatics. Both are big problems but when you face a fellow
provider that's as large as Verizon, there's not much one can do (in
my position) because of all sorts of agreements (i.e. routing, peering
agreements and many others) it was very difficult for a mid level
manager to convince the senior management the blocks needed to be
placed.
I did, however, have the capability to add my own blackholed routes to
the BGP sessions and (at the time) out of about 18,000 lines, *cn did
occupy about 60% of those. Verizon was always a problem to deal with
and never really wanted to address any spam related issues. All I'd
get was 'send the complaint to their abuse/spam section. What they
did I never knew and never saw any decline in the problem. At least I
could jerk a knot in our own customers when necessary.
I feel your pain but don't see your problem (as well as ours) changing
anytime soon from any action from Verizon.
Also, I've not kept up with the bidding war for MCI but if Verizon did
or will win it (God forbid), the 'Net as we know it will only get
worse. Their severe lack of customer service/focus is awful on every
end from home service, to Internet connectivity and to their wireless
service. I, like many, will never subscribe to anything they offer
unless there's no other way.
*waves to Jay*
-th
<c0 snippage>
Verizon.net is blackholed on our networks two reasons:
1. The sheer volume of spam courtesy of their netblocks, and
2. The sheer audacity of their "whitelist" arrangement in
which I and my customers have to give *them* our personal
data to send their users e-mail...while verizon itself
apparently does nothing to curb its outbound spam.
Since verizon.net was blackholed on our networks, our spam level
has gone down significantly; almost as much as it did when we blackholed
all of China.
- -Jay
--
-th
This communication is privileged & confidential to the intended recipient.
