I am starting a new post for this as an earlier one was marked “solved” and this isn’t solved and needs attention from eM Client.
I am getting a whole series of errors like this:
[IMAP] Cannot open folder “/Inbox”. (BAD Command Error. 12)
[IMAP] Cannot open folder “/Sent”. (BAD Command Error. 12)
Em Client 10.4.5298
I have tried:
Deleting the outlook[dot]com account and adding it back
Un-authorising the account at https://account.microsoft.com/privacy
Updating eM Client to 10.4.5298
None of these actions has helped.
I have EPIM Pro running on the same PC and it has no problems at all with outlook[dot]com.
There is clearly an issue with eM Client that need action from eM Client itself so please can we have some help.
I have tried:
Deleting the outlook[dot]com account and adding it back
Un-authorising the account at https://account.microsoft.com/privacy
Updating eM Client to 10.4.5298
There is now a newer V10.4.5326 just updated on the release history pages you can try and see if that helps. It’s a service update and bug fixes.
Before updating, make a manual backup first via “Menu / Backup” incase you need to restore for any reason. Also close eM Client before updating.
This error seems to come in waves, I thought it had disappeared with v10.4.5298 but came back. It still occurs with V10.4.5326.
Very annoying, this error got so bad yesterday that the Inbox on one account was inoperable for a couple of hours.
We have to wait until V11 comes out and see if the new protocol with Microsoft accounts fixes it. See Michael_Burger post here: Chronic problems using eM Client with hotmail and outlook - Mail - eM Client
Occasionally getting the same error for different folders in my Outlook account, including the Inbox. Incoming emails still comes through fine though.
Version 10.4.5298
Well this is IMAP (email) protocol error, the last update was only resolving Airsync protocol issues (calendar, tasks and contacts). We’ve seen the logs for this issue and it is clearly Microsoft sending us invalid data. More precisely sending us authentication error even though the authentication is correct. It seems there is not much we can do. It happens only for some particular accounts it seems.
Well we can track very exactly the bug to MS from the log files. Do you use IMAP in EPIM as well? It would be beneficial to see IMAP logs from both eM Client and EPIM. Maybe the Outlook.com bug happens only in combination with a specific IMAP feature that EPIM does not use. We can’t reproduce the error on any of our outlook.com test account, but we’ve received several log files from our uses and the bug on server side is very obvious.