[126648] in North American Network Operators' Group
Re: txt.att.net operators
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Wed May 26 14:12:19 2010
In-Reply-To: <A16877978862E44E9F4EECD23635750E010FDA24@zionex1.ZION.local>
Date: Wed, 26 May 2010 14:11:39 -0400
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Mike Walter <mwalter@3z.net>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, May 26, 2010 at 11:17 AM, Mike Walter <mwalter@3z.net> wrote:
> We have been struggling to locate someone at AT&T that handles the
> txt.att.net servers. =A0We have clients in our data center that can no
> longer send emails to mobile phones via 10digit@txt.att.net. =A0We have
> contacted AT&T and they say there is no problem on their end. =A0We can
> ping the server, but simply cannot connect to port 25. =A0We have checked
> all firewalls of each client. =A0Some ranges of IPs work and others don't=
.
> Looking for someone with a clue who can assist.
this is not a guaranteed service, nor does it have an official SLA,
and inbound mail/connections from louder speakers are often just
dropped, either at the TCP layer, or at the application layer (even
after what seems like a completed SMTP conversation.)
If you depend upon SMS for things, smtp -> sms gateways at the
provider aren't reliable enough.
