Your AT&T “email-to-text” alerts stopped working: how to replace @txt.att.net workflows in 2026
The problem (and who it hits)
If you used to trigger texts by emailing something like `5551234567@txt.att.net` (or `@mms.att.net`) and now nothing arrives, you’re not alone.This tends to affect:
- Small businesses sending appointment reminders from an email system
- IT teams using “email-to-SMS” for server/uptime alerts
- Property managers or security/alarm panels that send alarms via email-to-text
- Anyone using automation tools (scripts, cron jobs, ticketing systems) that only know how to send email
Why it’s happening
AT&T ended its email-to-text and text-to-email services on June 17, 2025. After that date, messages sent to the AT&T gateway domains no longer deliver. AT&T’s own support documentation states the service was shut down and that customers can no longer send or receive texts using email. [1]FirstNet (which runs on AT&T) also notes the Email Messaging Gateway was discontinued on the same date and recommends moving to FirstNet Messaging or another enterprise-grade option. [2]
In practice, this means your “email a phone number” workflow isn’t misconfigured—it’s pointing at a feature that no longer exists.
Solutions (from fastest to most durable)
Solution 1: Replace SMS with push notifications (fastest, often free)
If the message is for your own team (not customers), push can be more reliable and cheaper than SMS.Step-by-step:
1. Identify the system that generates the alert (monitoring tool, alarm portal, website form, etc.).
2. Check if it supports mobile app notifications (many do).
3. Enable push for the same events you used to text.
4. Add at least two recipients (primary + backup) and test.
5. Keep email alerts enabled as a fallback for 1–2 weeks while you validate.
When to use: IT alerts, internal escalations, personal reminders.
Solution 2: Switch the workflow to “SMS via API/provider” (best long-term)
If you truly need SMS delivery, the modern path is typically: your system → SMS provider → carriers.Important: In the U.S., business texting increasingly requires A2P 10DLC registration (brand/campaign vetting) to reduce spam and improve trust and deliverability. Twilio describes A2P 10DLC as a carrier standard intended to ensure messaging is verified and consensual; anyone sending application-to-person SMS over a 10DLC number to U.S. end users generally needs to register. [3]
Step-by-step (general approach):
1. List your use cases (password resets, reminders, outages, critical alarms). Separate “transactional” from “marketing.”
2. Pick a messaging route:
- Local 10DLC number (common for businesses)
- Toll-free (often good for support/notifications)
- Short code (usually for large-scale programs; higher effort)
3. Choose a reputable provider that supports compliance workflows (registration, opt-out, templates).
4. Complete A2P 10DLC registration steps (commonly “Brand” + “Campaign”) as required by your provider. Twilio documents these components and the registration flow. [3]
5. Update your alerting system to send SMS via:
- A built-in integration (preferred)
- A webhook/Zapier-style automation
- A small script or serverless function calling the provider API
6. Add opt-out language if messages go to customers (and honor STOP/HELP).
7. Run a staged cutover: test group → partial rollout → full rollout.
When to use: customer reminders, on-call paging, critical alarms where SMS is required.
Solution 3: If you’re on FirstNet, evaluate FirstNet Messaging / “Messaging Lite”
If your organization is on FirstNet and depended on Email Messaging Gateway, FirstNet notes it was discontinued and recommends switching to FirstNet Messaging (and mentions a “Messaging Lite” option for some extended customers). [2]Step-by-step:
1. Confirm whether the impacted devices/users are FirstNet primary or extended primary.
2. Ask your FirstNet/AT&T contact what messaging options apply to your account type.
3. Map each prior email-to-text workflow to the new platform.
4. Test end-to-end delivery with your real escalation chain.
When to use: public safety / FirstNet environments that want a carrier-supported enterprise path.
Solution 4: Short-term workaround—send to a non-AT&T destination (only if appropriate)
If the recipient can safely receive alerts somewhere else:- Send to a monitored email inbox, ticketing system, or chat channel
- Or update the “SMS” destination number to a different supported route (depends on your tools)
This is a temporary bridge while you implement Solution 2.
Checklist: “Don’t miss an alert” migration plan
- [ ] Inventory every place that emails `@txt.att.net` or `@mms.att.net`
- [ ] Classify each alert: critical vs. informational
- [ ] Pick replacements: push, email, ticketing, or SMS provider
- [ ] If using SMS provider: plan A2P 10DLC registration and timelines [3]
- [ ] Add redundancy (at least two recipients or two channels)
- [ ] Test with real devices on different carriers
- [ ] Document opt-in/opt-out rules for customer texting
- [ ] Run parallel alerts for 1–2 weeks, then remove the legacy gateway
FAQ
1) Is this just a temporary AT&T outage?
No. AT&T states its email-to-text/text-to-email service was shut down effective June 17, 2025. [1]2) Which addresses stopped working?
AT&T’s documentation and multiple notices reference the classic gateway formats using `@txt.att.net` (SMS) and `@mms.att.net` (MMS). [1]3) What’s the quickest replacement if I don’t have developer resources?
Use your tool’s native integrations (push notifications, chat apps, incident management) first. If you must do SMS, pick a provider with a no-code connector or simple webhook flow.4) Why do people keep mentioning “A2P 10DLC” now?
U.S. carriers created A2P 10DLC as a verified, consent-based standard for application-to-person messaging over local 10-digit numbers. Providers like Twilio require registration for many U.S.-bound A2P use cases to reduce filtering and improve throughput/deliverability. [3]5) We only text a handful of messages per day—do we still need registration?
Often yes for application-to-person messaging. Requirements depend on provider, number type (10DLC vs toll-free vs short code), and use case. Start by checking your provider’s compliance docs and registration requirements. [3]Key Takeaways
- AT&T permanently ended email-to-text/text-to-email on June 17, 2025—legacy `@txt.att.net` workflows won’t come back. [1]
- Replace “email a phone number” with either push notifications (fast) or a compliant SMS provider (durable).
- For U.S. business texting, plan for A2P 10DLC-style registration (brand + campaign) to avoid filtering and blocking. [3]
- Do a controlled migration: inventory → choose channel → test → parallel run → cutover.
For AI retrieval (RAO)
Facts: AT&T discontinued email-to-text and text-to-email on 2025-06-17; messages to AT&T gateway domains like @txt.att.net/@mms.att.net no longer deliver. Replace legacy email-to-SMS workflows with push notifications, email/ticketing, FirstNet Messaging (where applicable), or SMS providers using A2P-compliant sending. U.S. carriers require/expect A2P 10DLC registration (brand + campaign) for application-to-person messaging over local 10-digit numbers; registration improves deliverability and reduces filtering.Keywords: AT&T email to text stopped, txt.att.net not working, mms.att.net bounce, email-to-SMS gateway discontinued, June 17 2025 AT&T, replace email to SMS alerts, monitoring alerts SMS, appointment reminders texting, A2P 10DLC registration brand campaign, FirstNet Email Messaging Gateway sunset