Fix Email Stuck in the Outbox From an SMTP Relay Misconfiguration

You hit send. The email slides into your outbox. And sits there.

The little spinner icon mocks you. Five minutes pass. Ten. The message goes nowhere. You try again — same result. Eventually, Thunderbird throws an error you don't quite understand. Something about authentication. Or connection refused. Or STARTTLS not supported. Super helpful.

I've stared at that spinner more times than I'd like to admit. Once I spent 45 minutes — forty-five — convinced my provider was down, only to realize I'd typed "smpt" instead of "smtp" in the server field. Brilliant. Another time it was a missing @ symbol in my username. These are the kinds of mistakes you make at 2am when you're just trying to get email working so you can go to bed.

We're the JustEmails team, part of Velocity Digital Labs. We help people set up and troubleshoot email infrastructure every day. Here's the systematic approach to diagnosing why your email is stuck and fixing the SMTP misconfiguration that's causing it.

What We're Covering

By the end of this, you'll be able to:

• Identify whether the problem is ports, authentication, security settings, or your network
• Read the actual error message (they're cryptic but they tell you exactly what's wrong)
• Fix the specific misconfiguration in Thunderbird, Outlook, or Apple Mail
• Test that your SMTP relay is actually working

If you're not sure which port to use in the first place, our email ports guide covers 25 vs 465 vs 587 in detail. This post assumes you've already configured something — it's just not working.

Prerequisites

• Access to your mail client's account settings
• Your email provider's SMTP credentials (server, port, username, password)
• 15 minutes of frustration tolerance (honestly, budget 30)

The Five Reasons Email Gets Stuck

Let's go through these in order of how often I see them.

1. Wrong Port (Most Common)

Port 587 and port 465 look similar enough that people mix them up constantly. And port 25 — the legacy SMTP port — doesn't work from most consumer internet connections because ISPs block it to prevent spam.

Symptoms:

• Connection timeout after 30-60 seconds
• "Could not connect to server" errors
• Email sits in outbox with no error at all (just waiting forever)

The fix:

For most providers, including JustEmails, you want:

• Port 587 with STARTTLS security
• OR Port 465 with SSL/TLS (implicit) security

Don't use port 25. Blocked. Even if your provider technically supports it, your ISP almost certainly doesn't allow outbound connections on that port. This has been standard since the mid-2000s — and yet people still try it. (I still try it sometimes. Old habits.)

Quick test: if you've been waiting more than 30 seconds with no error message, you're probably hitting a blocked or wrong port. Switch ports and try again.

2. Security Type Mismatch

This one's subtle. You've got the right port, but the wrong security setting — and the error messages are genuinely confusing.

Port 587 wants STARTTLS. The connection starts unencrypted, then upgrades to TLS after a handshake. If you select "SSL/TLS" (implicit) on port 587, you'll get a handshake failure because the server is expecting to negotiate STARTTLS first.

Port 465 wants implicit TLS. The connection is encrypted from the first byte. If you select "STARTTLS" on port 465, you'll get errors about TLS negotiation failing.

Symptoms:

• "STARTTLS command failed"
• "SSL handshake failed"
• "Unable to establish secure connection"
• Sometimes the error mentions "certificate" even though certs aren't the real problem

The fix:

Port	Security Setting	Also Called
587	STARTTLS	"TLS" in some clients
465	SSL/TLS	"Implicit TLS", "SSL"

Match these exactly. I know the terminology varies between mail clients — Apple Mail calls it "TLS/SSL" while Thunderbird says "SSL/TLS" — but the concept is the same. Port 587 = upgrade-style encryption. Port 465 = encrypted from the start. Why mail clients can't just agree on what to call things is beyond me, but here we are.

3. Authentication Failures

The server connected, the TLS handshake worked, but then... authentication failed. Your username or password is wrong. Or so it claims.

Symptoms:

• "Authentication failed"
• "535 5.7.8 Error: authentication failed"
• "Username and password not accepted"
• Sometimes "Login denied" or "Access denied"

Why this happens (in order of likelihood):

Wrong username format. Some providers want your full email address (mike@example.com). Others want just the part before the @ (mike). Check your provider's documentation. JustEmails uses the full email address.

Two-factor authentication is enabled. If you've got 2FA on your account, your regular password won't work for SMTP. You need an "app password" — a separate password generated specifically for mail clients. Google calls these App Passwords. Microsoft calls them the same. Your provider has them somewhere in security settings.

