[84780] in North American Network Operators' Group
Re: 209.68.1.140 (209.68.1.0 /24) blocked by bellsouth.net for SMTP
daemon@ATHENA.MIT.EDU (Omar Thameen)
Sat Sep 24 06:26:16 2005
Date: Sat, 24 Sep 2005 06:25:41 -0400
From: Omar Thameen <omar@westside.urbanblight.com>
To: nanog@nanog.org
Cc: Suresh Ramasubramanian <ops.lists@gmail.com>,
Alan Spicer <a_spicer@bellsouth.net>
In-Reply-To: <bb0e440a05091920315008c9d2@mail.gmail.com>
Errors-To: owner-nanog@merit.edu
On Tue, Sep 20, 2005 at 09:01:40AM +0530, Suresh Ramasubramanian wrote:
>
> On 20/09/05, Alan Spicer <a_spicer@bellsouth.net> 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.
This may give you an idea of what issue may be and the response
you're likely to encounter.
Back in June, we contacted Bellsouth postmaster regarding their
filtering of SMTP connections (i.e., so that connection attempts
hang until the timeout is reached), and received this reply from
postmaster@bellsouth.net:
We will configure our settings for your company on our
Filtering mechanism to 50 messages within a 5 minute window.
We ask that you conform to this industry standards regarding
submission of email to our mail server.
As you all know, 50 messages/5 minutes is abysmally low, particularly
for a mailing list hosting provider. Our requests for higher
threshold and a pointer to the "industry standards" were summarily
dismissed.
If there's a Bellsouth contact with more of a clue on this list,
we'd be happy to meet any reasonable requirements you have for email
delivery.
Omar Thameen
omar@BIGLIST.com
