Outlook2016/Windows10/IMAP - Cannot receive Incoming Emails

[#1]

Can anyone provide assistance on this please?

I have a new laptop (Windows 10) running Office 2016 and using IMAP on Plusnet. I can send emails (and sync Sent and Draft folders), but cannot receive incoming emails.

I have a "being retired" Windows 7 pc also running Office 2016 and using IMAP on Plusnet. I can send and receive emails properly.

Both computers' settings in Outlook (server details, file namings, account namings etc) are identical. However i note the .ost files are approx 7GB for "Windows 7 pc", and about 500MB for the "new laptop". Both are setup and use the same home broadband connection.

The Send/Receive Synchronisation on the new laptop fails with a (sometimes reported) 800CCC0F-0-0-560 error code

Any suggestions on how to fix the new laptop? Is there something in my Windows 10 settings blocking the download of the incoming emails?

[#2]

In the Account Name and Sync settings, put inbox in the IMAP root folder field.

[#3]

Dear Mr Townman,

Thank you for your message. I have given it a try.

Neither PC nor Laptop have anything currently in the Root Folder Path. Please can you expand in why I should add it to one or both computers?

Initial tests with adding "inbox" to Root Folder Path strangely caused loss of ability to send emails from the laptop and did not solve issue of lack of incoming. So I have reverted to nothing in the Root Folder Field on the laptop at the moment. 

Best wishes

John_B

[#4]

Hi John,

Simple answer - "Because it will usually probably fix the issue".

A more relevant question would be "Why is this needed for some mailboxes ... but not others?".

I have multiple mailboxes from various suppliers and this "characteristic" applies to them all (not just Plusnet's services).  Some mailboxes show the content of all the folders without it, whilst others only show the content of folders other than the inbox which is completely empty.

---

@John_B wrote:

Initial tests with adding "inbox" to Root Folder Path strangely caused loss of ability to send emails from the laptop and did not solve issue of lack of incoming. So I have reverted to nothing in the Root Folder Field on the laptop at the moment.

---

Did you refresh the IMAP folder structure?

EXACTLY what error message did you get when attempting to send?  This should have no impact on sending but might just have an issue when saving the sent item in the IMAP folder ... if you did not refresh (re-subscribe to) the IMAP folders.

The following are mailboxes on the same mail server (Not Plusnet's)...

Note that for the first, the "other" folders appear under the inbox folder - this mailbox DOES NOT specify the root folder.

The second specifies the root folder and the "other" folders appear as peers to the inbox.

Why this happens has eluded me for several years.  What I suspect is this is connected to how the mailbox is accessed for the very first time after it was created: all of the services where I have seen this issue use the Round Cube webmail interface.  I have been known to use that to log into a new mailbox as soon as it was created to check it is working, before configuring on a local client.  I thus speculate that this could be a factor and indeed could be similar for other first touch clients too.

[#5]

Thank you for your explanations.

After adding "inbox" to Root Folder Path I restarted Laptop and I did see a change in File structure for the other components of the mail box (sent, draft etc) as you illustrated.

More importantly, after taking out "inbox" from the Root Folder Path (and restarting), the mailbox is now working properly for the past two days.........  So thank you.

I feel it is one of those, as you said .....Simple answer - "Because it will usually probably fix the issue".

So thank you for solving..

John_B

[#6 · Accepted solution]

Hi John,

You are welcome.  If the advice fixed the issue for you, might you please click the big green button, which will indicate to others experiencing the symptoms what might fix the problem for them too.