IMAPListMessages error code (-1307)
Kelly Burgess
kellyb at montana.com
Mon Sep 18 03:57:00 EDT 2017
Hi Mike,
>So what does -1307 mean, and then I might know how to fix it.
Here's a batch of strings from the Localizable.strings file in the wecommand.u_external file in Studio 8.0.3. Given that the documentation of the group ends with
-1302: IMAP: the server response to the CHECK command was incorrect
I think you can extrapolate from these strings that -1307 is probably "Received a header that was not requested in a FETCH response".
Kelly
------------------
"COMP_RES_2299" = "Web Enabler: IMAP: bad message length in FETCH response";
"COMP_RES_2300" = "Web Enabler: IMAP: unrecognized data item in response when FETCHing message or headers";
"COMP_RES_2301" = "Web Enabler: IMAP: the server response to the NOOP command was incorrect";
"COMP_RES_2302" = "Web Enabler: IMAP: the server response to the CHECK command was incorrect";
"COMP_RES_2303" = "Web Enabler: IMAP: The length of the additional headers requested is too long";
"COMP_RES_2304" = "Web Enabler: IMAP: FETCH response invalid";
"COMP_RES_2305" = "Web Enabler: IMAP: Selected headers not returned in FETCH response when listing messages";
"COMP_RES_2306" = "Web Enabler: IMAP: Invalid header line in FETCH response";
"COMP_RES_2307" = "Web Enabler: IMAP: Received a header that was not requested in a FETCH response";
"COMP_RES_11004" = "Web Enabler: Sockets: Interrupted function call";
"COMP_RES_11009" = "Web Enabler: Sockets: Bad file descriptor";
More information about the omnisdev-en
mailing list