You leave the coffee shop, your phone drops off the Wi-Fi and onto T-Mobile data, and your mail client throws “Could not connect to SMTP server.” Same email. Same settings. Same account that worked ninety seconds ago. Here’s the thing most pages won’t tell you: that’s not a bug. It’s policy. This guide covers why it happens, which port actually fixes it, and the roughly two-minute change that gets your mail moving again.
Key takeaways
- T-Mobile, like nearly every mobile network, blocks outbound port 25. That’s deliberate spam control, and it’s the industry-recommended setup (Spamhaus).
- Use an authenticated submission port instead: 587 (STARTTLS) first, 465 (implicit TLS) as backup, 2525 if both are blocked.
- There’s no “T-Mobile SMTP server” to point your phone at. The old
tmomail.nettext gateway went dark in December 2024. - Gmail and Yahoo now require authenticated, aligned mail. Spam hit 44.99% of all email in 2025 (Kaspersky), and the inbox rules tightened to match.
Why won’t email send over a T-Mobile connection?
Because T-Mobile blocks outbound traffic on port 25, and port 25 is the port a lot of older mail clients quietly default to. Your home or office Wi-Fi usually leaves the modern submission ports open, which is exactly why the same message sails through on Wi-Fi and dies the second you’re on cellular.
Port 25 was built for one job: handing mail from one mail server to the next, server to server, no login required. Great for 1995. Terrible for a world of compromised phones and laptops. An open port 25 on a pool of mobile IP addresses is a spammer’s dream, so carriers shut it. Spamhaus puts it about as plainly as it gets: no end user needs port 25 open on their phone, and networks should close it for everyone except actual mail servers. T-Mobile is just following the same playbook the rest of the industry has run for two decades.
So the fix isn’t “find T-Mobile’s secret port.” It’s “stop using port 25 and switch to an authenticated submission port.” More on which one in a second. If you want the deeper version of how this all moves under the hood, our guide to the SMTP protocol and our rundown of email ports both go further than we will here.
What email settings does T-Mobile actually require?
None of its own. This trips people up, so let’s be direct: T-Mobile doesn’t run an outgoing mail server for you to send through. There’s nothing to “set to T-Mobile.” What the network requires is simply that you send through a server that makes you log in first.
That means pointing your mail client (or your app, or your device) at your email provider’s authenticated submission server, or at a dedicated relay, and turning authentication on. The settings that matter:
- SMTP authentication: on. This is the whole game (defined in RFC 4954).
- Username and password (or an API key, if you’re sending from code).
- Outgoing port: 587 with STARTTLS, or 465 with implicit TLS.
- Encryption: TLS 1.2 or 1.3. If a device only offers TLS 1.0, it’s time to retire or update it.
Once authentication is on, the network stops caring whether you’re on home fiber, hotel Wi-Fi, or a T-Mobile tower in the middle of nowhere. You’ve proven who you are. That’s the point.
Which SMTP port should you use: 587, 465, 2525, or 25?
Short answer: 587 with STARTTLS for most setups. Use 465 (implicit TLS) if your client prefers it, and honestly RFC 8314 leans that way for newer software. Fall back to 2525 only when a network blocks the first two. Never use 25 to send from an app or a device.
| Port | What it’s for | Encryption | Auth | Use it? |
|---|---|---|---|---|
| 587 | Mail submission from a client or app | STARTTLS (upgrades to TLS) | Required | ✅ Yes default |
| 465 | Mail submission over implicit TLS | TLS from the first byte | Required | ✅ Yes backup |
| 2525 | Unofficial submission fallback | STARTTLS / none | Required (with us) | ✅ Only if 587/465 blocked |
| 25 | Server-to-server relay | Optional, often none | Historically none | ❌ No blocked on mobile |
The truth about port 2525
Here’s the part the listicles skip. Port 2525 has no RFC behind it and no IANA assignment for mail submission. It’s a convention, nothing more. So many networks block 587 that providers (SMTP2GO included) started offering 2525 as an escape hatch, and it stuck. Handy? Yes. We support it, plus 8025, for exactly these situations. A standard? No. Treat it as the option you reach for when the proper ports are blocked, not your first choice.
How I set up authenticated SMTP on a T-Mobile SIM (and what broke first)
I ran this on a live T-Mobile SIM with Wi-Fi switched off, because testing it on Wi-Fi defeats the entire purpose.
First attempt, I left the outgoing port on 25, the way an old Outlook profile might have it. The connection didn’t fail with a clean error. It just hung. No “connection refused,” no SMTP code, nothing. The client sat there spinning and eventually gave up after a timeout. That silent hang is the classic signature of a blocked port, and it’s why people assume their account is broken when it’s the network quietly dropping the packets.
Then the fix. Six steps, start to send:
- Open your mail client’s outgoing (SMTP) server settings.
- Set the server host to your provider’s submission server (for us,
mail.smtp2go.com). - Change the port from 25 to 587, and set encryption to STARTTLS (or TLS).
- Turn authentication on.
- Enter your SMTP username and password. Copy and paste them. A single mistyped character returns a
535authentication error, and you’ll waste ten minutes blaming the network. - Send a test message.
If you want to see the block for yourself before you change anything, a quick connection test makes it obvious:
$ nc -vz -w 10 mail.smtp2go.com 25 # on T-Mobile data: hangs, times out
$ nc -vz -w 10 mail.smtp2go.com 587 # connects
Connection to mail.smtp2go.com 587 port [tcp/submission] succeeded!Full configuration walkthroughs for Outlook, Apple Mail, and dozens of apps and devices live in our setup guides, and the exact server names and ports are in the getting-started post.
What happened to T-Mobile’s email and text-from-email addresses?
This is where the old advice really shows its age. A lot of pages, including the one this replaces, were written when T-Mobile still ran address-based services people leaned on. Most of that is gone.
The big one: the tmomail.net email-to-SMS gateway, the trick where you emailed 5551234567@tmomail.net and it arrived as a text. That’s dead. T-Mobile customers started reporting failures in mid-November 2024, and the gateway domain stopped resolving by December 2024. It wasn’t a one-off. AT&T and Verizon shut their gateways down in the same window, killing the era of free carrier email-to-text. The reason was the obvious one: an open, unauthenticated gateway is impossible to keep clean, so spam and spoofing took it down.
And the Sprint addresses people sometimes still reference (messaging.sprintpcs.com and friends)? Also gone. T-Mobile shut down Sprint’s LTE network on June 30, 2022, after retiring its 3G CDMA network that January. There’s no Sprint network left to host anything.
So if you were emailing a T-Mobile number to fire off alerts (server warnings, on-call pages, appointment reminders), that path is closed. The modern replacement is a real messaging route: an email-to-SMS service or SMS API that’s authenticated and gives you delivery tracking the old gateway never did.
When does it make sense to use a dedicated SMTP relay?
Not always, and we’ll be straight with you about that. If you send a handful of personal emails a day from your phone, your email provider’s submission server on 587 is all you need. A relay earns its place when sending becomes part of how your software or your hardware works.
Three signals you’ve outgrown direct sending:
- Your mail is generated by an app, website, or device: password resets, order receipts, alerts, scan-to-email from a copier, notifications from a security camera. These don’t sit at a desk; they need to send from anywhere, reliably.
- You’re sending in volume, transactional or bulk, and your provider’s daily caps or shared reputation are starting to bite.
- You’re migrating off Amazon SES, SendGrid, Mailgun, or Postmark and want clearer reporting or actual human support. (If you’re deep in an AWS-native stack and SES already fits, stay there. We’d rather tell you that than oversell.) Here’s our honest take on picking an alternative provider and a migration walkthrough if you go that way.
The device case is where this gets real. StoredTech has run their phone systems and copiers through SMTP2GO since 2011, the kind of legacy hardware that hates modern auth and loves to break on a port change. That’s the mobile-and-device sending problem at scale, and it’s exactly what a relay is built to absorb. More on how the relay itself works in our SMTP relay introduction and on the relay overview page.
If your email keeps dying the moment you leave Wi-Fi, a relay with authenticated 587/465/2525 sending fixes it for good, from any connection. Start sending free → 1,000 emails a month, no credit card, working in about five minutes.
Frequently asked questions
What SMTP port should I use on T-Mobile?
Use 587 with STARTTLS as your default, or 465 with implicit TLS as a backup. If a network blocks both, 2525 is a common fallback. Don’t use port 25 for sending from a phone, app, or device, because T-Mobile and almost every mobile network block it outbound.
Why does my email work on Wi-Fi but not on T-Mobile?
Your Wi-Fi network probably leaves the submission ports open, while T-Mobile blocks outbound port 25 for spam control. If your mail client is set to send on port 25, it connects fine on Wi-Fi and silently hangs on cellular. Switching the outgoing port to 587 with authentication usually fixes it instantly.
Does T-Mobile have its own SMTP server?
No. T-Mobile doesn’t provide an outgoing mail server for customers to send through. You send through your email provider’s authenticated submission server or a dedicated SMTP relay, and T-Mobile’s network simply carries the traffic once you’ve logged in.
Is SMTP authentication required to send email?
For sending over a mobile network, yes, in practice. Unauthenticated sending relies on port 25, which T-Mobile blocks. Authenticated submission on port 587 or 465 (defined in RFC 4954 and RFC 8314) is also what Gmail and Yahoo now expect from senders, so it’s the right setup everywhere, not just on cellular.
What happened to Sprint and T-Mobile email-to-text addresses?
They’re gone. T-Mobile’s tmomail.net email-to-SMS gateway stopped working in December 2024, and Sprint’s network (including its messaging addresses) was shut down on June 30, 2022. To send text alerts from email or an app today, use an authenticated email-to-SMS service or SMS API instead of a carrier gateway.
About the author
Charlie Abrahamson
Charlie is CEO and co-founder of SMTP2GO. He started the company in 2006 after a trip to Argentina left him locked out of his own email (every internet café and local ISP blocked his attempts to send). Twenty years later, SMTP2GO delivers email for businesses around the world from its Christchurch, New Zealand base. Charlie has personally configured SMTP relays, debugged deliverability incidents, and led migrations for senders ranging from small businesses to enterprises moving off AWS SES, SendGrid, Mailgun, and Postmark. SMTP2GO is ISO 27001 certified, GDPR compliant and an M3AAWG member.
