Why Your Email-to-SMS Stopped Working (+ the Easy New Solution)

Why Your Email-to-SMS Stopped Working (+ the Easy New Solution)

· by Sam Greenspan

The carrier email-to-SMS gateways that sysadmins relied on for years are dead. Here’s what happened, why carriers pulled the plug, and how to fix it in five minutes.

At some point in the past few years, your email-to-SMS alerts stopped working, likely without any warning. Then one day your server went down, your phone didn’t buzz, and you found out three hours later when a customer complained.

You’re not alone. The carrier email-to-SMS gateways that sysadmins and DevOps teams relied on for years are dead. number@vtext.com, number@txt.att.net, number@tmomail.net — dead.

Here’s what happened and why carriers pulled the plug. Also, here’s how to fix it in about five minutes.

Email to SMS: Table of Contents

The SMS Gateway Extinction (2022–2025)

The shutdown didn’t happen all at once. It was a slow-motion collapse, carrier by carrier, with minimal warning.

Sprint went first in early 2022, but their shutdown went largely unnoticed because Sprint was already being absorbed into T-Mobile.

Boost Mobile followed shortly after.

T-Mobile (@tmomail.net) became increasingly unreliable throughout 2024. Messages would arrive… sometimes. Then in December 2024, the T-Mobile email to text gateway went fully offline.

Verizon (@vtext.com) technically still exists as of this writing, but “exists” is a stretch. New signups are blocked. Delivery is inconsistent at best. Verizon’s own documentation tells businesses to stop relying on it. If your alerts still work through vtext.com, consider yourself lucky — and start planning your migration off of Verizon’s email to text alerts now.

AT&T (@txt.att.net, @mms.att.net) pulled the plug on June 17, 2025. Their support page announced it with no fanfare: “Say goodbye to email-to-text and text-to-email.” That’s it. No transition guide, no recommended alternatives, no apology for the workflows that broke.

The pattern here matters: none of these shutdowns came with advance notice or migration paths. Each carrier quietly updated a support page somewhere, and millions of automated systems broke.

Why Carriers Killed Email-to-SMS

It’s easy to assume carriers are just being difficult or that this is part of the broader trend of corporations cutting anything and everything free. The reality is more nuanced, even though it doesn’t make your broken alerts any less frustrating.

The spam problem became untenable

These gateways were designed when the internet was smaller and more trusting. (I actually remember using one of these back in 2003 for the first time. 2003!)

The premise was simple: anyone with an email client could send a text to any phone number. No authentication, no verification, no accountability.

Spammers, as usual, ruined everything. The gateways became firehoses of junk: phishing attempts, scams, and endless spam flooding through an unauthenticated channel that carriers couldn’t effectively police.

A2P 10DLC changed the regulatory landscape

Starting in 2023, US carriers began aggressively enforcing A2P (Application-to-Person) 10DLC registration.

The mandate is pretty simple:

  1. All business SMS traffic must be registered with The Campaign Registry (TCR)…
  2. Associated with a verified brand…
  3. And compliant with opt-in/opt-out requirements.

The old email gateways existed completely outside this framework. They were an unauthenticated front door into the SMS network. That’s exactly the kind of compliance hole that 10DLC was designed to close.

By late 2024, carriers were blocking unregistered A2P traffic entirely. The email gateways didn’t have a built-in mechanism for registration or verification.

(And the carriers weren’t particularly incentivized to build one. After all, email-to-text was a free service. Maybe it was worth something back when texts cost 10 cents each, but today? All downside risk, zero profit.)

Liability and consumer protection

Every phishing text that slipped through an email gateway was a potential lawsuit, a regulatory complaint, a news story about carrier negligence.

The risk calculus eventually tipped: maintaining these gateways created more liability than the modest amount of goodwill they generated. And again, they weren’t making any money for the carriers.

What this wasn’t about

The big cell phone industry buzzword in recent years has been RCS. That’s Rich Communication Services; think group chats, photo sharing, emoji responses to messages.

You’ll hear RCS (Rich Communication Services) mentioned as “the future of messaging.”

For consumer texting, that’s probably true. But RCS solves a completely different problem than email-to-text.

There’s no RCS workflow where you email an address and someone gets a notification. That’s not on the roadmap. Carriers didn’t kill email-to-SMS because something better replaced it, they killed it because they couldn’t control it.

Why SMS is still the best channel for alerts

For system notifications, text messages are still untouchable.

Universal. Texts work on every phone made in the last 25 years. No app required. No OS version dependencies. Even if you work with a hipster sysadmin who uses a flip phone, they can get texts.

