Email to SMS Gateway: What Still Works in 2026

An email to SMS gateway converts an email into a text message. For twenty years the free way to do it was the carrier address trick — send an email to 5551234567@txt.att.net and the carrier delivered it as an SMS. That era is over. AT&T shut down its email-to-text gateway on June 17, 2025, Verizon has announced the wind-down of vtext.com and vzwpix.com with completion expected by March 31, 2027, and the remaining carrier gateways are best-effort at best. What still works in 2026 is email-to-SMS delivered over registered A2P routes — either through an SMS API or through a carrier messaging service that accepts your alerts and sends them from a registered number.

If your monitoring stack, ticketing system, or on-call rotation still emails texts to carrier addresses, this guide covers how the legacy gateways worked, why they are being retired, what replaces them, and how to migrate before the next silent failure. SIPNEX is an FCC-licensed carrier that provides SMS and MMS messaging on registered A2P routes, and much of the traffic moving off email-to-text is exactly this: ops alerting built a decade ago and never touched since.

How the legacy email-to-text gateways worked

The carrier email-to-SMS gateway was an SMTP-to-SMS bridge. Each major US wireless carrier published a domain — AT&T used txt.att.net for SMS and mms.att.net for MMS, Verizon used vtext.com and vzwpix.com, T-Mobile used tmomail.net. You addressed an email to the recipient’s ten-digit number at the carrier’s domain, the carrier’s mail server accepted it, stripped it down to the subject and body, truncated it to fit an SMS, and delivered it to the handset as a text.

The appeal was obvious. It was free, it required no API integration, and every system that could send email could suddenly send texts. Nagios, Zabbix, cron jobs, UPS monitoring cards, building alarm panels, ticketing systems — anything with an SMTP client got SMS alerting by adding one email address to a notification list. No account, no credentials, no per-message bill.

That same openness is what killed it. The gateway had no sender authentication, no consent verification, no delivery receipts, and no way for the carrier to distinguish a legitimate server alert from a phishing blast. You never knew whether a message arrived — the gateway accepted the email and everything after that was invisible.

Why the gateways are dying

Three forces converged on the email-to-text gateways, and they map directly to why the A2P messaging framework exists.

Spam and abuse. An open, free, anonymous email-to-SMS bridge is a spammer’s dream. Bulk phishing and smishing campaigns funneled through the gateways for years, and carriers responded with increasingly aggressive filtering that caught legitimate alerts along with the junk. Long before any formal retirement, delivery through the gateways had become erratic — delayed by minutes or hours, silently dropped, or truncated unpredictably.

No authentication or registration. Modern US business messaging runs on registered identity. Traffic from ten-digit numbers requires brand and campaign registration through The Campaign Registry — the full process is in our step-by-step A2P 10DLC registration guide — and carriers route registered traffic preferentially while filtering everything else. An email arriving at a gateway address carries none of that: no registered brand, no campaign, no attestable sender. Structurally, gateway traffic is exactly the unregistered traffic the framework was built to squeeze out.

Formal retirements. AT&T discontinued its email-to-text and text-to-email service on June 17, 2025, per its retirement notice, covering txt.att.net, mms.att.net, and its Cricket domains. Verizon has published notice that email to vtext.com and vzwpix.com is shutting down, with the wind-down anticipated to complete by March 31, 2027 — and warns some senders may lose access earlier. T-Mobile’s tmomail.net gateway is widely reported as degraded and unreliable for automated traffic. The direction is one-way: no carrier is investing in these bridges, and each retirement strands every alert list still pointing at that domain.

The failure mode is the dangerous part. Nothing bounces. Your monitoring system reports the notification email as sent, the gateway address silently swallows it, and the first sign of trouble is an incident nobody was paged for.

What replaces email-to-text for alerting

The replacement is not another free gateway — it is delivery over a registered A2P route, reached one of two ways.

An SMS API. Your monitoring or ticketing system calls an HTTP endpoint instead of sending an email, and the provider delivers the message from a registered number with real delivery receipts. Most modern monitoring platforms have native integrations or webhook support that makes this a configuration change rather than a development project. Our SMS API explainer covers how the request flow works and how to evaluate providers on deliverability.

A carrier messaging service with an email-to-SMS bridge on registered routes. Several providers offer hosted email-to-SMS bridges on registered routes; SIPNEX delivers alert traffic as SMS from your registered numbers via its messaging platform — so systems that can only speak SMTP or a simple webhook still get carrier-grade delivery. The difference from the old gateways is everything that happens after ingestion: the message leaves from a number tied to a registered brand and campaign, it rides registered A2P routing instead of a spam-filtered side door, and you get delivery status instead of silence.

Either way, the alerts themselves need a registered home. Operational alerts to your own staff are a standard campaign use case, registration fees are modest — a one-time brand fee plus a small per-campaign fee, itemized in the registration guide — and SIPNEX handles the TCR submission for messaging customers. Fees and carrier rules shift periodically; our A2P 10DLC news tracker logs the changes as they land.

Migrating monitoring alerts off email-to-text

If your alerting still emails carrier addresses, here is the migration path.

1. Inventory the senders. Grep your monitoring configs, ticketing notification rules, cron scripts, and hardware appliances (UPS cards, alarm panels, environmental sensors) for carrier gateway domains — txt.att.net, vtext.com, tmomail.net, and the rest. The appliances are the ones teams forget; some can only send email and will need the bridge approach rather than an API.

2. Pick the route per system. Systems with webhook or API support move to direct API delivery. SMTP-only systems point at a provider-hosted email-to-SMS bridge that delivers over registered routes. Do not stand up your own unauthenticated relay — you would be rebuilding the problem.

3. Register the traffic. One brand registration for your business, plus a campaign covering operational notifications. Numbers attach to the campaign, and alerts then send from those registered numbers. If the recipients are your own on-call staff, your provider can typically document staff consent as the opt-in method during campaign setup.

4. Cut over with verification. Switch one alert class at a time, confirm delivery receipts show delivered — not just sent — and only then retire the gateway addresses. Keep email or push notifications as a parallel channel for critical pages; SMS should be a leg of your escalation policy, not the whole policy.

5. Watch the delivery reports. The single biggest upgrade over the legacy gateways is that failure is now visible. Alert on your alerting: if delivery receipts stop coming back, you want a page about it.

Frequently asked questions

The old gateways died because nobody owned delivery. On a registered route, someone does. SIPNEX provides SMS and MMS messaging on registered A2P routes — alerting and notifications from the same DIDs as your voice, A2P 10DLC registration handled on your behalf, carrier surcharges itemized, and delivery receipts on every message. Move your alerts to a registered route or call (833) 665-2220.