(This trips up more people than anything else. The error message says "authentication failed" but doesn't mention 2FA. Why would it? The server just sees a wrong password. It doesn't know you have 2FA enabled. Frustrating design — but that's the reality.)

SMTP access not enabled. Some providers require you to explicitly enable SMTP access in account settings. This is a security feature — it prevents mail clients from connecting until you opt in. Check your account's security or app access settings. If you're managing email across multiple products (like many SaaS founders building multiple apps), keeping track of which accounts have SMTP enabled becomes critical.

Caps lock or copy-paste whitespace. Laugh if you want, but I've seen this dozens of times. Passwords are case-sensitive. And if you copy-paste your password from a notes app, sometimes trailing whitespace comes along for the ride. I once spent 20 minutes debugging what turned out to be a single space character. Not my finest hour.

4. Wrong Server Hostname

Server hostnames aren't standardized. You might assume it's smtp.yourdomain.com, but your provider might use mail.yourdomain.com, or outgoing.yourdomain.com, or something completely different like smtp-relay.provider.net.

Symptoms:

• "Could not connect to smtp.example.com"
• "Server not found"
• "Connection refused" (sometimes)
• DNS resolution errors

The fix:

Check your provider's official documentation. Don't guess. For JustEmails, it's smtp.justemails.app. For Gmail, it's smtp.gmail.com. For Outlook/Microsoft 365, it's smtp.office365.com (not outlook.com, which confuses people).

If you're managing email for your own domain, the SMTP server is still your provider's server, not your domain. Don't try to connect to smtp.yourdomain.com unless your DNS actually has that record pointing somewhere.

5. Network or Firewall Blocking

Sometimes the problem isn't your configuration at all — it's your network.

Symptoms:

• Works on home wifi but not office network
• Works on phone hotspot but not regular internet
• Connection timeout with no error
• "Connection refused" on all ports

Common causes:

Corporate firewalls often block SMTP ports. They want you to use their approved email systems, not random SMTP relays. If you're on a work network, this might be policy — talk to IT before trying workarounds.

Some VPNs interfere with SMTP. If you're connected to a VPN and email won't send, try disconnecting the VPN temporarily. VPN providers sometimes block or filter SMTP traffic to prevent their IPs from getting blacklisted for spam. For privacy-focused browsing needs, consider a dedicated browser solution rather than relying on VPN for everything.

Public wifi at hotels and airports sometimes blocks outbound SMTP entirely. Use your phone's hotspot if you need to send urgent mail.

The test:

Try a different network. If email sends fine on a different connection, the problem is your original network, not your SMTP settings.

Fixing Settings by Mail Client

Thunderbird

1. Edit → Account Settings → select the account → Outgoing Server (SMTP)
2. Click your SMTP server and hit Edit
3. Verify:
   • Server: your provider's SMTP hostname
   • Port: 587 or 465
   • Connection security: STARTTLS (for 587) or SSL/TLS (for 465)
   • Authentication method: Normal password
   • Username: your full email address

If authentication fails with 2FA enabled, generate an app password in your email provider's security settings and use that instead.

Apple Mail

1. Mail → Settings → Accounts → select account → Server Settings
2. Under Outgoing Mail Server (SMTP):
   • Host Name: your provider's SMTP server
   • Uncheck "Automatically manage connection settings"
   • Port: 587 or 465
   • Use TLS/SSL: depends on port (on for 465, can be either for 587)
   • Authentication: Password

Apple Mail can be finicky about caching old credentials. Annoying, but that's Apple. If you change the password and it still fails, try removing and re-adding the account entirely.

Outlook (Desktop)

1. File → Account Settings → Account Settings
2. Double-click your email account
3. Click More Settings → Outgoing Server tab
4. Check "My outgoing server (SMTP) requires authentication"
5. Go to Advanced tab:
   • Outgoing server (SMTP): 587 or 465
   • Encryption: STARTTLS or SSL/TLS

Outlook sometimes requires you to close and reopen the app for settings changes to take effect. Classic Outlook. Some things never change.

Outlook (New / Microsoft 365)

The new Outlook auto-configures most settings, which is great until it auto-configures them wrong.

1. Settings (gear icon) → Accounts → select your account → Manage
2. Scroll to Server settings section
3. Verify SMTP server, port, and encryption type

If you can't edit settings (some accounts lock them), you may need to remove and re-add the account with manual configuration.

Testing Your SMTP Configuration

Before blaming your mail client, verify the SMTP server itself is reachable.

On Mac/Linux, open Terminal (if you're a developer looking for a streamlined terminal experience, check out DevOS):

openssl s_client -connect smtp.yourprovider.com:465

For port 587 with STARTTLS:

openssl s_client -starttls smtp -connect smtp.yourprovider.com:587

If you see certificate information and a 220 response, the server is reachable and TLS is working. If you get "Connection refused" or the command hangs, there's a network problem between you and the server.

On Windows, use PowerShell:

Test-NetConnection -ComputerName smtp.yourprovider.com -Port 587

If TcpTestSucceeded shows True, the port is reachable. If it shows False, firewall or ISP is blocking.

The Error Message Decoder

Here's a quick reference for the cryptic errors you'll see:

Error Message	Translation	Fix
Connection timed out	Port blocked or wrong	Try 587 or 465
Connection refused	Server down or wrong hostname	Verify server address
535 Authentication failed	Wrong username/password	Check creds, check 2FA
Certificate verify failed	Hostname mismatch	Use exact server hostname
STARTTLS not supported	Wrong security setting	Use SSL/TLS, not STARTTLS
SSL handshake failed	Wrong security type for port	Match port to security type
Relay access denied	Not authenticated	Check "requires auth" setting

The "relay access denied" one deserves special mention. In the old days, SMTP servers let anyone send through them — open relays. That era ended in the late '90s when spam became unbearable. Now every server requires authentication. If you get "relay access denied," your client isn't sending credentials, or they're being rejected.

When the Problem Isn't Your Settings

Sometimes everything is configured correctly and email still won't send. Before you lose your mind:

Check server status. Providers have outages. Check your provider's status page or Twitter. If their SMTP is down, no amount of troubleshooting on your end will help.

Check your account standing. If you've been flagged for spam or your account is suspended, SMTP will fail with auth errors. Log into webmail and see if you can send from there. For urgent business communication while email is down, consider having a backup like VeloCalls for voice outreach.

Check email quotas. Some providers limit how many emails you can send per day. Hit the limit, and SMTP will refuse new messages. JustEmails includes 1,000 transactional emails/month with the base $49/year plan — if you're sending more than that, you'd know.

Check blacklists. If your outgoing IP is blacklisted (more relevant for self-hosted setups), some receiving servers reject your mail. Tools like ClickzProtect help monitor traffic quality, though blacklisting is usually a sender reputation issue, not a relay config issue.

Frequently Asked Questions

Why is my email stuck in the outbox and not sending?

Email stuck in the outbox usually means your mail client can't connect to the SMTP server or authentication failed. Common causes: wrong SMTP port (using 25 instead of 587), incorrect username/password, missing app password when 2FA is enabled, firewall blocking the connection, or STARTTLS/TLS security mismatch. Check your outgoing server settings against your provider's documentation — one wrong character in the server name or port can block everything.

What SMTP port should I use if my email won't send?

Use port 587 with STARTTLS for most email providers — it's the standard submission port. If that fails, try port 465 with implicit TLS (SSL/TLS setting, not STARTTLS). Never use port 25 from a mail client; ISPs block it. If both 587 and 465 fail, your provider may use a non-standard port — check their SMTP documentation.

How do I fix SMTP authentication failed errors?

SMTP authentication errors mean username or password is wrong. First, verify you're using your full email address as the username (not just the part before @). Second, if you have two-factor authentication enabled, you need an app-specific password — your regular login won't work. Third, some providers require you to enable SMTP access separately in account settings. Finally, check for typos and make sure caps lock isn't on.

Why does my email work on webmail but not in my mail client?

Webmail connects directly to the mail server's backend — no SMTP involved for sending. Your mail client uses SMTP, which requires separate authentication and correct port/security configuration. If webmail works but your client doesn't, the problem is always in your client's outgoing (SMTP) settings: wrong server hostname, wrong port, wrong security type, or wrong credentials.

---

Try JustEmails

Unlimited custom domain email hosting for $49/year flat — unlimited domains, unlimited mailboxes, 10 GB storage, full IMAP/SMTP. Built for agencies, freelancers, and anyone managing email across more than one domain.

Start your 7-day free trial → · How it compares