Arrogant RBL list maintainers
frnkblk at iname.com
Wed Dec 9 21:08:07 CST 2009
I've seen their form, too. I think you're reading too much into their
Does it matter if they label your non e-mail server IPs as dynamic space,
and therefore put it on their DUL?
From: Michael Holstein [mailto:michael.holstein at csuohio.edu]
Sent: Wednesday, December 09, 2009 3:18 PM
To: Ken Chase
Cc: nanog at nanog.org
Subject: Re: Arrogant RBL list maintainers
> To be clear: because the legitimate mailserver with a proper non-generic
> reverse was in a block with other generic reverses, they blacklisted you?
Their initial email said :
Trend Micro Notification: 126.96.36.199/16 added to DUL
and then went on to say :
To work with us, please generate the following three lists:
1) TOTAL ALLOCATED SPACE - in CIDR format
Please include all information for the space you announce.
The total of Static and Dynamic space must equal the
Total Allocated Space.
2) DYNAMIC SPACE LIST - in CIDR format
3) STATIC SPACE LIST - in CIDR Format
Which was, of course, impossible .. since trunking a VLAN across the
core just to have all the printers in the same /22 would be silly.
After some arguing back-and-forth .. they (Trend) said :
Also we don't see the IP address as static as we see the generic naming
*csuohio.edu* as dynamic and the WHOIS information doesn't indicate that the
space is static.
Seriously .. we're a college campus, not a colo. Org-Abuse roles is defined
(and valid) and real people read the RFC2142 required addresses. What more
do these people want?
(Note: they did eventually say "okay, we see the MXs as static so those
aren't listed" .. but not without some discussion).
Cleveland State University
More information about the NANOG