1. Check for Messages Stuck in the Outbox
Before changing any settings, confirm where in the send process the message is failing.Open your Outbox folder
Open the stuck message
Check for obvious issues
- The To, CC, and BCC fields contain valid, properly formatted email addresses.
- The message does not contain an unusually large attachment (see Step 4).
- You are not in Work Offline mode (Send/Receive → Work Offline should not be highlighted).
Attempt a manual send
2. Verify Your SMTP Settings
Incorrect outgoing server settings are the most common cause of send failures, especially after an account migration or password change.Open Account Settings
Confirm the SMTP server address
Verify the port and encryption
Confirm authentication settings
Re-enter your password
3. Test SMTP Connectivity
If your settings appear correct but sending still fails, verify that your machine can actually reach the SMTP server on the required port. A firewall, proxy, or ISP block may be silently dropping the connection.Test with Test-NetConnection (Windows PowerShell)
TcpTestSucceeded : True. If you see False, the port is blocked between your machine and the server.Test with Telnet (optional, Windows)
220 banner response confirms connectivity. An immediate connection error or timeout confirms a block.Test from a different network
Test-NetConnection fails from the office network but succeeds from a hotspot, escalate to your network team to whitelist the SMTP server address and port in the firewall or proxy configuration.4. Check Attachment Size Limits
Emails with attachments that exceed your mail server’s size limit will permanently fail to send and may remain stuck in the Outbox without a clear error.Check your provider's size limit
Check the total message size in Outlook
18 KB). Note that file sizes increase by approximately 33% after base64 email encoding.Use an alternative for large files
5. Verify Sender Authentication (SPF / DKIM)
If your messages are reaching recipients but landing in spam, or if you receive NDRs (Non-Delivery Reports) mentioning authentication failures, your domain’s SPF or DKIM records may be misconfigured. As an end user, you can verify your sending reputation without needing access to DNS settings.Send a test message to mail-tester.com
[email protected]).Send your test email
Check your score
Interpret and act on results
- SPF / DKIM failures: Report to your IT administrator or email provider — these require DNS record changes.
- Blacklist listing: Report the specific blacklist name to your IT team. Blacklist removal requests must be submitted by the domain/IP owner.
- Content score issues: Review the email body for spam-trigger phrases or excessive links.
Escalation
When to escalate to your IT Help Desk
When to escalate to your IT Help Desk
Test-NetConnectionfails on both ports 587 and 465 from the corporate network, indicating a firewall rule needs to be added.- You receive NDRs with
550 5.7.64or550 5.7.1errors, which indicate relay denial or authentication policy blocks that require server-side configuration. - Multiple users on the same domain are experiencing send failures simultaneously — this points to a server-side or DNS issue.
- Your IP or domain appears on a blacklist in the mail-tester.com report.
- SPF or DKIM checks fail — DNS record updates are required.
- The full text of any Non-Delivery Report (NDR) or bounce message.
- The error code displayed by your email client.
- The results of your
Test-NetConnectioncommands. - Your mail-tester.com score report (screenshot or URL).