After the AT&T Email to Text Shutdown — What’s the Best Alternative?

AT&T killed txt.att.net and the other carriers followed. Here’s why the email-to-SMS gateways are gone for good — and the best alternatives for your server alerts.

The AT&T email to text shutdown is over. The txt.att.net gateway is gone.

If you’ve been troubleshooting why your server alerts aren’t hitting your phone anymore, that’s the answer: AT&T pulled the plug on their email-to-SMS service, and they’re not the only ones.

Verizon’s vtext.com, T-Mobile’s tmomail.net, and every similar service from every other carrier have met the same fate.

The era of free carrier-provided email-to-text gateways is over. Here’s why it happened and alternatives you can use instead.

AT&T Email to Text Shutdown: Table of Contents

• How txt.att.net Worked
• Why AT&T and the Other Carriers Killed Email-to-SMS
• What Are Your Email-to-SMS Options Now?
• Why text.email Makes Sense as an AT&T email-to-SMS Replacement
• With AT&T Email to Text Gone, Are You Ready to Migrate Your Email-to-Text Alerts?

How txt.att.net Worked

The setup was almost shockingly simple: send an email to yournumber@txt.att.net, and AT&T would deliver it as an SMS to your phone.

This made it perfect for infrastructure alerting. Down time alerts, cron jobs, backup scripts, monitoring systems — anything that could fire off an email could send you a text.

You didn’t need to integrate anything. You just pointed your alerts at an email address and forgot about it.

A lot of sysadmins have been running on this setup for 10, 15, even 20 years. It worked… until one day it didn’t.

Why AT&T and the Other Carriers Killed Email-to-SMS

Here’s why the carrier gateways no longer exist.

Reason #1: Spam

The short answer: spam ruined it for everyone.

These gateways had no authentication. Anyone who knew the address format could send a text to any AT&T customer.

Spammers eventually exploited this at scale with phishing links, scam messages, and bulk garbage flooding through what was essentially an unguarded door.

Reason #2: The carriers weren’t incentivized to fix it

The gateways were free. They were a legacy feature from (sigh) a different era.

Free services that cause a lot of headaches? Those are long gone from every business.

And the carriers had zero financial motivation to secure a service that generated no revenue.

Reason #3: The regulatory pressure

When text spam really started getting out of control, the carriers and regulators realized they needed to set up some guardrails.

Those came in the form of the Campaign Registry and new compliance regulations.

A2P 10DLC (application-to-person 10-digit long code) rules now require all automated SMS traffic to be registered and verified. The carrier gateways couldn’t comply with this; they were anonymous by design.

There was no way to retrofit sender verification onto a system built around “any email address can send to any phone number.”

None of these factors are reversing. The gateways are dead for good.

What Are Your Email-to-SMS Options Now?

Even though the carriers shut down their gateways… you still need your alerts.

Here are your options.

Drop-in replacement for email-to-text

text.email is the option that actually mirrors what you lost with AT&T email to text shutting down.

Send an email, receive an SMS.

It’s the same workflow you’re used to, but built on compliant infrastructure that isn’t going to disappear. There are no APIs required, no code changes, and no new integrations. (More on this below.)

The market has a few other answers, but they come with tradeoffs.

Building your own system

Twilio, Vonage, and other API-based SMS platforms are made for programmatic texting.

They’re well-documented, and scale to millions of messages. They also require actual development work.

You’ll need API keys, authentication, and custom code for every system that currently just sends email. That’s great if you’re building an app. It’s overkill (both in time, cost, and system maintenance) if you just need to know when your NAS backup fails.

Incident management platforms

PagerDuty, Opsgenie, and other incident management tools are built for on-call alerting with escalation policies, schedules, and incident tracking.

They’re also built for large teams with large budgets. If you’re a one-person operation or a small team that just needs “text me when something breaks,” you’re paying for a lot of functionality you won’t use.

Push notifications

Pushover, Ntfy, and other push notification services are relatively cheap and easy to set up.

The tradeoff: they’re app-based, not SMS. You need their app installed, and push notifications don’t have the same “wake you up at 3 AM” reliability as a text message. Phones throttle push notifications. They get grouped, silenced, delayed — while SMS cuts through.

Why text.email Makes Sense as an AT&T email-to-SMS Replacement

The reason the old gateways worked so well was their incredible simplicity and functionality.

Email is universal; pretty much every server, every script, and every application can send it.

Text messages are universal; every phone can receive them.

That made email-to-text the path of least resistance — and the most reliable path — for alerting.

text.email preserves that entire workflow. You point your alert emails to yournumber@yourkeyword.text.email, and it shows up immediately as a text.

Your existing scripts, cron jobs, and monitoring configs just need an address change.

What’s different from AT&T’s old email-to-SMS gateway is the backend.

text.email is A2P 10DLC compliant. The private keyword system ties messages to your account, which solves the spam problem that killed the carrier gateways. Nobody can send texts through your keyword but you.

Monthly and annual plans include 200 SMS messages per month. For alerting use cases (where you’re hopefully sending very few messages because nothing’s constantly on fire) that covers most people.

With AT&T Email to Text Gone, Are You Ready to Migrate Your Email-to-Text Alerts?

AT&T email to text is gone — they aren’t bringing txt.att.net back. The regulatory environment won’t allow it, and they have no financial incentive to try. The same goes for Verizon, T-Mobile, and all the other carriers.

That’s the bad news.

The good news: the replacement doesn’t require rethinking your entire alerting stack. text.email works the same way the old gateways did, minus the design flaw that got them shut down. And it takes about two minutes to set up.

Subscribe to text.email. Find everywhere you’re sending to txt.att.net. Change it to yourkeyword.text.email. Test it. You’re done.

It’s a config change, or at worst, a find-and-replace in a handful of scripts.