Fwd: Contact w/ clue re: AT&T SMS email gateway?

[Marc Powell]

Seen on NANOG mailling list, forwarding here due to recent question  
about this same issue. Appears to be an ATT thing at this point.

No interesting responses to the thread yet.

--
Marc

Begin forwarded message:

> From: Dave Pascoe <davekm3t at gmail.com>
> Date: September 17, 2009 2:03:55 PM CDT
> To: nanog at nanog.org
> Subject: Contact w/ clue re: AT&T SMS email gateway?
> Reply-To: Dave Pascoe <dave at tcnc.com>
>
> Recently something seems to have changed with the @txt.att.net email  
> to
> SMS gateway.  Messages sent through the gateway suffer from the  
> following:
>
> 1) Long delay in reaching the phone (intermittent)
>   (yes I know there is no latency guarantee)
>
> and, even more crippling,
>
> 2) Message comes through as just "SMS Message" instead of the SMTP
> message content.  And the sender is always 410-000-01x, where x
> increments by 1 with each new incoming email-to-SMS gateway-handled  
> message.
>
> Phone is an iPhone 3GS.  This has worked fine for quite a while.  No
> changes on the iPhone.
>
> I have gone through normal AT&T Wireless Customer Service but there
> isn't much clue there - had to explain what an email to SMS gateway  
> is.
>
> Anyone elese seeing this?  Anyone from AT&T Wireless here?
>
> Please contact me off-list.
>
> TIA,
> Dave Pascoe
>


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null