Outlook Not Receiving New Email? Here’s the Fix

If your Outlook account has stopped receiving new email, but the same mailbox looks completely current in webmail, you’re not looking at a broken mail server. You’re looking at a dead sync path inside Outlook itself, and it won’t show an error to tell you that. It will just quietly stop pulling new mail and keep showing you the last thing it managed to cache, sometimes for well over a year.

Here’s how to confirm what’s actually happening and get a working setup back.

The Setup This Applies To

This applies to a mailbox hosted on a standard cPanel mail server (or any non-Microsoft IMAP host), added to Outlook as a “connected account” rather than a native Microsoft 365 mailbox. That distinction matters. The mailbox itself isn’t a Microsoft-hosted inbox, it’s a third-party account that Outlook is pulling in through its own sync layer, and that’s the layer that broke.

Why Outlook Isn’t Receiving New Email

The mailbox works perfectly through the mail host’s own webmail. Every message is current, right up to the moment you check it.

Open the same account in Outlook on the web, Outlook mobile, or the “new” Outlook desktop app reached through a browser at office.com, and none of them show anything newer than a fixed date, frozen in place no matter how much time passes. Logins succeed normally. No error banner, no “sync failed” message, nothing pointing at a cause. Outlook simply isn’t receiving new email for that account, and it gives you no indication why.

The usual first-round troubleshooting doesn’t move the needle: checking the internet connection, clearing browser cache and cookies, checking the junk and archive folders, restarting the app, even testing on a second device. That last one is the trap. Testing on Outlook web, Outlook mobile, and the new desktop app all in a row feels like three independent confirmations that something is wrong with the mail server. It isn’t. All three run through the same Microsoft cloud-sync backend for non-Microsoft mail, so you’re not looking at three data points, you’re looking at one broken connection through three different windows.

It’s also worth ruling out the more common, unrelated causes before assuming this is the issue. A mailbox that’s simply offline, filtered to “Unread only,” or sorted into a Focused/Other split can look similarly stalled. The distinguishing detail here is that the account isn’t missing a handful of messages, it’s frozen entirely as of one specific date, across every Microsoft-side client at once, while a completely separate access method (webmail) shows the account is fine.

Root Cause

Microsoft deprecated the “connected accounts” feature that let Outlook aggregate mail from third-party, non-Microsoft mailboxes, cutting off the authentication path for that sync starting July 1, 2024. The change was never surfaced to the end user as an error. The sync simply stopped, and Outlook kept displaying whatever it had last successfully pulled before the cutoff.

Mail server logs confirm this cleanly: after the cutoff date, there are zero authentication attempts from Microsoft’s servers against the mailbox. Microsoft isn’t failing to sync, it isn’t even trying. That’s the detail that rules out anything on the hosting side and points squarely at Microsoft’s own infrastructure.

The Fix

Direct IMAP connections bypass the broken aggregator entirely, since they never touch Microsoft’s sync backend in the first place. Here’s how to get there.

1. Confirm the connection is actually dead, not just broken. In outlook.office.com, click the gear icon, then go to Settings > Mail > Sync email. Look for a “Connected accounts” section. If it’s missing entirely, along with any “Send and receive” option for that account, the feature has been fully removed for that mailbox, not just interrupted. There’s nothing left to reconnect.
2. Check the mail server’s own authentication logs for login attempts from Microsoft’s servers around the time of a sync attempt. Zero attempts confirms the sync was never reaching the server, which rules out a credential problem, firewall block, or hosting issue on your end.
3. Stop troubleshooting inside Outlook’s web or mobile app. Nothing you do there will restore the connection. The feature is gone for that account, not misconfigured.
4. On desktop, use Classic Outlook, not New Outlook. In the Outlook desktop app, find the “Try the new Outlook” toggle, usually in the top right corner, and switch it off. New Outlook shares the same broken cloud-sync path as the web and mobile versions. Classic Outlook connects directly to the mail server over IMAP instead.
5. Add the mailbox manually as a direct IMAP account, not through any “connected accounts” option. In Classic Outlook: File > Add Account > Advanced options > Let me set up my account manually, then choose IMAP. You’ll need:
   • Incoming server: your mail host’s IMAP hostname, port 993, SSL/TLS
   • Outgoing server: your mail host’s SMTP hostname, port 465 or 587
   • Standard mailbox username and password

   These settings will differ by host. Check your provider’s mail configuration page if you don’t already have them on hand.

6. On mobile, skip the Outlook app entirely. Outlook mobile has no option to connect a third-party mailbox outside its own cloud sync, so there’s no equivalent fix available inside the app. Samsung Email, Apple Mail, or Thunderbird, configured with the same standard IMAP settings above, all connect straight to the mail server and work correctly.
7. If the mailbox will be active on more than one device, confirm every client is set up as IMAP, not POP. POP causes devices to compete over which one “owns” the mail, which can result in messages being deleted from the server once one device downloads them.

What About Contacts and Calendar?

Setting the mailbox up as a direct IMAP account fixes mail, but it won’t bring back contacts or a calendar. That’s expected, not a step you missed. IMAP is a mail-only protocol. It has no mechanism for syncing contacts or calendar events at all.

This gets confusing when a contacts list was visible in Outlook before, and appears to vanish once the mailbox is reconnected via IMAP. Before assuming anything was lost in the switch, check whether that list was a real, saved address book in the first place. In outlook.office.com, open the Contacts icon in the left navigation. If it’s empty, what was showing before wasn’t a maintained contact list, it was Outlook’s auto-populated “Other Contacts” feature, a list built from mail history under the old connected-accounts sync, not something anyone actually saved. Once that sync is gone, so is the list it was generating, because there was nothing actually stored to migrate in the first place.

If real contacts do exist somewhere, exported from a previous client, a CRM, or a spreadsheet, the fix is a straightforward export and import rather than a sync setting: save them as a vCard (.vcf) file and import that into the new mail client. Some mail hosts also support CardDAV for live contact syncing separate from IMAP. Check your host’s documentation to confirm it’s available before assuming it is.

Prevention

Before assuming a sync complaint is a hosting problem, check whether the account in question is a native mailbox or a Microsoft “connected account” pulling in third-party mail. The two behave identically until something breaks, and only one of them can actually be fixed by adjusting settings.

If Microsoft’s own documentation says a feature has been discontinued, treat every symptom tied to that feature as unfixable rather than working through a standard troubleshooting checklist. The checklist assumes the feature still exists.

When onboarding a client onto a new device or a fresh Outlook install, it’s worth confirming up front whether their mailbox will be added as a connected account or as a direct IMAP connection. Setting it up correctly the first time avoids a repeat of this exact conversation months later, when the same account quietly stops receiving new email again for the same underlying reason.

Closing

This exact failure mode is easy to misdiagnose because it presents as a server problem and tests as “confirmed” across multiple devices. For general email client configuration steps on a cPanel-hosted mailbox, see our email account FAQs. If you’re managing cPanel-hosted email for clients who also rely on Outlook and run into this same wall, TPP Web Solutions can help get the client-side setup sorted correctly.