0 votes

we're encountering an error that may have been around for a while, since migrating to Office 365. A small number of users are reporting some issues with a custom application we created using the Limilabs Mail component. Please consider the following pseaudo code:

using (Imap imap = new Imap()) {
  imap.ConnectSSL(serverImap);
  imap.UseBestLogin("user", "pass");

  imap.SelectInbox();

// Do some other stuff
}

The line imap.SelectInbox(); will, for only some users, generate an ImapResponseException with message "INBOX doesn't exist".

If I check that using the GetFolders() function, this appears to be correct.

However, I cannot find ANY inbox folders, not even under another name. I do see other expected folders like Sent Items etc.

So my question: what is the problem here? How can I access the root folder/inbox for these users?

by

1 Answer

0 votes
 
Best answer

I've already found the problem. Webmail was "normal", no visible issues there.

I found the cause to be that the webmail had its normal, usual INBOX, translated to our language, "Postvak IN".

Then, when inspecting the folder structure in WebMail, I noticed (after looking multiple times, 50+ folders) that there was another item "Inbox" as a subfolder of the root Inbox.

I tried renaming that to InboxOLD and voila, suddenly SelectInbox() did work as expected.

It seems that, long before I was even working here, we have been working with Lotus Notes and that has been completely replaced by Microsoft Office (for years already).

We believe this migration process to be the culprit of this extra Inbox folder and causing errors for the users that have had their account since then. What's strange is that, up until today, we never received any errors or complaints. Maybe MS changed something.

by (301k points)
...