When Outlook reports emails are down, it usually means the client cannot send or receive messages because it cannot connect to the mail server. This status typically appears as an error or notification indicating that outgoing or incoming delivery is failing. Causes vary from simple network or account configuration issues to server outages or authentication mismatches. Understanding the specific error code, account type (IMAP or Exchange), and current connectivity context helps you quickly restore reliable email flow.
Confirm the problem and collect details
Before attempting fixes, note the exact wording, error code, and whether the issue affects all messages or a single folder. These details narrow troubleshooting and help you communicate clearly with support if needed.
Key identifiers to record
- Error message text and any error code (for example, 0x800CCC0E, 0x80042108)
- Send/Receive status: unable to send, unable to receive, or both
- Account type shown in Outlook: Exchange, POP3, IMAP, or Microsoft 365
Check your connectivity and basic settings
Many delivery failures stem from network or device settings that block the ports and protocols Outlook uses.
Quick checks to perform now
| Check | What to verify | Expected state |
|---|---|---|
| Internet connection | Open a website in your browser | Works without captive portals |
| Firewall/antivirus | Temporarily pause to test email | Email succeeds when paused |
| Outlook Send/Receive | Manually start a Send/Receive cycle | Progress completes without errors |
If toggling the firewall or manually triggering Send/Receive changes the behavior, you’ve identified a local blocking issue. If the problem persists across networks (for example, on mobile hotspot and home Wi-Fi), the cause is more likely account or server related.
Inspect account and server settings
Incorrect protocols, ports, or encryption settings commonly cause Outlook to report emails down.
Verify core settings by account type
- Exchange (Microsoft 365): Outlook should connect to Autodiscover; credentials must match the tenant
- IMAP: Port 993 with SSL/TLS is typical; confirm server address matches provider requirements
- POP3: Port 995 with SSL/TLS is common; verify that the same encryption and authentication settings are used
- SMTP: Outgoing port 587 with STARTTLS or 465 with SSL/TLS; ensure authentication is enabled
Cross-check these values against your email provider’s current documentation, since settings can change. Many issues resolve by re-adding the account with modern autodiscover or autoconfiguration flows rather than manual tweaks.
Authentication, tokens, and credential issues
Authentication failures are a frequent reason Outlook shows emails as down, especially for services that have moved to OAuth or modern authentication.
- Sign-in prompts that repeat or fail indicate mismatched passwords, MFA requirements, or app passwords where needed
- For Microsoft 365, ensure Modern Authentication is enabled on the account and in your organization’s policies
- If you use app passwords or legacy protocols, confirm they are still valid and not blocked by conditional access
Review sign-in history in your account security portal to see whether recent blocks or token issues align with when Outlook started reporting errors.
Server-side and service health checks
Outlook may report emails down when the provider has an outage, maintenance event, or configuration change on its side.
How to verify service health
- Check your provider’s status page or service health dashboard for incidents
- Look for advisories on authentication endpoints, SMTP, IMAP, and Exchange Online
- Review recent provider announcements if the issue began after a known update window
For Microsoft 365, use the Service health portion of the Microsoft 365 admin center or the Microsoft 365 Status page. For other providers, consult their support sites for real-time incident information.
Advanced diagnostics and remediation steps
When basic checks don’t resolve the issue, deeper troubleshooting can isolate whether the problem is local or server driven.
Try these steps in order
- Test with Outlook on the web or a mobile client to see if mail works elsewhere
- Create a new Outlook profile and add the account to rule out profile corruption
- Export and back up existing rules, then disable them to see if they’re causing rejection
- Temporarily disable advanced sending options or outbound proxy settings that may interfere
- Check and update Outlook to the latest version or channel for bug fixes
If different clients or networks succeed while Outlook fails, focus on Outlook-specific settings, cached credentials, and add-in interactions.
When to contact support and what to share
Persistent errors, repeated authentication loops, or consistent server rejection often require provider or administrator support.
- Include the exact error message and code
- Share the account type and whether the issue affects one or all users
- Provide timestamps and results of basic connectivity and Send/Receive tests
- Note any recent changes to password, MFA, or organization policies
With these details, support can more quickly determine whether the cause is on the client, network, or server side.