
Why Is My Phone Not Sending Emails From a Third-Party App?
TL;DR: A third-party email app that receives mail but won't send it usually has a misconfigured SMTP server, an outdated password or OAuth token, or a port blocked by your carrier or network. Work through the checklist below in order and you'll identify the cause without guessing.
What Happened
Your phone receives incoming mail without a problem, but hitting Send produces an error, a spinning wheel, or silent failure where the message sits in Outbox forever. The asymmetry is the clue. Incoming mail (IMAP or POP3) and outgoing mail (SMTP) use completely separate server paths and authentication. Something broke on the outgoing side only.
Common triggers:
- A recent password change on your email account that the app never re-authenticated after.
- An expired OAuth token (the secure handshake modern apps use instead of storing your password directly).
- SMTP server address or port entered incorrectly during initial setup.
- Your mobile carrier or a hotel/office Wi-Fi blocking outbound port 25, the traditional SMTP port.
- A security policy change pushed by Google, Microsoft, or Apple that revoked access for older authentication methods.
Why It Matters
This is not a rare edge case. Google ended support for "less secure app" sign-ins in 2022, and Microsoft completed a similar move for Basic Auth on Exchange Online in late 2022. Any app that was authenticating with a plain username and password against those providers stopped working overnight when those changes rolled out. If your email was working and then suddenly wasn't, that timeline is worth checking.
For business users, a broken outbound email on a mobile device can mean missed approvals, delayed client responses, and no paper trail, all without an obvious alert. The message just sits in Outbox.
Cracked screen or a phone that won't hold a charge? Get a repair quote
What We Don't Know Yet
Without seeing the specific error message your app shows (or checking its logs), it's impossible to know whether the fault is authentication, network, or server configuration. Some apps surface a clear error like "SMTP authentication failed" or "Connection timed out on port 25." Others fail silently. The diagnostic steps below account for all three scenarios.
Also worth noting: behavior can differ between Wi-Fi and mobile data. A port block imposed by one network won't follow you to another, so testing on both is part of the process.
What to Do About It
Step 1: Check the Error Message
Open your Outbox, tap the stuck message, and look for any error text. Screenshot it. "Authentication failed" points to credentials. "Connection refused" or "timeout" points to network or port. "Certificate error" points to a misconfigured server address.
Step 2: Re-Authenticate the Account
In your email app's settings, remove the account and add it back. Use the app's guided setup rather than entering SMTP details manually if the option exists. This forces a fresh OAuth handshake or prompts for your current password. This resolves the problem in a large share of cases.
Step 3: Verify SMTP Settings
If manual configuration is required, confirm these against your provider's official documentation:
| Provider | SMTP Server | Port | Encryption |
|---|---|---|---|
| Gmail | smtp.gmail.com | 587 | STARTTLS |
| Outlook/Microsoft 365 | smtp.office365.com | 587 | STARTTLS |
| Yahoo | smtp.mail.yahoo.com | 465 | SSL/TLS |
| iCloud | smtp.mail.me.com | 587 | STARTTLS |
Port 587 with STARTTLS is the standard for modern authenticated SMTP. Port 465 with SSL is a legacy alternative still supported by some providers. Port 25 is almost universally blocked on mobile networks for consumer accounts.
Step 4: Test on a Different Network
Switch from Wi-Fi to mobile data, or vice versa, and try sending again. If it works on one and not the other, a port block on that specific network is your answer. Use port 587 or 465 rather than port 25, which most carriers block at the infrastructure level.
Step 5: Check for App-Specific Permissions
On Android, go to Settings, Apps, select your email app, and confirm it has not been denied any background data or network permissions. On iOS, check Settings, your email app name, and confirm Background App Refresh is enabled if the app requires it for sending queued mail.
Step 6: Check Provider Security Events
Sign in to your email account on a desktop browser and look for a security or activity log. Google, Microsoft, and Apple all show recent sign-in attempts and blocked access events. If you see your app listed as blocked or "access revoked," follow the provider's steps to authorize it. For Microsoft 365 accounts managed by an employer, an IT administrator may have applied a Conditional Access policy that blocks third-party clients entirely.
If your organization uses Microsoft 365 and this is a recurring issue, managed IT support or a review of your Microsoft 365 configuration may be more efficient than troubleshooting each device individually.
When to Get Help
If you've completed all six steps and mail still won't send, the fault is likely one of the following:
- A server-side policy your provider requires a specific app configuration to satisfy.
- A corporate MDM profile that restricts email clients.
- An account-level block that requires contacting your provider's support.
For straightforward device-side issues that need hands-on help, remote support is a practical option. For business email infrastructure questions, business IT support covers policy, configuration, and ongoing management.
Cracked screen or a phone that won't hold a charge?
Bring it in. Most phone and tablet repairs are same-day, with parts that actually last.



