+- Atozed Forums (https://www.atozed.com/forums)
+-- Forum: Indy (https://www.atozed.com/forums/forum-8.html)
+--- Forum: Indy General Discussion (https://www.atozed.com/forums/forum-9.html)
+--- Thread: What might cause this IMAP client error - "'Unexpected: Non-last response line..." (/thread-865.html)
What might cause this IMAP client error - "'Unexpected: Non-last response line..." - edwinyzh - 12-11-2018
The error happens during the execution of TidImap4.UIDRetrievePeek, any hint as to trace the source of the issue?
And here is the full error message:
---------------------------
Debugger Exception Notification
---------------------------
Project program1.exe raised exception class EIdReplyIMAP4Error with message 'Unexpected: Non-last response line (i.e. a data line) did not start with a *, offending line: nthalten. Sollten Sie diese E-Mail irrt=C3=BCml='.
---------------------------
Break Continue Help
---------------------------
Thanks.
RE: What might cause this IMAP client error - "'Unexpected: Non-last response line..." - rlebeau - 12-12-2018
(12-11-2018, 05:49 AM)edwinyzh Wrote: The error happens during the execution of TidImap4.UIDRetrievePeek, any hint as to trace the source of the issue?
Not without seeing the complete IMAP response that was received from the peek command. But, the error basically means that the response contained at least 1 line of text that did not start with a leading '*' character, and that line was not the last line in the response. UIDRetrievePeek() sends a FETCH command, and every line in the response, except the last, should begin with "* # FETCH ..." (where '#' is an email message number), and the last line contains the final status code for the response (OK, NO, BAD).
RE: What might cause this IMAP client error - "'Unexpected: Non-last response line..." - edwinyzh - 12-12-2018
Thank you @rlebeau