Forum Discussion
gmail to phone.#tmomail.net is not working
emails from GMAIL to the SMS gateway, <phone.#>.@tmomail.net are NOT received as texts.
emails from OUTLOOK to the SMS gateway, <phone.#>.@tmomail.net ARE received as texts.
google has a gmail application "email to text" whereby one can gmail <phone.#>@sendemailtotext.com and receive text. That is, google has their own email-SMS gateway. When using this app, I DO receive the email as a text.
It appears that google is restricting emails to the tmobile email-SMS gateway, @tmomail.net, to force customers to use googles app "email to text". Did I mention that google charges for the service?
Is there anyone who can shed any light on this? Is there anyone who can email <phone.#>.@tmomail.net and receive a text?
Gracias
frito
edwardp wrote:
The vast majority of messages, are a miss.
As of yesterday (14 September 2023), such messages were not being delivered to the phones (multiple) and the senders (not specifically via Gmail) are not receiving a bounce/reject message, so it appears the messages are winding up in a black hole somewhere.
@HeavenM I understand spam filters are necessary, but when legitimate messages aren’t getting through, this is a problem.
This is beyond ridiculous now.
Not being able to get a message through can be extremely frustrating. The spam filters should not be blocking everything. Are you sending these messages from your personal email address or from an automated email service? Does the email that you are sending from include words like admin, info, alert, test, contactus, or sales? (This is not a complete list of words in the email address that are filtered but gives you an idea.) The tmomail.net message route is not designed for ANY business messages, so if you are sending a message for a business purpose, you should either send from your business email to another email address or use a message aggregation service to send those. If you are sending a personal message (like "hey I left my phone at home. Can you make sure to feed the dogs?"), then those messages should not be blocked and we can dig deeper into what happened there (Unless that message is sent from a work email that is something like alert@company.com, because those are filtered out).
I know this is extra frustrating because this email to text service has allowed these types of messages for a long time. T-Mobile is making large strides against spammers and scammers and that means cracking down on the avenues that we know those bad apples are using to take advantage of our customers. T-Mobile is leading the pack when it comes to these changes, but we are not the only ones. The other carriers are also making their filters stronger. That is why it is important to start finding the right way to send those business messages, so you don't have to worry about being flagged as spam.
There is a way I have worked around this and the solution is actually better.
create a new gmail account.
setup spark email to connect to this account. (I have an iPhone)
instead of emailing tmomail.net , email to this new address you createdenable notifications on spark so it pops up whenever an email arrives. I have implemented this on my end for my stock alerts and it actually works better because I am not limited to text.
notifications also show up on my Apple Watch and this avoids the total nonsense from T-Mobile.Try logging into Gmail and setting up the forwarding allow list. Its under gmail settings "forwarding and POP/IMAP" gmail will send a verification code to the recipient to allow forwarding. Just a thought since its a static address that maybe gmail will tag the outgoing email/sms differently.
Use the $5 app, pushover, to send notifications to your phone. Search ipcamtalk.com for instructions on how to use it.
I've been in the process of setting up a small alert system with gmail for our staff in case of building emergencies in case email isn't an option.This has worked for me flawlessly in testing until today (day before release). Now 9 out of 10 texts to tmomail.net bounce with the 550 5.1.1 server temporarily unavailable AUP#MXRT message--which brought me to this forum showing this problem has been rotting for a while.
This approach is incredibly short-sighted. This is not spam, it's messaging our own staff who have consented to receive messages. Only t-mobile has this problem. For those who say "you need to send an to a real email address"--well no, that's the whole point. It's used as a fallback in case other communications don't work. T-Mobile is disregarding sms standards here. For the record, t-mobile's spam prevention is atrocious, I get several fake messages a day, but the one that has a legitimate purpose is blocked without being reported as spam.
So no, I don't accept that we should find another method. T-mobile should support standards. Right now they are failing in that regard, and from what these forum anecdotes tel me, rather miserably.
