User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.13pre) Gecko/20071022 Ubuntu/dapper-security Firefox/1.5.0.13pre Build Identifier: version 2.0.0.9 (20071031) There are a few problems with tags encoding when using custom tags: - Spaces are replaced with underscores, but underscores are stored as underscores too - It looks like tags are stored lowercase - It looks like the lowercase-ing is done after encoding to MUTF7, breaking the encoding. Examples: "UPPERCASE" is stored as "uppercase" "space tag" is stored as "space_tag" "underscore_tag" is stored as "underscore_tag" "accéntued" is stored as "acc&aok-ntued" The worst problem is for "accéntued", seen by other MUAs as "acc檉ntued" It would also be nice to keep casing, and to encode underscores as &AF8-, as in "underscore&AF8-tag"... Reproducible: Always Steps to Reproduce: Tag a message with "UPPERCASE", "space tag", "underscore_tag", "accéntued". From another MUA, you will see "uppercase, "space_tag", "underscore_tag, "acc檉ntued". Actual Results: The IMAP server sends: [10:11:17] IMAP4< * 1 FETCH (FLAGS (\Seen acc&aok-ntued space_tag underscore_tag uppercase) UID 53) Expected Results: It should have been [10:11:17] IMAP4< * 1 FETCH (FLAGS (\Seen acc&AOk-ntued space_tag underscore&AF8-tag UPPERCASE) UID 53)

we lower-cased because a particular imap server wasn't preserving the case of the keywords and Mark Crispin said that servers didn't need to preserve the case of keywords - I didn't realize we were doing that after the mutf7 conversion. Maybe we could change our code to make keywords case-insensitive, but try to maintain the case on the server, if the server supports it.

Do you happen to remember which IMAP server that is? I suppose maintaining case on the server is an easy fix for most of the people. It still leaves the problem of breaking extended chars (&AOk- versus &aok-), but for this I have no idea about a solution that wouldn't break existing tags. (A solution that breaks existing tags would be to encode them as quoted-printable UTF-8... qp-encoding being case insensitive). I'm interested in this, because I'm developing imap tags support for a concurrent MUA ;), (I noticed these problems when testing interoperability with TB).

I'm using case sensetive tag, and it won't work.