North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: 209.68.1.140 (209.68.1.0 /24) blocked by bellsouth.net for SMTP

  • From: Suresh Ramasubramanian
  • Date: Mon Sep 19 23:35:21 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rte+lUnh9s6VxHnFuK2iZIsv1Tnvq8W8gU/TCrxdYbSCQ51BeLekhCATUyBgtlvMghPHooXlpFk9+Q5tX/VPT3RQXlkiphhO2B4/oWNnCyvzTZ+mcK+Jp3aCqrRpnOjtdJ9J9kki0/zZESu64dtVwPz+JDhJFoOcTyhjAK+VpXM=
On 20/09/05, Alan Spicer <[email protected]> wrote:
> 
> I wonder if anyone with Bellsouth.net can tell me why this ip or /24
> 
> 209.68.1.140 (209.68.1.0 /24)
> 
> would be blocked from sending SMTP to bellsouth.net customers.
> 

That's a large (and quite good) webhost called pair.com, which also
hosts the Pittsburgh IX (pitx.net)

http://www.pair.com/support/notices/blocked-email.html

Blocking is fine - happens.  Postmaster and other role accounts not
replying at all to email that they're sent is just not a good thing to
do.

--srs
-- 
Suresh Ramasubramanian ([email protected])