--
Comments posted to news.admin.net-abuse.blocklisting
are solely the responsibility of their author. Please
read the news.admin.net-abuse.blocklisting FAQ at
http://www.blocklisting.com/faq.html before posting.
That you may be SWIPed 76.209.202.0/25
does not make you the owner,
in this case a renter (Baptist Child and Family Services)
that asks others (IP whois) to contact the owner (AT&T)
with any complaints.
ASHandle: AS7132
CIDR: 76.192.0.0/10
NetRange: 76.192.0.0 - 76.255.255.255
NetType: Direct Allocation
OrgName: AT&T Internet Services
CIDR: 76.209.202.0/25
NetRange: 76.209.202.0 - 76.209.202.127
NetType: Reassigned
CustName: Baptist Child and Family Services IAF 1149236.6376
RAbuseEmail: ab...@sbcglobal.net
RNOCEmail: sup...@swbell.net
RTechEmail: ipa...@att.com
OrgAbuseEmail: ab...@sbcglobal.net
OrgNOCEmail: sup...@swbell.net
OrgTechEmail: ipa...@att.com
Since you aren't a IP or AS whois listed contact,
reports of abuse won't be sent to you, they would
be sent to AT&T who may not do anything about it,
likely not even notifying you.
Nothing very surprising about someone listing or blocking
AT&T netspace.
<http://www.spamhaus.org/statistics/networks.lasso>
The 10 Worst Spam Service ISPs As at 01 August 2007
Rank Network Number of Current Known Spam Issues
1 verizon.com 49
2 xo.com 40
3 gwbn.net.cn 35
4 att.net 34
<http://www.spamhaus.org/sbl/listings.lasso?isp=att.net>
Found 34 SBL listings for IPs under the responsibility
of att.net
21 Listings in yellow are known spam gangs with ROKSO
records <http://www.spamhaus.org/rokso/index.lasso>
(Known professional spam operations)
--
E-Mail Sent to this address <Blac...@Anitech-Systems.com>
will be added to the BlackLists.
> Humor why a CIDR of 76.208.0.0/13 would be blocked if there was no
> CIDR associated with it. hav a lookup up in ARIN for 76.209.202.101...
> You'll see that AT&T owns 76.192.0.0 - 76.255.255.255, and I own
> 76.209.202.1 - 76.209.202.127. Who brained up the idea to block a
> range of static IP's from AT&T?
It may surprise you but routing info is considered more reliable than
WHOIS info. Use your own brain and take a look at routing data (BGP).
#v+
$ whois -h riswhois.ripe.net 76.208.0.0
% This is RIPE NCC's Routing Information Service
% whois gateway to collected BGP Routing Tables
% IPv4 or IPv6 address to origin prefix match
%
% For more information visit http://www.ripe.net/ris/riswhois.html
[...]
route: 76.208.0.0/13
origin: AS7132
descr: SBIS-AS - AT&T Internet Services
[...]
num-rispeers: 95
source: RISWHOIS
#v-
--
[pl>en: Andrew] Andrzej Adam Filip : an...@priv.onet.pl : an...@xl.wp.pl
http://anfi.homeunix.org/spamcop-top200/2007/2007-08-01.html
http://anfi.homeunix.org/spamcop-top200/last/latest.html
>Humor why a CIDR of 76.208.0.0/13 would be blocked if there was no
>CIDR associated with it.
What were you trying to ask?
> hav a lookup up in ARIN for 76.209.202.101...
>You'll see that AT&T owns 76.192.0.0 - 76.255.255.255, and I own
>76.209.202.1 - 76.209.202.127.
No. In fact, the second statement contradicts the first. AT&T owns
76.192/16, but you only lease 76.209.202/25.
>Who brained up the idea to block a range of static IP's from AT&T?
His name is legion. Some are blocking much wider swathes than that,
and quite properly.
--
Shmuel (Seymour J.) Metz, truly insane Spews puppet
<http://patriot.net/~shmuel>
I reserve the right to publicly post or ridicule any abusive
E-mail. Reply to domain Patriot dot net user shmuel+news to contact
me. Do not reply to spam...@library.lspace.org