Reliable on degraded connectivity. SMS can punch through when data is spotty but cell signal exists. When you’re in an area with poor connectivity, texts are generally the only things that still come through.

Immediate and interruptive. Push notifications compete with every other app on the phone. SMS cuts through. There’s no notification settings to misconfigure, no badge counts to ignore.

Battle-tested. Decades of infrastructure hardening have added up to be perfect for this use case. The SMS network has survived everything thrown at it.

When your production database is down at 3 AM, you need a message that you can’t and won’t miss. SMS is purpose-built for that.

What You Might’ve Already Tried

If you’ve been dealing with broken email-to-SMS alerts, there’s a chance you’ve explored some alternative email to text options. Here’s why the obvious options don’t quite fit.

Twilio, Vonage, or API-based SMS providers

These work great if you want to build your own system, manage API keys, handle authentication, and navigate A2P 10DLC registration yourself. (No, you can’t skip A2P 10DLC, your messages won’t be delivered without it.)

For a software product with SMS baked into its architecture, they’re the right choice.

PagerDuty, Opsgenie, or incident management platforms

These are enterprise-grade solutions for enterprise-grade problems. If you’re running a large SRE team with complex on-call rotations, escalation policies, and incident workflows, these make sense.

If you’re a solo founder, a small DevOps team, or someone who just needs to know when a backup fails? You’re paying for 97% of features you’ll never touch, and you still have to reconfigure every alert source to point at their APIs.

Zapier, n8n, or automation platforms

With every layer of abstraction, you add another potential point of failure. I’ve tried no code, you’ve tried no code… there’s a reason both of us no longer rely on no code.

In this situation, you still need an SMS provider underneath, you’re adding latency, and you’ve now got one more system to monitor and maintain.

The fundamental mismatch

All of these solutions require you to change how your systems generate alerts.

But you don’t want to rebuild your alerting architecture. You already have systems that can email. Servers, NAS devices, monitoring tools, cron jobs — they all know how to send email.

That’s the interface that exists.

You just need those emails to become texts.

Email-to-SMS, Rebuilt for 2026 and Beyond

So… this is exactly why we built text.email: to be a modern replacement for the carrier gateways, designed specifically for alert notifications.

How it works

  1. Sign up with your email address
  2. Pick your plan
  3. Choose a private keyword (your subdomain)
  4. Send emails to number@yourkeyword.text.email

That’s it. Any email sent to that address becomes an SMS, delivered in seconds.

Works with everything that sends email

  • Linux CLI tools: mailx, sendmail, msmtp, ssmtp
  • Monitoring systems: Prometheus Alertmanager, Nagios, Zabbix, Datadog
  • Uptime monitors: UptimeRobot, Pingdom, Better Uptime, StatusCake
  • NAS devices: Synology, QNAP, TrueNAS
  • CI/CD pipelines: GitHub Actions, Jenkins, GitLab CI
  • Legacy systems: That ancient PHP script from 2009? If it can call mail(), it works.

Why it’s different

No code, no API, no SDKs.If your system can send email, it can send SMS. The integration is a config change, not a development project.

A2P 10DLC compliant. We handle the compliance side so you don’t have to navigate TCR, brand verification, or campaign registration yourself. Your messages route through properly verified channels.

Carrier-agnostic delivery. Works regardless of which carrier the recipient uses. No more guessing whether someone is on Verizon or T-Mobile or trying to maintain multiple gateway addresses.

Private by default. Your keyword means only emails sent to your subdomain are delivered and billed to your account. Random senders can’t rack up charges on your behalf and the carriers’ old spam problem is gone.

From the GMass team. We’ve been in the email sending platform business since 2015, sending more than 9 billion messages for 400k+ users. Deliverability and reliability aren’t challenging for us or new to us.

What text.email is for

What text.email is not for

text.email is a one-way notification layer.

It’s not a marketing platform, not a mass-texting service, not an appointment reminder service, and not a two-way conversation tool.

It’s built for alerts; fast, reliable, one-way notifications when something needs your attention now.

Email to SMS Stopped Working — But You Didn’t

The carrier gateways aren’t coming back.

But email-to-SMS as a concept doesn’t have to die with them. The workflow (email goes in, text comes out) is too useful to abandon. It just needs infrastructure that’s built for the current regulatory environment and messaging landscape.

That’s what text.email provides: the same simple workflow you relied on before, backed by compliant, multi-carrier delivery.

Try text.email free

Send an email to
your-number@text.email
and receive it as a text in seconds. No signup required.