`.Inbox` returning null about mailkit HOT 10 CLOSED

Since you are in direct communication with the MS Support, I'm going to close this because I'm 99% sure this is an Exchange issue (or a Office365 permissions issue).

I'll still be listening for notifications on this thread if there is anything you find out and if it is a MailKit issue, I'll reopen it (or you can reopen it).

The MS Support people are probably in a better position to help you at this point.

from mailkit.

This would only make sense, I think, if an INBOX couldn't be found. Do you have a protocol log that I could take a look at?

from mailkit.

@jstedfast not yet on the protocol log. going to work on putting that together, but need to spent a bit of time getting the app running locally, as it usually runs as an Azure function.

fwiw - I can access these users' inbox (they are technically a "shared" inbox in MS Outlook) from my own outlook account, which has access -- my current working theory is that Inbox is null because of a silent permissions issue 🤷🏻‍♂️ -- hopefully that protocol log will give some additional hints.

from mailkit.

One other piece of information, I tried Getting the first folder in the personal namespace, as shown below. That throws an index error, indicating that PersonalNamespaces is an empty list.

emailClient.GetFolder(emailClient.PersonalNamespaces[0]);

Working on that protocol log today.

from mailkit.

That suggests to me that probably a NAMESPACE command failed. That's probably also why Inbox is null.

from mailkit.

Hey @jstedfast I found a workaround for this authentication issue. Not pretty but it's going to do the job for now. I'm still actively engaged with MS support to track down the root cause. I will follow up on this ticket when I have more info -- in case it's helpful for error handling in Mailkit. Feel free to keep this issue open or closed in the meantime. Thanks for your quick responses on this 🙏🏻

from mailkit.

Is this one of those Exchange authentication issues where it says "User authenticated but not connected"?

from mailkit.

I haven't seen that anywhere in my logs. I do know that the imapClient.IsConnected property returns true.

from mailkit.

It reports true in the case I mentioned as well because there is a connection.

The problem I mentioned is Exchange thinking that there is no connection. It's a very bizarre error that I think (if my memory is correct), it has something to do with the user's Office365 settings not allowing IMAP connections, but the correct OAuth2 credentials were supplied in the AUTH command.

This results in Exchange getting confused and returning all sorts of errors to various commands like NAMESPACE.

from mailkit.

Here's an example: #1494

StackOverflow has a number of these as well, but no logs that I saw in the first few clicks

https://stackoverflow.com/search?q=%5Bimap%5D%5Boffice365%5D+authenticated+but+not+connected

from mailkit.