Email-to-Text Gateways: How to Send SMS From Email
An email-to-text gateway (also called an email-to-SMS gateway) is a carrier-operated bridge that converts an email into a text message: you send an email to a special address built from the recipient's phone number and the carrier's gateway domain, and the carrier delivers the body as an SMS to that phone. For years it was the free, semi-secret way to text from a computer, beloved by IT departments for server alerts and by anyone who wanted to reach a phone from an inbox.
This guide explains how the gateways work, the address format, and how to use them, and then the part most articles skip: why the gateway era is ending, what the reliability and compliance limits always were, and what to use instead when messages actually matter.
Key takeaways:
- The mechanism is an address format: [tennumberdigits]@[carrier-gateway-domain] turns an email into an SMS on that carrier's network.
- You must know the recipient's carrier, and the gateway silently fails if the number has moved to another network.
- Carriers treat gateway traffic as best-effort and have been retiring the service; AT&T discontinued its email-to-text gateways in 2025, and remaining gateways offer no assurance of delivery.
- For organizational messaging, reminders, alerts, campaigns, two-way conversation, gateways were never compliant-by-design or reliable; registered SMS platforms and APIs are the working alternative.
How email-to-text gateways work
The flow is simple enough to fit in one sentence: the carrier runs a mail server that accepts email for addresses in the form of a phone number at the carrier's gateway domain, strips the message down to text, and injects it into its SMS network for delivery to that number.
Practical mechanics:
- Compose an email to the gateway address for the recipient's number and carrier (formats below).
- Keep it short and plain. The gateway truncates to SMS length (160-character segments), strips or mangles formatting and attachments, and often prepends the subject line, so many senders leave the subject blank.
- Send. Delivery typically takes seconds to minutes, with no delivery receipt back to you.
- Replies, when supported, return to your email address as texts-turned-email, completing a crude two-way loop.
Some carriers historically ran a second domain for multimedia (MMS) gateways, which accepted longer messages and images.
The gateway address formats
Formats used by major US carriers, with the caveat that this landscape is actively shrinking and any given gateway may be retired or filtered by the time you rely on it:
| Carrier | SMS gateway format | Status notes |
|---|---|---|
| AT&T | number@txt.att.net | Discontinued; AT&T retired its email-to-text service in 2025 |
| Verizon | number@vtext.com | Legacy service, best-effort; heavily filtered for bulk traffic |
| T-Mobile | number@tmomail.net | Legacy service, best-effort |
| Cricket | number@sms.cricketwireless.net | Follows its host network's policies |
| US mobile virtual operators generally | varies by host network | Depends on the underlying carrier's gateway |
Two operational warnings baked into this table. First, you must know the carrier, and with number portability, the carrier a number started on is often not the carrier it is on today; a ported number makes the old gateway address silently dead. Second, retirement is the trend: carriers have been shutting gateways down or filtering them aggressively because the same free bridge that served IT alerts became a spam and smishing cannon. Verify against the carrier's current documentation before building anything on these addresses.
What gateways were genuinely good for
In their prime, the gateways earned their keep in narrow, low-stakes lanes:
- Server and infrastructure alerts: monitoring systems emailing an on-call engineer's gateway address, the classic use, now largely replaced by paging apps and SMS APIs.
- One-off personal convenience: texting a phone from a desktop inbox before web-messaging clients existed.
- Legacy system bridges: old software that could send email but not SMS, given a crude texting capability with zero integration work.
The common denominator: a technical sender, a known recipient who chose the arrangement, and messages where silent failure was tolerable. That last clause is the important one.
Why gateways fail as organizational messaging
Measured against real messaging requirements, the gateway model breaks down on every axis:
- No delivery assurance. Gateways are best-effort with no receipts; you cannot know whether the appointment reminder arrived. Proper SMS routes provide delivery receipts, covered in the SMS delivery receipts guide.
- Aggressive filtering. Carriers treat bulk gateway traffic as presumptive spam. Even before retirements, gateway blasts to lists were routinely dropped without notice.
- The carrier-lookup problem. Maintaining carrier mappings for a contact list, through portings, is unmanageable at any scale.
- No sender identity. Messages arrive from odd numeric or email-styled originators, exactly the pattern recipients are now trained to distrust as smishing.
- No compliance tooling. Organizational texting in the US requires consent under the Telephone Consumer Protection Act (TCPA, 47 U.S.C. 227), sender identification, working STOP handling, and registered sending routes (10DLC or verified toll-free) under CTIA guidelines. Gateways provide none of this: no opt-out automation, no consent records, no registration, which puts gateway campaigns on the wrong side of both carriers and the statute.
- Mangled formatting and truncation, which is cosmetic for a server alert and disqualifying for anything customer-facing.
What to use instead
The replacement depends on which job you were hiring the gateway for:
- Alerts and system notifications: an SMS API. A few lines of code send registered, receipted, identity-bearing texts, and the build-vs-buy decision is mapped in the SMS API for beginners guide.
- Sending texts from a computer: any modern SMS platform provides a web inbox, which is the gateway's convenience with delivery, identity, and two-way threading attached.
- Reaching a list: a mass-texting platform with opt-in management, segmentation, scheduling, STOP automation, and registered routes; the category is covered in the mass texting service guide.
- Email-triggered texting specifically: platforms and automation tools accept email or webhook triggers and send real SMS, preserving the "my system only speaks email" integration pattern without the gateway's failure modes.
The migration is usually anticlimactic: the hardest part is admitting that the free bridge was costing you every message it silently dropped.
Frequently asked questions
How do you send a text message from email?
Historically, by emailing the recipient's gateway address: the ten-digit number at the carrier's gateway domain (for example, number@vtext.com for Verizon), which the carrier converts to an SMS. Today, with gateways being retired and filtered, the dependable method is an SMS platform or API that sends real texts from a web inbox or from your systems.
What is the email-to-text address for each carrier?
Legacy formats include number@vtext.com (Verizon) and number@tmomail.net (T-Mobile); AT&T's number@txt.att.net was discontinued in 2025. Formats only work on the recipient's current carrier, so ported numbers break them, and remaining gateways are best-effort with no assurance of delivery.
Why do email-to-text messages fail to deliver?
Common causes: the gateway was retired, the number ported to a different carrier than the address assumes, the carrier filtered the message as bulk or suspicious traffic, or the message exceeded SMS limits and was truncated or dropped. Gateways provide no delivery receipts, so failures are silent.
Are email-to-text gateways free?
The carrier gateways charged the sender nothing, which is exactly why they attracted spam and why carriers now filter or retire them. The recipient's standard message rates applied. For organizational use, per-message platform pricing buys what free never included: delivery, identity, receipts, and compliance.
Can businesses use email-to-SMS gateways for customer messaging?
They should not. Gateway traffic lacks consent tooling, STOP handling, sender registration, and delivery visibility, putting it at odds with TCPA obligations and CTIA carrier standards, and carriers filter it aggressively. Registered SMS platforms and APIs are the compliant, reliable route.
Conclusion
The email-to-text gateway is a lovely piece of internet archaeology: a free bridge between the two messaging systems everyone had, perfect for an era of server alerts and known recipients. That era is closing, carrier by carrier, and the gateway's defining trait, nobody vouches for the message, is precisely what modern messaging cannot tolerate. Use the bridge, where it still stands, for nothing you would miss; use registered rails for everything you would.
Replacing a gateway-era workflow? Contact the FRANSiS team to see email- and event-triggered texting with delivery receipts, two-way replies, and compliance built in.
