Stop the Silent Failures

For engineers maintaining alert systems pointed at vtext.com. The addresses, the status, why the model broke, and the one-line replacement.
Verizon’s SMS gateways still partially work in 2026, but the consumer-era email-to-text path is ending. AT&T’s gateway shut down in June 2025, T-Mobile silently stopped delivering in late 2024, and Verizon has set a hard sunset of March 31, 2027.
This guide covers the exact addresses Verizon published, including the legacy domains that no longer work, where every major US carrier gateway stands today, and the five reasons they are being retired rather than modernized. It closes with the one-line config change that keeps alert systems firing on a compliant email-to-text service.
TL;DR
For reference, here is every form Verizon SMS address ever published:
| Format | Type | Status (2026) |
|---|---|---|
<10-digit>@vtext.com | SMS, text only | Phasing out, intermittent failures |
<10-digit>@vzwpix.com | MMS, text + image/video | Phasing out, intermittent failures |
<10-digit>@message.alltel.com | Legacy Alltel | Discontinued (Alltel was absorbed by Verizon in 2008) |
<10-digit>@vmobl.com | Legacy / regional | Discontinued |
The Verizon email to SMS gateway used a single vtext.com address format, written as number@vtext.com or 10digit@vtext.com, where the number is the recipient’s 10 digit mobile number. New to how SMS gateways work? Our SMS gateway guide covers the concept before you dig into Verizon’s specifics.
The active format most scripts and apps still use is 1234567890@vtext.com. Note: no plus sign, no country code, no dashes, just the 10 digits and the domain. This format predates E.164 and is one reason the gateways behave inconsistently with non-US numbers.
Verizon is retiring @vtext.com and @vzwpix.com because the gateways were built as open, unauthenticated relays that current carrier compliance rules cannot accommodate. The phase-out began in late 2024 and completed on March 31, 2027. Five factors drove the decision.
Anyone on the internet could email any Verizon mobile number at @vtext.com with no account and no sender verification. Because the From address on an email is trivially spoofed, an attacker could send phishing texts while masking their identity, and the message landed on the handset looking like an ordinary SMS.
Attackers used this to send phishing texts, known as smishing, at volume. The gateways became one of the cheapest ways to reach a US mobile phone anonymously.
The gateways predate 10DLC and the modern application-to-person messaging rules. There was no mechanism to verify who was sending, register what campaign the traffic belonged to, or record whether the recipient had consented. Carriers now require a registered business identity, a registered campaign, and opt-in records for every business message sent to a US mobile number. The email gateway model cannot supply any of the three.
Verizon responded to the abuse by filtering gateway traffic aggressively rather than rebuilding it. Legitimate alerts started getting blocked or delayed with no bounce and no error code.
A monitoring system would log the email as sent while the text never reached the phone. That failure mode is why the gateway became unusable for alerting long before the announced sunset date, and it is the single most reported symptom among teams still pointed at vtext.com.
The specific filters, the error codes they return, and Verizon’s own published notice are documented.
Verizon was operating a free relay whose dominant traffic was abuse. The underlying systems were built for a consumer use case that no longer exists and were never designed for current security or compliance expectations. Retiring the service was cheaper than rebuilding it to a standard the carriers themselves now enforce.
Business SMS has consolidated onto registered paths: 10DLC for standard business numbers, short codes for high volume, and verified sender identities across the ecosystem. Each requires traceability, consent, and campaign registration. The open email-to-SMS model is not a deprecated version of that framework. It is architecturally incompatible with it, which is why no carrier chose to modernize its gateway instead of closing it.
| Carrier | Historic SMS gateway | Historic MMS gateway | Status now |
|---|---|---|---|
| AT&T | txt.att.net | mms.att.net | ❌ Permanently shut down June 17, 2025 |
| T-Mobile | tmomail.net | tmomail.net | ❌ Quietly stopped Nov–Dec 2024 (no announcement) |
| Verizon | vtext.com | vzwpix.com | ⚠️ Phasing out through March 31, 2027, works intermittently |
| Sprint | messaging.sprintpc s.com | (no separate MMS) | ❌ Discontinued after T-Mobile merger (2020) |
| US Cellular | email.uscc.net | (no separate MMS) | ⚠️ Inconsistent, limited public communication |
| Cricket | mms.cricketwireles s.net | (combined) | ❌ Largely discontinued |
| Boost | myboostmobile.com | (combined) | ❌ Discontinued |
The consumer-era carrier gateways are over. There is no carrier left to switch to, which is why the replacement has to come from outside the carriers entirely. TextBolt runs the same email-to-SMS pattern on a registered 10DLC number, so a single address covers every carrier your recipients are actually on.
<phone>@sendemailtotext.comThe simplest way to replace a vtext.com integration is to swap the destination address. Everything else in your system, the alert template, the trigger logic, the recipient phone number, stays exactly as it is.
Before:
recipient: 2065551234@vtext.com
subject: Server-Prod-3 CPU 94%
body: Threshold exceeded on Server-Prod-3 for 8 min.
After:
recipient: +12065551234@sendemailtotext.com
subject: Server-Prod-3 CPU 94%
body: Threshold exceeded on Server-Prod-3 for 8 min.
That’s the full migration. One line of config. Three differences:
sendemailtotext.com instead of vtext.com.+1 (E.164 format).How It Works
Underneath, TextBolt registers your business as a legitimate sender through The Campaign Registry. The form takes about 10 minutes to fill out during signup; carrier review of the 10DLC registration typically takes 1 to 2 business days. Once approved, every text that hits the recipient’s phone goes through the carrier-trusted 10DLC pipeline, not the deprecated consumer-gateway path that broke.
If you’re moving off vtext.com or vzwpix.com specifically, the Verizon vText to TextBolt migration page is the canonical product reference for the swap.
Swap One Address, Done
Replace @vtext.com with @sendemailtotext.com and your existing systems keep working.
The biggest users of email-to-SMS gateways were never people texting each other. They were systems sending alerts. We see this every day at TextBolt, customers migrating from vtext.com are almost always doing one of these:
mail/sendmail/msmtp, Python smtplib, Node nodemailer, PowerShell Send-MailMessageFor all of these, the migration is the same: change the destination from a carrier gateway to <phone>@sendemailtotext.com. The source system doesn’t need new software, new credentials, or a new integration. It already speaks SMTP, that’s how it was talking to vtext.com in the first place.
Migrating away from Verizon sms email gateway address is usually a quick process. Most teams need about 30 minutes of hands-on work, followed by one to two business days for carrier review. The review happens in the background, and your existing SMS gateway continues working until the registration is approved.
| Step | Time |
| Sign up and complete business verification for 10DLC | About 10 minutes of form filling |
| Carrier review of the registration | 1–2 business days (runs in the background) |
| Replace the vtext.com destination address in your alert system | Less than a minute per system |
| Send the first test alert | Typically delivered within 5 seconds end-to-end |
| Confirm delivery and update documentation/runbook | About 15 minutes |
| Total hands-on time | About 30 minutes |
Teams that have relied on vtext.com for years can usually complete the switch in an afternoon. The only waiting period is the carrier’s 10DLC review, and because the old gateway continues working during this process, there is no gap where critical alerts stop reaching users.
If you have a production alert system pointed at vtext.com today, here is the realistic timeline:
The risk for engineering teams is not the planned 2027 date; it’s the unplanned silent failure between now and then. Off-hours pagers don’t fire. Alarm-panel notifications don’t arrive. The fault is hard to debug because the email was sent successfully from the source system’s point of view. It just never became a text on the other end.
A 10DLC-registered alternative removes the silent-failure mode entirely. Either the text gets delivered, up to 98% on registered 10DLC senders, or you get a clear bounce telling you why.
The migration is a destination-address change in each system that sends alerts. Nothing else in the alert pipeline moves.
my.textbolt.com/signup. Email + phone. Free 7-day trial, 10 test credits, credit card required at signup to prevent spam accounts.+1<your-cell>@sendemailtotext.com. Subject is optional. Body is the message. It should arrive on your phone within a few seconds.<phone>@vtext.com (or tmomail.net, txt.att.net), replace with +1<phone>@sendemailtotext.com. Save.That’s it. Total elapsed time: 30 minutes plus the 1–2 business day carrier review window for the 10DLC registration.
| Plan | Price | Credits / month | Per-message effective cost |
|---|---|---|---|
| Basic | $29 / month | 500 | $0.058 |
| Standard | $49 / month | 1,000 | $0.049 |
| Professional | $99 / month | 2,500 | $0.040 |
| Annual (any tier) | 20% off | same as monthly | varies by tier |
| Enterprise | Custom | 5,000+ | From $0.030 |
One credit = one SMS segment (155 GSM-7 characters, or 70 Unicode characters). A typical 80-character monitoring alert is one credit. Most teams running off vtext.com send fewer than 500 alerts per month, so the Basic tier ($29) covers them comfortably. Pay-as-you-go top-up packs are available for spike months.
See the full TextBolt pricing plans for annual discounts and Enterprise tiers.
By default, TextBolt sends from a shared toll-free number, a pool of carrier-registered numbers managed for SMB customers. For most alerting use cases that is exactly what you want, with instant delivery and no per-number setup.
If your recipients need to see a consistent business number, either for two-way conversations or so the sender stays the same on every message, a dedicated toll-free number is available as an add-on at $45 per year. Same registration, same delivery, your number on every send. Add it from the add-ons page after signup.
Verizon’s web messaging tool cannot replace a gateway for alerting, because it is a consumer feature tied to a single Verizon line rather than a service an application can send through.
The tool at messages.vzw.com, earlier messages.verizonwireless.com, lets a Verizon Wireless customer send texts from a browser instead of a handset. There is no API, no way for a script or a monitoring system to send through it, and it carries rate limits on volume.
If you need to send SMS programmatically from a server, an app, or an alert rule, you need an SMS provider registered with the carriers. That is what 10DLC exists for.
| Feature | Carrier gateway | TextBolt |
|---|---|---|
| Send by email | ✅ Yes | ✅ Yes |
| Send via SMTP from scripts | ✅ Yes | ✅ Yes |
| Recipient’s carrier matters | ✅ You needed the right gateway for each carrier | ❌ Works to all major US + Canadian carriers |
| Registered as a business sender (10DLC) | ❌ No, outside the framework | ✅ Yes, included on every paid plan |
| Carrier deliverability commitment | ❌ Best effort, currently sunsetting | ✅ Up to 98% delivery on registered traffic |
| Delivery confirmation / status | ❌ None | ✅ Real-time status in dashboard |
| Web dashboard for non-engineers | ❌ None | ✅ Yes, compose, contact book, templates, history |
| Two-way replies (recipient texts you back) | ❌ Inconsistent | ✅ Replies come back to the original sender’s email inbox |
| Audit log for compliance | ❌ None | ✅ Yes, every send timestamped and attributable |
| Spam filtering | ❌ Aggressive on unregistered traffic | ✅ Pre-cleared as a legitimate business sender |
| Going to keep working in 2027 | ❌ No | ✅ Yes |
Verizon does offer an official replacement, the Enterprise Messaging Access Gateway (EMAG), a set of APIs that includes an SMTP email-to-SMS interface. EMAG is an enterprise product. It requires registration and provisioning through a Verizon business account, and setup is an API or SMTP integration rather than a same-day change. That makes it a heavier lift for most small and mid-sized teams. TextBolt keeps the simple email-to-text workflow with no integration work, and 10DLC is handled for you. For a full comparison of replacements beyond EMAG, see our Verizon EMAG alternatives guide.
| Verizon EMAG | TextBolt |
|---|---|
| Enterprise API gateway. Requires a Verizon business account and API or SMTP integration, SMS and MMS, you provision 10DLC. | Email-to-SMS. Send to +1<phone>@sendemailtotext.com, SMS only, 10DLC handled for you. |
Try TextBolt Free for 7 Days
See the drop-in replacement send a real text in seconds. Plans start at $29 a month.
Setup is the same regardless of which carrier gateway you’re leaving:
vtext.com or vzwpix.com: swap your alert system’s destination to +1<phone>@sendemailtotext.com after your 10DLC registration clears.txt.att.net: The gateway is fully off since June 17, 2025, so this is the most urgent move. See the AT&T email to text migration page, or email support@textbolt.com for a hand-held migration call.tmomail.net: Texts stop arriving without bouncing, so test first. See the T-Mobile email to text migration page for the address swap.If you have a specific alarm panel, monitor, PBX, or automation tool you want help wiring up, email support@textbolt.com with what you’re using. We’ve migrated customers off vtext.com who were running everything from a Bash script cron-ing once a minute to enterprise SCADA stacks with ten years of alert history. The destination address swap is the same in every case.
The Verizon SMS gateway address (vtext.com and vzwpix.com) had a 20-year run as the default way for systems to text their humans. That era is over. Verizon’s announced full sunset is March 31, 2027, and AT&T’s and T-Mobile’s gateways are already gone.
The Verizon SMS address replacement is the same shape, an email-to-SMS gateway, but built on the 10DLC framework the carriers actually support. It is not an SMS gateway for Verizon numbers alone, which is the practical upgrade. One address reaches every US carrier. The configuration change is one line. The benefit is that it keeps working past 2027.
Migrate before the silent failures find you in production.
Start your migration with TextBolt
Partially. Verizon is in the middle of a phase-out announced through March 31, 2027. Some messages still get through; others fail silently. Business-critical alerts should not depend on it.
Verizon email to text service is shutting down the gateways because they were open, unauthenticated relays that cannot meet current carrier compliance rules. Anyone could email any Verizon number with no account and no sender verification, and the spoofable From address made the gateways a cheap channel for phishing texts.
Modern business SMS requires a registered sender identity, a registered campaign, and opt-in records under 10DLC, none of which the email gateway model can supply. Verizon chose to retire the service rather than rebuild it, with the phase-out starting in late 2024 and full shutdown on March 31, 2027.
There is no maintained free email-to-SMS gateway anymore. The free model died with the carrier gateways. Paid alternatives like TextBolt start at $29/month with a 7-day free trial.
Yes. Every major US carrier email to SMS gateway has closed or is closing. AT&T shut down txt.att.net on June 17, 2025, T-Mobile’s tmomail.net stopped delivering around November and December 2024 with no announcement, Sprint’s closed after the T-Mobile merger, and Verizon completes its shutdown on March 31, 2027. The free carrier gateway model is ending across the industry because it cannot meet 10DLC and A2P registration requirements. Replacements run on registered business numbers rather than carrier-owned domains.
Verizon filters gateway traffic without returning a bounce, so the sending system logs a successful email while the message is dropped before it reaches the handset. This is the most common failure pattern reported on @vtext.com and it is not a configuration problem you can fix from your end. A 10DLC-registered sender removes the failure mode because every message returns either a delivery confirmation or a specific error.
The SMS gateway address for Verizon is 10digitnumber@vtext.com, using the recipient’s 10 digit mobile number with no dashes, spaces, or country code. The Verizon SMS email address for messages carrying images is 10digitnumber@vzwpix.com. Both were free consumer gateways that converted an ordinary email into a text on a Verizon phone. Verizon began retiring them in late 2024 and full shutdown is scheduled for March 31, 2027, so neither address should be used for business alerts.
About 30 minutes of hands-on time, plus 1–2 business days of carrier review for the 10DLC registration (you can use trial mode immediately to test).
The Basic plan ($29/month, 500 credits) covers that with room to spare. Pay-as-you-go top-up packs are also available if you’d rather not subscribe.
Yes. You can send from Gmail, Outlook, Apple Mail, server-side SMTP (sendmail, Postfix, msmtp), or any application that can transmit a standard email. The only requirement is that the sending email address is registered to your TextBolt account.
If you’re switching alert systems one at a time, the old vtext.com addresses will continue to (intermittently) work until Verizon’s sunset. There is no migration window. You flip each system on its own schedule.