We have an application that needs to read Yahoo via IMAP. For internal reasons, I need to loop twice through the message processing steps and the second time through, I am getting a weird operation and a LastResponse. Here is what the stripped down code looks like (removed our stuff and all the typical Chilkat error checking to make sure everything works right)....
The section that says TESTING CODE is what I put in to try to figure out what was going on. The first time through the loop, everything is fine. The second time, we get a 0 count and the Last Response reads:
"aaah BAD [SERVERBUG] UID FETCH Server error - Please try again later"
I can move the Loop to encompass all the code from the CONNECT down, but when I do that, sometimes Yahoo itself blocks the account because too many logins within a short period of time... that is why we moved the login steps OUT of the loop.
Any one have any suggestions or what this error message might refer to?
asked Dec 27 '12 at 21:11
To understand the problem better, set the KeepSessionLog property = true prior to connecting, and then examine the full contents of the SessionLog property after the error occurs. It should provide a detailed listing of each IMAP command sent, and each response received, leading up to the error.
The error implies that it's somehow a bug on the server side, but regardless, maybe something can be gleaned from the session log that might provide a clue on how to avoid it. For example, maybe calling imap.Noop() might be sufficient at a certain point. It's impossible to know without more detailed information.
answered Dec 28 '12 at 09:31
The KeepSessionLog didn't show anything odd other than the same fail message. BUT.... putting the NOOP() right at the beginning of the loop corrected the problem.
So, I guess I'd like to know... what does a NOOP() command do? Is it like some sort of "wakeup" call?
Thanks for your help...
answered Dec 31 '12 at 11:51