Re: nnimap compatibility issues (UTF-7, msg count, SEARCH vs. group

[Dave Love <d.love@dl.ac.uk>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1298 bytes --]

Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:

> 1. UTF-7 decoding mangled
>
> Here's the IMAP excerpt:
>
> 1 CAPABILITY
> * CAPABILITY IMAP4 IMAP4rev1 LITERAL+ UIDPLUS X-NETSCAPE
> 1 OK Completed
> 2 LOGIN "hohohoimnottellingyou" "youdlovetoknow"
> 2 OK User logged in
> 3 LIST "" "*%"
> * LIST (\Noinferiors ) "/" "Trash"
> * LIST (\Noinferiors ) "/" "Unerw&APw-nscht"
> ...
> 3 OK Completed
>
> The "Unerw&APw-nscht" string is misdisplayed in the server buffer, it
> prints as "Unerw.ünscht";

I'm not sure what that means and what exactly goes wrong.  Where is it
decoded from the utf-7?

> UTF-7 decoding is on. However, it appears
> correctly as "Unerwünscht" in other client software, namely Sylpheed
> 0.8.11claws and Mozilla 1.3. Just in case: CVS 5.10.x Gnus, emacs 21.3.

Did this work before I changed utf7.el recently to cope with more than
Latin-1?  If so, it's probably a coding conversion confusion, and
perhaps the dot is a mangled \201 or similar.  Previously the decoder
returned a unibyte string, which doesn't make much sense.  As far as I
could tell, that just happened to work by automatic conversion (in a
Latin-1 session).  You could test it by commenting out
`mm-enable-multibyte' in `utf7-decode'.  I can't, I'm afraid.