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

> 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.

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

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...

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

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

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

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.