Skip to content
WelcoYour alerts, by text.

T-Mobile tmomail.net not working: why alerts vanish without a bounce

If tmomail.net is not working for your alerts, the on-call T-Mobile phone can get them back once you change one address. T-Mobile's tmomail.net email-to-text gateway reportedly stopped delivering in December 2024, with no formal notice. Mail is still accepted and then dropped, so your monitoring tool logs a success and no bounce comes back. Point those alerts at your Welco address instead.

7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing

  • A delivery report for every text
  • No agent or plug-in
  • No per-user fees

Replaces email-to-text from

  • T-Mobile

Published:

Server monitor emails 5551234567@tmomail.net; the T-Mobile gateway replies 250 OK but drops it, so no text arrives. The same alert sent to it-oncall@welco.ai goes through Welco to the phone. The email reaches Welco and the phone shows: “Welco: [srv14] Server DOWN, no ping 5 min at 2:41 AM. Reply STOP to opt out.”

Animation: the old carrier address 5551234567@tmomail.net is replaced with the Welco address it-oncall@welco.ai, and alerts arrive again.
  • No shutdown date was announced. SigSpan reports delivery got unreliable in November 2024 and stopped in December 2024.
  • Emails to tmomail.net are reportedly accepted and then dropped, with no bounce.
  • Metro by T-Mobile phones used the same gateway.
  • Fix: replace each @tmomail.net address with your Welco address and watch the delivery report.

What the on-call admin gets back

  • Alerts on the T-Mobile phone again

    Welco texts the mobile number itself, so a dead gateway domain no longer sits between your server and the admin.

  • Proof beyond a 250 OK

    A delivery report shows whether each text reached the phone and, if it didn't, the reason in plain English.

  • Only the alerts worth waking for

    Alert rules can text DOWN and CRITICAL and leave warnings and recoveries in email.

  • Nights go to whoever is on call

    Route by time of day, so after-hours alerts reach the night admin and the day team sleeps.

When did tmomail.net stop working?

Reports put the stop in December 2024, though T-Mobile never published an end date for its gateway. What we know comes from services that track carrier delivery. SigSpan, NVRtxt and Notifyre all report the same pattern. T-Mobile's exit was the quietest part of the email-to-text gateway shutdown.

Delivery first became patchy in November 2024. Because there was no announcement, many teams found out only when a server went down and nobody's phone buzzed. T-Mobile now also runs the US Cellular gateway.

Are my T-Mobile alerts affected?

  1. 1.Does any monitoring tool or alarm send email to an address ending in @tmomail.net?
  2. 2.Does anyone on call use Metro by T-Mobile and get alerts through an email address?
  3. 3.Has one person's phone gone quiet since late 2024 while others on the same list still get alerts?

Answer the 3 questions to see your result.

Why tmomail.net failures don't bounce

Your monitoring server hands each alert to a mail server and waits for an OK. Once it gets one, its job is done. It can't see what happens to the message after that.

Reports say T-Mobile's side still gives that OK, then discards the message. No bounce, no error and no text. Every check on your side looks normal.

What the mail log shows

In a Postfix log, an accepted message ends in status=sent with a 250 reply. That line only proves the handoff, not the text. Treat a tmomail.net line like that as unproven.

Prove it, then fix it in 15 minutes

Start with one test so you know the gateway is the cause. Then make the switch. Moving many tools at once? Use the carrier switch checklist.

  1. Send one test to the T-Mobile address

    Trigger a test notification to the tmomail.net contact and wait ten minutes. If the log says sent and the phone shows nothing, you've found it.

  2. Find every tmomail.net contact

    Search your configs and user lists for tmomail.net. On a Nagios server, grep -r tmomail.net in the config folder lists them all.

  3. Set up Welco and confirm each phone

    Sign up with your work email, get your business verified and invite the on-call admins. Each one enters their own number and replies YES before any alert is sent.

  4. Approve the monitoring server

    Add the address your server sends from to approved senders, so only your tools can text your team.

  5. Swap the address and check the report

    Replace the tmomail.net address with your Welco address. Fire a test, then open Welco's delivery reports to see the text land.

Stop losing alerts to a gateway that says OK

Point your monitoring tool at Welco and see each delivery for yourself.

7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing

A switch alert that tmomail.net would have dropped

This Zabbix problem email went to a T-Mobile address. Through Welco, it becomes one line the on-call admin can act on.

Alert email from zabbix@noc.example.net, subject “Problem: Unavailable by ICMP ping”. Welco trims it to one text of 96 characters: “Welco: [core-sw-1] Unavailable by ICMP ping, severity High at 12:20 AM. Reply STOP to opt out.”

Text received: Welco: [core-sw-1] Unavailable by ICMP ping, severity High at 12:20 AM. Reply STOP to opt out.

Characters229961 credit

Animation: the alert email "Problem: Unavailable by ICMP ping" is trimmed into one text: "Welco: [core-sw-1] Unavailable by ICMP ping, severity High at 12:20 AM. Reply STOP to opt out."

See the full setup on the Zabbix SMS alerts page. A credit union IT team gets its overnight failures as texts this way.

Monitoring tools where tmomail.net addresses live

The address sits wherever the tool keeps its contacts. These are the usual spots to look.

Frequently asked questions

Did T-Mobile ever announce the end of tmomail.net?

Not that anyone has found. Services that track gateways report the slowdown in November 2024 and the stop in December 2024, with no formal notice from T-Mobile. That's why the change caught so many teams off guard. Treat the gateway as closed.

My mail server says the message was accepted. Why no text?

Accepted only means T-Mobile's mail server took the message. Reports say it is then dropped without a bounce, so your server never hears about it. Only a real phone receiving a real text proves delivery. Welco shows that in a delivery report.

Does Metro by T-Mobile use the same gateway?

Yes. Metro by T-Mobile phones were reached through the same tmomail.net domain, so they lost email-to-text at the same time. With Welco, the phone's brand doesn't matter. The alert is texted to the number, and its owner confirms it once with YES.

Could tmomail.net start working again?

We wouldn't count on it. There was no notice when it stopped, so there would likely be none if it changed again. A path that can fail without telling you isn't safe for alarms. Move the alerts and remove the old address.

What does Welco cost compared with the free tmomail.net gateway?

More than free, but there are no per-user fees, no agent to license and no setup fee. Each text uses message credits, and rules that text only DOWN and CRITICAL keep the count low. Test it on one monitoring tool during the 7-day free trial, which includes 15 credits.

How will I know a Welco alert actually reached the phone?

Welco keeps a delivery report for every text. It shows whether each text was delivered and, if not, why, in plain English. Common reasons include a phone that is switched off or a landline number that can't take texts.

Will a flapping host flood the T-Mobile phone with texts?

Not if you set it up for that. Duplicate protection stops one alert email from texting a phone twice, and alarm flood control limits bursts. Rules can keep recovery emails out of texts, so good news wakes nobody. Each new problem email still becomes a text.

Give your T-Mobile on-call phone its alerts back

One address change per tool, and a report that shows each text. View plans or start free.

7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing