You open Outlook, new messages arrive normally, but every reply either sits in the Outbox or fails with a sending error. That combination is useful diagnostically: receiving and sending do not always use the same connection path, credentials, or server settings. A mailbox can therefore appear healthy on the incoming side while the outgoing side is broken.
Illustrative example: imagine Avery uses Outlook for Windows with a work email account supplied by a third-party hosting provider. Avery can receive a new message from a client, but a plain reply will not leave the Outbox. This is a hypothetical example used only to show how to apply the troubleshooting process; it is not a real test result or customer story.
The safest approach is to start with the simplest checks, test after each change, and only move into account or server configuration when the earlier steps do not explain the problem. Microsoft’s current support guidance covers both New Outlook for Windows and classic Outlook, although some menus differ between them. The official starting point is Microsoft’s Outlook send/receive troubleshooting page.
Receiving mail proves only that at least part of the mailbox connection is working. For POP or IMAP accounts, incoming mail and outgoing mail use different server settings. IMAP or POP handles retrieval, while SMTP handles sending. A correct incoming configuration can therefore coexist with a wrong SMTP host name, port, encryption choice, password, or authentication method.
With Microsoft 365 or Exchange accounts, the cause may be different because modern Outlook clients generally use Microsoft’s Exchange connection stack rather than a manually configured SMTP submission path. In those cases, an offline client, a stuck message, expired sign-in, profile problem, add-in, account restriction, or service issue is more likely than a random SMTP port problem.
Start by composing a new message to yourself with a short subject such as “send test.” Do not add an attachment, signature image, distribution list, or unusual formatting. This separates a basic sending failure from a problem caused by one particular message.
In classic Outlook, look at the status bar. Microsoft says statuses such as Working Offline, Disconnected, or Trying to connect mean Outlook cannot reach the mail server. On the Send/Receive tab, use Work Offline to return to online mode when necessary, then try Send/Receive again. Microsoft documents this behavior in its guide to working offline in Outlook for Windows.
For Avery, this first test answers a basic question: does sending fail even for a tiny, brand-new message while Outlook is online? If yes, continue. If the test message sends, the original stuck message is the better place to investigate.
A large or malformed message can block later messages behind it. Microsoft specifically recommends checking the oldest item in the Outbox first. Large attachments are a common cause. In Microsoft’s desktop Outlook troubleshooting guidance, an attachment larger than about 20 MB is a warning sign because provider limits vary; Outlook.com separately documents a 25 MB attachment limit for regular attachments.
If the oldest message has a large file, remove the attachment and retry. A cloud-sharing link, such as OneDrive, may be more practical for a large file. If the message is difficult to edit because Outlook keeps trying to send it, classic Outlook users can temporarily choose Work Offline, move or edit the message, then reconnect. See Microsoft’s official instructions for messages stuck in the Outbox.
In the example, suppose Avery’s first failed message contains a presentation but the small test message also fails. That means the attachment may be a separate issue rather than the root cause, so Avery should keep going instead of assuming file size explains everything.
If your provider offers webmail, sign in through the provider’s official website and send the same small test message. For an Outlook.com mailbox, use Outlook on the web. This comparison is valuable:
Do not treat this as proof of one exact cause. It is a routing test that tells you where to spend your next troubleshooting effort.
If you recently changed the mailbox password, completed a security reset, enabled multifactor authentication, or saw a sign-in prompt, update the account sign-in before changing server settings. Microsoft’s current Outlook support instructions say a changed password may need to be entered again in Outlook. New Outlook can prompt you to continue signing in to the affected account.
Some non-Microsoft providers still require an app-specific password for certain mail clients. That rule comes from the email provider, not from Outlook itself, so use the provider’s official instructions rather than a password recipe from a third-party blog.
For Avery, a password change the previous day would be a strong clue. If re-authentication fixes the small test message, there is no reason to alter SMTP ports or rebuild the Outlook profile.
This is the most important branch when receiving works but sending fails on a manually configured POP or IMAP account. Confirm the outgoing server name, port, encryption method, user name, and authentication method against the email provider’s own documentation. Do not copy settings from an unrelated provider, and do not assume the incoming and outgoing host names are identical.
For Outlook.com specifically, Microsoft currently publishes smtp-mail.outlook.com for SMTP, port 587, STARTTLS encryption, and OAuth2/Modern Auth. Those values are for Outlook.com manual connections and should not be generalized to Gmail, Yahoo, an ISP, or a custom-domain mail host. The authoritative reference is Microsoft’s Outlook.com POP, IMAP, and SMTP settings page.
If the mailbox is hosted in Exchange Online, do not treat “enable SMTP AUTH” as a universal fix. Microsoft states that modern clients such as Outlook and Outlook on the web generally do not use SMTP AUTH to send mail through Exchange Online. SMTP AUTH is mainly relevant to specific POP/IMAP clients, applications, devices, and other authenticated submission scenarios. Administrators should consult Microsoft Learn’s Exchange Online SMTP AUTH documentation before changing tenant or mailbox policy.
If the account itself is Outlook.com, a temporary sending restriction can be triggered by unusual sign-in activity or anti-abuse controls. Microsoft also notes that full Microsoft cloud storage can prevent sending and receiving. Check the account through Microsoft’s own account and Outlook.com interfaces rather than repeatedly changing the desktop app.
Outlook.com also has sending limits, and Microsoft notes that limits can vary with account history and subscription status. If you were sending to many recipients or sending unusually high volumes, review Microsoft’s current Outlook.com sending limits. If Microsoft has temporarily blocked the account for unusual activity, follow the official Outlook.com account-unblocking process.
If webmail sends correctly, the password is valid, and the provider settings are correct, the desktop Outlook profile becomes a more plausible cause. In classic Outlook, Microsoft documents a built-in profile repair path: File > Account Settings > Account Settings, select the account, then choose Repair when that option is available. Follow the wizard and restart Outlook. See Microsoft’s profile repair instructions.
If sending still fails, Microsoft also recommends testing classic Outlook in Safe Mode because an add-in can interfere with sending. On Windows, launching outlook.exe /safe starts classic Outlook without normal add-ins. If sending works only in Safe Mode, investigate the add-ins or create a fresh Outlook profile instead of changing mail-server settings again.
Antivirus products with email-scanning features can also interfere with mail transport. Do not disable security software permanently just to make Outlook send. Check the security vendor’s official support instructions and restore protection after any controlled diagnostic test.
Generic advice becomes less useful once Outlook gives a specific error. Microsoft’s troubleshooting page lists errors such as 0x80042109 for failure to connect to an outgoing SMTP server and several other send/receive codes. Record the exact code, the account type, whether webmail can send, and whether a plain message without an attachment fails.
For Avery, imagine the final evidence is: webmail sends successfully, Outlook desktop cannot send, the provider confirms the SMTP settings, and the failure disappears in Safe Mode. That pattern points toward the local Outlook installation, profile, or add-ins—not the recipient and not the provider’s mailbox service. Again, this is only an illustrative scenario, not a claimed test outcome.
Do not stop at “the Send button no longer shows an error.” Use a short verification sequence:
If the problem returns after restart, or only one network/device fails, note that pattern before escalating. For a work or school Microsoft 365 account, contact the organization’s administrator when policy, licensing, tenant health, or server-side settings may be involved. For Gmail, Yahoo, iCloud, ISP, or custom-domain accounts, use the provider’s official mail settings and support channel.
| What you observe | Best next step |
|---|---|
| Small test message sends, but one old message is stuck | Inspect the oldest Outbox item and its attachments. |
| Classic Outlook says Working Offline or Disconnected | Reconnect before changing account settings. |
| Webmail sends, desktop Outlook does not | Focus on Outlook credentials, configuration, profile, and add-ins. |
| Webmail also cannot send | Check account restrictions, provider status, storage, and sending policy. |
| POP/IMAP receives but cannot send | Compare SMTP host, port, encryption, and authentication with the provider’s official documentation. |
| Sending works in classic Outlook Safe Mode | Investigate add-ins or create/repair the Outlook profile. |
The main principle is to preserve evidence as you troubleshoot. Receiving mail successfully narrows the problem, but it does not prove the whole account is correctly configured. A small controlled test, followed by Outbox, connectivity, sign-in, provider settings, and finally profile/add-in checks, is more reliable than changing several settings at once.
Secure a local RAG system against prompt injection with practical controls for ingestion, retrieval, access control, prompt boundaries, tool permissions, output validation, and red-team testing.
Outlook receives mail but will not send? Diagnose Outbox, offline mode, passwords, SMTP settings, account limits, profiles, and add-ins in a practical order.
Organize monthly bills in Excel with a free calendar-based system for due dates, amounts, payment status, recurring charges, and monthly review.
Use this simple Word task delegation matrix template to assign owners, clarify approvals, track due dates, and reduce confusion across a small team.
Reduce hallucinations in enterprise RAG agents by tracing failures, improving retrieval and permissions, adding grounded answer and action controls, and evaluating retrieval, citations, abstention, and tool use.
Fix missing audio in PowerPoint screen recordings by checking recording audio, Windows microphone access, input devices, playback, updates, and repair options.
Fix Excel formulas that are not calculating automatically in three steps: enable Automatic calculation, force a recalc, and repair formula cells.
Build a private local PDF extraction pipeline with PyMuPDF, OCRmyPDF/Tesseract, Docling, and Ollama structured outputs. Compare speed, layout fidelity, hardware needs, and validation tradeoffs.
Use this simple printable daycare attendance sheet for home childcare, with practical fields for arrival, departure, absences, totals, and record checks—plus guidance on when a basic paper log is not enough.
Fix LangChain agent memory loss in long conversations with thread-scoped checkpointers, stable thread IDs, summarization, persistent stores, and practical tests.
