VM

vm-imap-protocol-error: expected UID...

Bug #494806 reported by Uday Reddy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Fix Released
Low
Uday Reddy

Bug Description

<email address hidden>

I managed to make this work with google, but
not with my actual work place imap server. I am getting

Logging into the IMAP server...
vm-imap-protocol-error: IMAP protocol error: "expected UID,
RFC822.SIZE and (FLAGS list) in FETCH response"

Related branches

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

> VM FETCH 1:1 (UID RFC822.SIZE FLAGS)
> > * 1 FETCH (FLAGS () UID 59171 RFC822.SIZE 5233)
> > VM OK Completed

Darn, the server is returning the three things in a different order!
VM should be able to process that. I will do a fix.

Changed in vm:
status: New → Confirmed
importance: Undecided → Critical
assignee: nobody → Uday Reddy (reddyuday)
milestone: none → 8.1.0-beta
Revision history for this message
Uday Reddy (reddyuday) wrote :

Eli, the current revision 643 should fix this problem. Can you try it? -- Uday

Changed in vm:
status: Confirmed → Fix Released
Revision history for this message
mere user (emacs-user) wrote :

nice. this works when I set the promary inbox to an imap folder for the server that previously did not work. thanks!

so far the good news.

Now, another imap-related problem: when I use vm-visit-imap-folder and I have the appropriate variable vm-imap-account-alist set to a list of two possible imap accounts, with the password field specified as *, I get the following error message:

Checking for new mail for /Users/me/Mail/imap-cache/imap-cache-c...
byte-code: No password in IMAP maildrop specification, "imap-ssl:imap.computer.edu:993::login:me:*"

note that the specification inbox is missing after 993, although it is included in the account definition.

thanks...

Revision history for this message
Uday Reddy (reddyuday) wrote : [Bug 494806] Re: vm-imap-protocol-error: expected UID...

mere user writes:

> Checking for new mail for /Users/me/Mail/imap-cache/imap-cache-c...
> byte-code: No password in IMAP maildrop specification,
> "imap-ssl:imap.computer.edu:993::login:me:*"

That is a bad error message. The real problem is that you need
another * in your account spec. Instead of 993:: you need to put
993:*:

Cheers,
Uday

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

mere user writes:

> note that the specification inbox is missing after 993, although it is
> included in the account definition.

I missed this line earlier. You need to send me your setting for the
vm-account-alist so I can see what problem it might have. You should
of course remove any passwords you might have put there and replace it
with *.

In future, please use the vm-submit-bug-report function which will do
all this automatically.

Cheers,
Uday

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

From: emacs user <email address hidden>

Hi Uday, ok, I just got it.  this is simply due to my misunderstanding.  I didn't realize that when prompted for the imap folder I need to specify it as string:inbox or string:Sent etc.  this works very nicely now that I figured this out, sorry for wasting your time, many thanks for your patience!  cheers, E

Changed in vm:
status: Fix Released → In Progress
importance: Critical → Low
Revision history for this message
Uday Reddy (reddyuday) wrote :

It seems that the bad error message arises if an IMAP account name is given with vm-visit-imap-folder, but no folder name. Calls for a better error message.

Uday Reddy (reddyuday)
Changed in vm:
status: In Progress → Fix Committed
Uday Reddy (reddyuday)
Changed in vm:
status: Fix Committed → Fix Released
Uday Reddy (reddyuday)
Changed in vm:
milestone: 8.1.0b → 8.1.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.