What the carrier gateway was, and why it died
Every major carrier used to run an email-to-SMS gateway. You addressed an ordinary email to the recipient number at a carrier-specific domain, and the carrier stripped the email envelope and delivered the body as a text. It was free, it needed no account, and it was wonderfully convenient for a monitoring alert or a one-off note.
That convenience was the problem. US business messaging now runs on registered senders: a brand and campaign filed under 10DLC, consent captured under the TCPA, and CTIA guidelines on top. An anonymous email arriving from any address on earth satisfies none of that and cannot be traced back to a responsible sender, so the gateways became the easiest possible route for spam and the hardest possible thing for a carrier to police. Rather than try, the carriers closed them.
Current status, and why your alerts stopped arriving
| Carrier | Gateway | Reported status |
|---|---|---|
| AT&T | txt.att.net | Shut down, June 2025 |
| T-Mobile | tmomail.net | Stopped delivering in late 2024, with no formal announcement |
| Verizon | vtext.com | Being retired, full shutdown set for March 2027, already filtering |
| Smaller carriers and MVNOs | Various | Some still deliver, none are dependable |
Statuses change, and not every carrier announces. Treat the table as the shape of the situation rather than a guarantee, and verify before depending on any of it.
The pattern worth knowing is that gateways tend to fail quietly. Messages are filtered or dropped rather than bounced, so the sender sees a successful email and assumes the text arrived. Teams usually discover the shutdown when somebody asks why they stopped getting alerts, which is the worst possible way to find out that a notification channel has been dead for months.
Can you send an email to a phone number at all now?
For a person sending one message to one phone, not reliably on the big three networks. There is no consumer replacement, because the thing being replaced was the loophole.
For a business, the answer is a proper sending path: a messaging platform or API with a registered 10DLC brand and campaign behind it. Most platforms, including SimplyRCS, will accept a message triggered from your own systems by API or webhook, which covers the real use case behind almost every email-to-text search, getting an automated alert from a server, a CRM, or a form onto somebody’s phone.
That path costs more than free, and it is worth being straight about that. What it buys is a message that actually arrives, a delivery receipt proving it, automatic STOP handling, and an opt-in record you can produce if anyone asks. The gateway never offered any of those, which is a large part of why it is gone.
Forwarding an email to a phone, and why the rule breaks quietly
The most common version of this is not sending a one-off, it is a forwarding rule. Somebody sets up their mail client, or a monitoring tool, or a shared alias, to auto-forward anything matching a filter to a number at a carrier address, and then forgets it exists. That setup is the most fragile form of the whole pattern, because a rule nobody looks at cannot tell you it stopped working.
When the gateway went away the rule did not error. The forward still succeeds, the mail server still reports delivery, and the message simply evaporates at the carrier. Anyone still running one of these on AT&T or T-Mobile has been forwarding into nothing since 2024 or 2025 without a single bounce to signal it.
Verizon is the one worth checking today, because it is the last of the big three with anything left. Mail to vtext.com may still arrive, may be filtered, and is scheduled to stop entirely by March 2027. Building a notification path on that is borrowing against a date that is already set.
If the forward matters, the replacement is a rule or integration that calls a messaging API rather than an email address. The mechanics are about as simple, and the difference is that a failure is reported back to you instead of disappearing.
Where RCS fits
Once traffic runs through a registered sender, RCS becomes available on the same path. The same alert can arrive with your brand name, logo, and a verified checkmark rather than from an unknown number, carry a button rather than instructions to call somebody back, and report whether it was read. Where a handset cannot receive RCS, it falls back to SMS automatically, so the alert still lands.
- Carrier email-to-SMS gateways are effectively dead on AT&T, T-Mobile and Verizon.
- They closed because anonymous email could not meet 10DLC, TCPA and CTIA requirements.
- Failures are usually silent, so a dead alert channel can go unnoticed for months.
- Auto-forwarding rules are the worst-affected case: the forward still succeeds while the text never lands.
- The replacement for business use is a registered platform or API, not another free gateway.
- A registered path also unlocks delivery receipts, STOP handling, consent records, and RCS.