notifications to [phone-number]@tmomail.net are no longer working. I'm using the default smtp settings and the "send notification to" action.

 

 

It is likely tmobile doing this.  Verizon started disallowing this as well several years ago.  Though I was too lazy to completely remove my text notifications and still occasionally I get one hours or days later.  I now just depend on email notifications.  Those seem solid.

Try googling tmobile email to text notifications and see what might come up.

Edited March 19Mar 19 by jkmcfadden

It sounds like this may have stopped working a while ago and I haven’t noticed. Anyone know of another way to send sms messages from iOX? Maybe the notification plugin?

I'd suggest biting the bullet and moving to the paid for notification plug-in with the pushover app vs texts.

The problem is the mobile carriers not wanting the traffic, not the iox method of trying to get it there

I have the paid for notification app, never used pushover. Some of the notifications go to family members and they seldom read emails, that is why I want to send SMS.

Most of the major wireless carriers have been blocking non-wireless to wireless sms messages.  Most likely to reduce spam from auto dialers.

Had the same with T-Mobile over some time and finally switched to Pushover about a year ago now. Works way better and reliable with customization like Critical override. Worth the $5 if it is still that price. 

So I've confirmed that the t-mobile email to SMS gateway is still working when I send to it from my personal email address. I suspect they have blocked the default UD SMTP server. I tried using my own gmail login in the admin console but get smtp error -1 (see below). Do you see anything wrong with my settings?

 

 

Doesn't the user need to be a gmail account or did you not update the SMTP server settings? Seems you are using a gmail SMTP but a ID for sandbergweb.com.

Edited March 21Mar 21 by sdynak
typo

Pushover is totally worth it. Keeps your notifications separate and is much more reliable. 

On 3/19/2025 at 4:27 PM, photogeek54 said:

I have the paid for notification app, never used pushover. Some of the notifications go to family members and they seldom read emails, that is why I want to send SMS.

With the Notification plugin and Pushover your notifications can be sent as a message in Pushover app, very similar to text messages (with history), not an email.

@sdynak that is a Gmail account. I have my own domain  setup in a Gmail workspace.

I can’t use pushover as. I send to many people and don’t want to make each of them get a pushover app.

21 minutes ago, photogeek54 said:

@sdynak that is a Gmail account. I have my own domain  setup in a Gmail workspace.

I can’t use pushover as. I send to many people and don’t want to make each of them get a pushover app.

Ok, I'm not familiar with the Gmail workspace and if it functions the same. 

Are you using a "App Password" for Gmail? I believe you need this to make it work as a more secure environment. Not sure that will work with your domain setup. You could always just try a standard Gmail account and test. 

 

This could help also - 

 

Edited March 21Mar 21 by sdynak

Yes adding an app password was the answer, thanks for the tips. SMTP now works. I suspect that that tmobile is rate limiting the messages coming from UD.  I am able to send some texts via the phone@tmomail.net gateway using my gmail SMTP but may be rate limited too. I'll update if I figure that out.

UPDATE: I setup a program to send SMS to tmobile every 5 minutes. My Eisy sent the messages every 5 minutes for about 20 times (missing 2 of the messages towards the end) then became highly irregular. So yes it works somewhat but is definitely rate limited.