mobile.mycingular.com Doesn't Work Anymore
See, here’s the thing. I’ve got a Cingular (now AT&T) cell phone, and I’ve got all kinds of automated systems that page me when things in my business go awry. All of my systems are set to send email to [mycellphonenumber]@mobile.mycingular.com.
But in the last couple of days, I’ve noticed that notifications that should have arrived on my cell phone weren’t coming through (I copy those notifications to multiple addresses, so I still knew about them).
As best I can tell, you now have to send your email to [mycellphonenumber]@txt.att.net instead of the old mobile.mycingular.com address.
You can also use [number]@cingularme.com, but I’m betting it’s only a matter of time before that address goes away, too.
Hope that helps somebody out there…
UPDATE (9/5): Sometime late in the afternoon on 8/30, mobile.mycingular.com started working again. That said, I found that txt.att.net has a big advantage over mobile.mycingular.com: message size. With mobile.mycingular.com, most of my alert messages came through in 4 parts (that is, the email notification was split into four separate text messages). WIth txt.att.net, although the message is still broken into four parts, it’s delivered as a single text message. Strange, but it may save a bit on text message charges.
9 Responses Leave a comment
I've seen this too. not sure whats up. Was just googling to find out why and came across this
I'm seeing mobile.mycingular.com still working there is a pretty long delay before the message is received from their server. I've tried switching over to msg.att.net but I don't know if all numbers have been ported over. Have you had any luck figuring this out?
Fish ><>
seems that i’m not able to get texts using either mobile.mycingular.com or txt.att.net, anyone else having issues?
nevermind, turns out it was an (att) agent error (“accidentily” removed texting from my acct)… i was, however, able to confirm @txt.att.net is however the correct (preferred) domain for text messages (and @mms.att.net is the correct domain for multi-media messages)
The problem is that mobile.mycingular.com comes into the iPhone from 1 set source number, meaning 1 message thread. txt.att.net comes in as an incrementing source number (1(410)000-001, 002, 003, etc) so its a new message thread everytime you receive a message. This is PAINFUL for my needs as we sometimes get 100+ alerts if a router or a firewall fail over.
That’s a very interesting distinction, and not one that I had noticed. I’ve been using txt.att.net for some time, but I have the same situation that you do: When a router or firewall fails, I get LOTS of threads because lots of monitored equipment suddenly is unreachable. Fortunately, that is an exceedingly rare occurrence.
Having the SAME problem here. AT&T took down that server and directed the MX record to the same server as txt.att.net. Have been on the phone for hours with them and nobody that I have talked to knows how to fix it other than to say those servers were taken down. This is very discouraging for types like us that have systems that depend on it working the way it has for years. They won’t change anything unless we voice our opinions or start leaving AT&T in large numbers until someone there wonders why their customers are leaving. CALL IN AND COMPLAIN. If enough people complain maybe they will fix it. Have to go now, I have about 100 text messages I have to delete on my iPhone as well…sore finger here I come…
After upgrading my iPhone to 4.2.1 (coincidence?) the texts to mobile.mycingular.com are now coming in the same format at txt.att.net.
This means back to getting each message as a seperate thread.
Has anyone else noticed this?
I have noticed the texts to mobile.mycingular.com are now coming in the same format at txt.att.net. This sucks for any system admin out there. Time to give AT&T a call.