You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the changes to the IDLE code, the IdleResumeCommand function in ImapClient is throwing exceptions on some operations (like MoveMessage). This seems to be because that code is catching the responses for the other commands (EXPUNGE for MoveMessage, I've also seen OK SUCCESS).
Is it really necessary to throw and exception if we don't get the response we were expecting? It seems like since we don't do anything with the response, it's pointless to throw an exception.
The text was updated successfully, but these errors were encountered:
After the changes to the IDLE code, the IdleResumeCommand function in ImapClient is throwing exceptions on some operations (like MoveMessage). This seems to be because that code is catching the responses for the other commands (EXPUNGE for MoveMessage, I've also seen OK SUCCESS).
Is it really necessary to throw and exception if we don't get the response we were expecting? It seems like since we don't do anything with the response, it's pointless to throw an exception.
The text was updated successfully, but these errors were encountered: