> Le 12/12/2010 19:23, Giampaolo Tomassoni a écrit :
> > How does it work?
> >
> > I just got blocked by the AT&T's blacklist (in contacting
> ab...@att.com,
> > besides...), but I'm pretty sure my MX is not an open relay or other
> kind of
> > nifty thing.
> >
> > Maybe AT&T blocks whole address bunches from which some hosts are
> spamming?
> > Because this could explain me why: my MX is co-located...
> >
> 
> $ host tomassoni.biz
> tomassoni.biz has address 62.149.201.242
> tomassoni.biz has address 62.149.220.102
> tomassoni.biz mail is handled by 10 c0.edlui.it.
> 
> $ host c0.edlui.it
> c0.edlui.it has address 62.149.220.102
> c0.edlui.it has address 62.149.201.242
> 
> $ host 62.149.201.242
> 242.201.149.62.in-addr.arpa domain name pointer
> host242-201-149-62.serverdedicati.aruba.it.
> 
> $ host 62.149.220.102
> 102.220.149.62.in-addr.arpa domain name pointer
> host102-220-149-62.serverdedicati.aruba.it.
> 
> So both IPs use generic hostnames, which are a sign of "half
> configured"
> servers.

Unfortunately the RDNS is not under my control.

Which is a fact I share with a lot of people worldwide...


> think as the receiving side. when I see spam out of joe.spam.example, I
> blocklist spam.example (and possibly every IP and domain related to
> them). If I see spam coming from host1-2-364.serverdedicati.aruba.it,
> what will I blacklist?

I personally (and many serious blocklists) would block the single spamming
address. You may easily see that Aruba.it is a co-location provider, so you
may easily understand that different hosts from the same address bunch are
probably handled by different organizations, with different means and
purposes.

To me, it is counter-productive to block the whole bunch.

Giampaolo

Reply via email to