July 13, 2026 · 8 min read

Email-to-text stopped working: replacements for system alerts (2026)

For two decades, the free carrier gateways were the duct tape of IT alerting: point a server, UPS, alarm panel, or datalogger at 5551234567@vtext.comand its email arrived as a text. That era is over. T-Mobile’s gateway went dark in late 2024, AT&T shut its down permanently in June 2025, and Verizon has published a final shutdown date of March 31, 2027 — with heavy spam-filtering already dropping messages today.

The frustrating part: nothing on your side broke. The device still sends its alert email exactly like it always did. There’s just no longer anything on the other end turning it into a text.

Carrier email-to-text status (2026)

CarrierGatewayStatusDetail
T-Mobile / Metro@tmomail.netDeadStopped resolving ~Dec 2024 — no formal notice
AT&T / Cricket / FirstNet@txt.att.net · @mms.att.netDeadPermanently shut down Jun 17, 2025
Verizon@vtext.com · @vzwpix.comDyingHeavily filtered now; full shutdown Mar 31, 2027
Google Fi@msg.fi.google.comWorkingStill documented — the most reliable holdout
US Cellular@email.uscc.netUncertainReported working; future unclear after T-Mobile acquisition
Boost Mobile@sms.myboostmobile.comWorkingReported working — treat as temporary

Status as of July 2026. The carriers killed these gateways to fight spam — the survivors can vanish without notice, exactly as T-Mobile’s did.

Your real options, compared

Every replacement falls into one of four buckets. Which one fits depends on whether the alert has to be an actual SMS, and how much engineering you want to own.

1. Push-notification apps (Pushover, ntfy, and friends)

Cheap and reliable — ifevery recipient installs and maintains an app, and your device can speak the service’s API instead of (or via) email. Push is a good fit for a technical team’s own phones. It fails for everyone else: property owners, on-call rotations with personal phones, or anyone who won’t keep an app logged in with notifications enabled.

2. SMS APIs (Twilio, Telnyx, and similar)

The most flexible option and the most work: you write and host the glue that receives your device’s email or webhook and calls the API, then register your traffic for A2P 10DLC, manage opt-outs, and monitor deliverability. Sensible when messaging is a core part of your product. Overkill for “the sump pump should text me.”

3. Bulk-SMS platforms with an email-to-SMS feature

Business texting platforms aimed at marketing and customer messaging sometimes include an email-to-SMS bridge. They work, but pricing is usually per-seat or credit-based and the alerting use case is an afterthought — no per-device addresses, no duplicate-alert throttling, no alert parsing.

4. Purpose-built email-to-SMS alert forwarding

The drop-in replacement for what the carriers took away: your device keeps emailing, a service like EmailToTxtreceives it at a unique per-device address, cleans up the alert, and delivers a real SMS over registered, compliant A2P messaging — with consent recording, STOP/HELP handling, rate limits, and duplicate suppression built in. The only change on your side is the recipient address in the device’s email settings.

Migrating: the 10-minute version

  1. Inventory what was emailing a carrier gateway — grep your configs and mail logs for vtext.com, txt.att.net, tmomail.net, and vzwpix.com.
  2. Create an endpoint for each device or system and get its unique inbound address (see our device setup guides).
  3. Swap the recipient address in each device’s email/SMTP alert settings. Nothing else changes — same mailbox, same events.
  4. Add the phone numbers that should receive each device’s alerts, with the recipient’s consent, and send a test event.

Systems that can’t authenticate to a modern mailbox (very old firmware, no TLS) can usually still send through a local smarthost relay — configure the relay once, point the fleet at it, and have it forward to your alert addresses.

Frequently asked questions

Why did my system alerts stop arriving as texts?
Almost certainly because the carrier email-to-SMS gateway your system emailed (like number@tmomail.net or number@txt.att.net) was shut down. The device or software is still sending email — there is simply nothing on the other end converting it to a text anymore. Check the carrier status table above for exactly when your gateway died.
Is vtext.com still working in 2026?
Barely. Verizon has published a full shutdown date of March 31, 2027, and messages are already heavily spam-filtered. Do not build or keep anything important on it — migrate before the deadline.
What is the cheapest replacement for a carrier email-to-text gateway?
If the recipient is technical and willing to install an app, push services are cheap or free. If the alert must arrive as a real SMS on any phone with no app, a purpose-built email-to-SMS forwarding service is the least-effort replacement — your device keeps sending the same email, only the address changes.
Can I just use a free SMTP-to-SMS trick instead?
The surviving free gateways (Google Fi, US Cellular, Boost) only deliver to phones on those specific carriers, can silently spam-filter automated mail, and can disappear at any time like the big three did. They are fine as a stopgap, not as the thing your monitoring depends on.
Why not just use my monitoring tool’s built-in SMS integration?
If your platform supports an SMS provider natively and you are comfortable managing API credentials, A2P registration, and per-message billing, that is a solid option. Most appliances, UPS cards, alarm panels, and legacy tools only speak SMTP though — email is the one notification method nearly everything supports.
Does EmailToTxt work with any device?
Anything that can send an email over SMTP: servers, NAS units, UPS network cards, alarm panels, building controls, dataloggers, printers, and monitoring software. You point the device’s existing email-alert setting at your unique EmailToTxt address and each alert arrives as a clean text.

Get camera alerts back on your phone

NVRtxt turns your NVR’s alert emails into clean SMS texts to any phone, over compliant 10DLC messaging. Point your recorder at a unique address and you’re done.