Comment 10 for bug 909908

There was a double encoding: vm-read-imap-folder-name calls vm-imap-encode-list-to-spec, which calls utf7-encode and thus returns an already encoded string to a function that normally takes and unencoded string.

The attached diff (relative to revision 1333) produces a version that works fine for all the folder operations I tend to use.