For years, there was a handy trick for sending text messages from an email account. You would address an email to something like 5551234567@txt.att.net, and it would arrive on the recipient’s phone as a text. Monitoring systems, home automation setups, and small businesses relied on it.
If yours suddenly stopped working, here is the short answer: the carriers shut the gateways down. This article explains what happened, how to confirm it is the cause, and what to use instead.
The Gateways Are Gone
The free email-to-SMS gateways run by the major US carriers have been retired. The timeline, based on carrier announcements and industry reporting:
- T-Mobile took its @tmomail.net gateway offline around December 2024, describing it as a legacy system.
- AT&T closed @txt.att.net and @mms.att.net on June 17, 2025. Messages sent to those addresses now fail silently.
- Verizon began phasing out @vtext.com and @vzwpix.com, with a full shutdown scheduled for March 2027, though many senders report delivery has already dropped to near zero.
The reason is not mysterious. These gateways were free, unauthenticated, and open to anyone, which made them a favorite channel for spam and phishing. Rather than rebuild them under modern messaging regulations, the carriers retired them. They are not coming back.
A note on dates: carrier shutdown schedules can shift, so treat the Verizon timeline as current as of this writing and check Verizon’s own support pages for the latest status.
How to Confirm the Gateway Is Your Problem
Before you rebuild anything, make sure the dead gateway is actually what broke. Run through these checks.
Check which gateway address you are using. Look at the actual recipient address in your script, automation, or email client. If it ends in @txt.att.net, @mms.att.net, @tmomail.net, or @vtext.com, you have found the problem.
Confirm the recipient’s carrier. People switch carriers and keep their numbers. An address that worked when the recipient was on Verizon may fail now that they ported to T-Mobile. But given the shutdowns above, a carrier change is the less likely explanation these days. The gateway itself is the prime suspect.
Check for silent failure. The cruelest part of this breakdown is that it fails silently. Your email client shows the message as sent. There is no bounce, no error, no delivery report. The message simply never arrives. If your “sent” folder looks healthy but nobody is receiving texts, that pattern matches a dead gateway exactly.
Rule out email-side problems. If you are unsure, send a test email to a normal email address from the same account or script. If that arrives fine, your email sending works and the gateway is the broken link.
Check message length and formatting. The old gateways typically truncated long messages or split them awkwardly. If some messages arrive but long ones do not, formatting may be part of the issue, though with the gateways retired, this is now a secondary concern.
What to Use Instead
The good news is that the replacements are better than what they replace: more reliable, with delivery confirmation and proper formatting.
An SMS API with 10DLC registration. This is the professional replacement. Services like Twilio, Plivo, and Telnyx let you send texts programmatically from your applications, with delivery receipts and proper throughput. For US messaging, you will need to register your brand and campaign under the 10DLC system, which is the framework carriers now require for application-to-person texting. Our SMS API guides hub covers 10DLC registration, troubleshooting, and common setup problems in detail.
Your phone’s built-in messaging. If you were using email-to-text as a personal convenience, for example to text yourself reminders from your computer, most desktop operating systems now sync with your phone’s messaging app directly. That covers the personal use case with no gateway needed.
A business texting platform. If you were sending appointment reminders or notifications to customers, a proper business texting tool gives you scheduling, templates, opt-out handling, and compliance features the old gateway never had. Our free tools page includes utilities that help with campaign setup, like cost estimation and quiet-hours checking.
Push notification services. For system alerts and monitoring, which was one of the biggest uses of email-to-text, dedicated push services are more reliable and give you acknowledgment that the alert was seen.
Migrating Without Breaking Things
If you have scripts or systems still pointed at the old gateways, here is a sane migration order.
First, inventory every place the gateway addresses appear: scripts, monitoring configs, cron jobs, documentation. The addresses tend to hide in places people forget.
Second, pick your replacement and set it up in parallel. Get the SMS API account created, register your 10DLC campaign, and test with a small number of messages before touching production systems.
Third, swap the sending code. Most email-to-text integrations are a single function or a single mail call, so the change is usually small. The bigger work is in the new provider’s setup, not in your code.
Finally, add delivery monitoring. One advantage of doing this properly is that you get delivery receipts. Set up logging or webhooks so the next failure is loud instead of silent.
Before you start sending at any real volume, run through a pre-send campaign checklist to make sure consent, opt-outs, and sending windows are handled.
Frequently Asked Questions
Why did my email to text stop working all of a sudden?
The most likely reason is that the carrier retired its email-to-SMS gateway. T-Mobile, AT&T, and Verizon have all shut down or are shutting down these free gateways because they became major spam vectors. Messages to the old addresses now fail silently.
Is there a free email to text gateway that still works?
Not reliably. The major carrier gateways are gone or going, and the smaller ones that remain are unreliable and unsupported. For anything important, use a proper SMS API instead.
Can I still text Verizon numbers by email?
Verizon’s @vtext.com gateway is being phased out with a full shutdown scheduled for March 2027, and delivery is already unreliable. Do not build anything new on it.
What is the cheapest replacement for personal use?
For personal reminders and notes to yourself, use your phone’s built-in messaging sync with your computer. It is free and does not depend on any carrier gateway. For business or automated use, a pay-per-message SMS API is the standard replacement.
Do I need 10DLC registration to send texts from my app?
For application-to-person messaging to US numbers, yes, carriers now expect proper 10DLC registration. Unregistered traffic gets filtered or blocked. The registration process involves verifying your business and describing your messaging use case.