For a while now, every time I enter a virtual folder I get the uninformative error message attached here. I think the dialog should give more context to the user to be useful. At least the folder that was accessed should be mentioned so that I could check out, if that particular folder has some problems. For me as a technical user, it would be nice to know what was that "current command" that failed. The virtual folder searches messages from 67 different folders, so trying to find the culprit by trial and error is really tedious. The folder is in online search mode. The problem happens with IMAP connection to an Exchange server, if that would matter.

The same error is mentioned in Core bug 171197 comment 6, related?

> The same error is mentioned in Core bug 171197 comment 6, related? Thanks for pointing that out! It definitely seems related, I guess I'll have to reopen that. However, this bug is about the UI, _when_ an error happens: if at all possible, the message should provide more context, e.g. the folder name that had the failing command, so that the user can decide, if the contents of the virtual folder are OK, or even to debug and fix the problem by doing something to the offending folder. In my case the contents of the virtual folder seem OK, so I guess the failing folder is one of the less used folders out of the total 67 and I just miss its results.

improve summary with Unrecognized internal error: 0x8004050a etc