vm-imap-server-timeout malfunctions
Bug #1082641 reported by
Uday Reddy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
VM |
Triaged
|
High
|
Uday Reddy |
Bug Description
Setting vm-imap-
Checking IMAP connection to server...
IMAP message unavailable: IMAP protocol error: "No response from the IMAP server"
However, the IMAP process buffer shows:
VM NOOP
VM OK Success
VM UID FETCH 3584:3584 (RFC822.SIZE)
* 79 FETCH (UID 3584 RFC822.SIZE 29450524)
VM OK Success
VM UID FETCH 3584:3584 (BODY.PEEK[])
* 79 FETCH (UID 3584 BODY[] {29450524}
Delivered-To: <email address hidden>
...
So, the NOOP succeeded and so did the FETCH. Did the timeout occur in the middle of FETCH? That is bad news.
Changed in vm: | |
milestone: | 8.2.0b1 → 8.2.0 |
To post a comment you must log in.
Attempting to further navigate through the folder while FETCH was still going on in the background produced the following problems:
Checking IMAP connection to server... or-marker- p, nil or-marker- p, nil or-marker- p, nil
Unable to load message; Wrong type argument: integer-
Retrieving message body... done
Checking IMAP connection to server...
Message body loaded
Checking IMAP connection to server...
Unable to load message; Wrong type argument: integer-
Checking IMAP connection to server...
Unable to load message; Wrong type argument: integer-