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
imap-proto is 0.16.2 in the lockfile. I tried plugging it into a test there and it returned an error (i directly copy pasted the email from the terminal, so this might have caused some CRLF to disappear). The email used was the notification email i got from github for your reply above.
This happens to any UID email.
#[test]fnmy_test(){let lines = b"* 20763 FETCH (BODY[1] {506}\r\nDoes it only happen with this particular message or with any messages? Could you extract the input and try to turn it into an `imap-proto` test, e.g. try inserting it somewhere here: https://github.com/jonhoo/rust-imap/blob/main/src/parse.rs--Reply to this email directly or view it on GitHub:https://github.com/async-email/async-imap/issues/71#issuecomment-1483830410You are receiving this because you authored the thread.Message ID: <async-email/async-imap/issues/71/[email protected]>)A008 OK Success\r\n";println!("{:#?}", parse_response(lines));}
The above returns an Err with the bytes and code: TakeWhile1
Running any of these:
(with any valid uid)
causes no body, text or any other data to be parsed, and the trace shows it hitting this:
async-imap/src/imap_stream.rs
Line 123 in 60ed0ff
The
need minimum X bytes
is always a little lower than the size of the data returned. In this case 220 bytes returned, but it saysminimum 130
.Run with gmail imap servers, with this crate setup:
calling
BODY[]
orBODY.PEEK[]
or any other call works fine.Connecting to the imap server directly like so:
and running the same commands (with same UIDs) seems to work fine.
The text was updated successfully, but these errors were encountered: