VM

vm-imap-server-timeout malfunctions

Bug #1082641 reported by Uday Reddy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Triaged
High
Uday Reddy

Bug Description

Setting vm-imap-server-timeout to 1 had the following effect. When an attempt was made to fetch an external message, notifications received were:

  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.

Tags: imap new
Revision history for this message
Uday Reddy (reddyuday) wrote :

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...
Unable to load message; Wrong type argument: integer-or-marker-p, nil
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-or-marker-p, nil
Checking IMAP connection to server...
Unable to load message; Wrong type argument: integer-or-marker-p, nil

Uday Reddy (reddyuday)
Changed in vm:
milestone: 8.2.0b1 → 8.2.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.