> On Thu, Mar 28 4:32PM Scott Evans said : > I, as I'm sure many here do, use this for our network/service monitoring and > if all heck breaks loose and I have 100's of notifications the @txt results > in each appearing as an individual text which can be very tedious to
This is true. I basically use the gateway address as a paging system, defining "senders" that specific notifications come from so that my text messaging app can distinguish these "senders" as unique individuals and play a specific notification tone when one of these messages come in. I've already been hit with AT&T's (I'm sure their not the only one) heavily filtering these messages based on content so I only send a really simple one word in these messages. Since the message itself isn't that important - it's the "sender" that is important in my specific need. This can't be duplicated with the txt address, since the txt doesn't come from a consistent sender. > On Thu, Mar 28 4:32PM Blake Hudson : > There are some alternatives to sms/mms, but it depends on your device and its > capabilities. I can use IMAP and push notifications. The downside here is that my phone (Android) seems to want to go to sleep and shut off wifi, especially at night. Which is really when these notifications are of more importance. And then getting unique notification tones for different messages is also a bit more problematic. I've tried tackling these issues before, but then MMS always seems to start working again so I abandoned it. But as you say, MMS email gateways are becoming less and less reliable. So I may just have to bite the bullet and work on these issues and get away from the MMS gateway. > On Thu, Mar 28 1:33PM Jay Hennigan said : > Extreme congestion of the cell site to which the phone is connected is > another possibility. I've seen this firsthand with an annual event that > brings a large population to a rural area where the cell I can't really completely discount this. But I'm in a rural area, so I don't think the towers are congested. Plus, regular MMS works (picture from someone else's phone sent directly to my phone number). The only part that is consistent is the MMS email gateway. I can tell from the logs that AT&T's mail servers are accepting the message - but then it just seems to sit there a while before it ever reaches the phone. Unfortunately, I'm not an admin on AT&T's mail servers so I can't see what is happening to the message after it is accepted by their mail server. I'm guessing that this MMS email gateway is not used by a lot of people, otherwise I'd think that there would be more urgency to resolve this and fully resolve this (this isn't the first time this has happened for me - and others seems to have experienced the same thing). Or perhaps Jay is right - and this is only affecting me right now. I just thought if any admins from AT&T monitored this list they might want to take a look at their MMS email gateway servers: mx3a.txt.att.net [166.216.149.129] mx3b.txt.att.net [166.216.152.132] and see if something is flaky on there. But as Blake suggested - I'm probably better off abandoning the MMS email gateway so as to better avoid this problem in the future. _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
