[Dovecot] Encoding dovecot keywords

[Ernesto Revilla Derksen]

Hi.

2011/4/10 Timo Sirainen <tss at iki.fi>

> On 9.4.2011, at 13.41, Алексей Сундуков wrote:
>
> > Ok, but if I write my own MUA application? If different MUA use it's
> > own encoding format I think it's bad, very very bad way. Because
> > application can't decode keywords written by another application.
>
> Yeah, it sucks.
>

Well, it could be worse. Dovecot's max length is configurable. We just need
atom compatible keywords. For latin written languages, this could be doable.
For other languages, it sucks. It would be better if keywords were that
UTF-7 modified thing, just like folder names, but that is not the standard
:-(


> > Can someone known a solution to this problem?
>
> No. You could try proposing a standard though.
> http://www.washington.edu/imap/lists/imap-protocol.html


This is cool!

Well, changing IMAP keywords to UTF-7-mod + specifiying min size supported
by IMAP servers and max size in capabilities anyhow would be a not too
intrusive change, right?

Regards.
Erny


>
> > 2011/4/9 Michael M Slusarz <slusarz at curecanti.org>:
> >> Quoting Алексей Сундуков <public-mail at alekciy.ru>:
> >>
> >>> But I can't understand what encoding use dovecot for keywords? I set
> >>> "тест" (number 5) keyword:
> >>>
> >>> cat dovecot-keywords
> >>> 0 &bcienqrbbeiepgqybdaetw-_&bdwenqrcbdoema-
> >>> 1 test
> >>> 2 $label1
> >>> 3 $label2
> >>> 4 $label3
> >>> 5 &beienqq6beeeqg-
> >>>
> >>> but "&beienqq6beeeqg-" do not convert to "тест". Why?
> >>
> >> Because only mailboxes are encoded in Modified UTF-7.  There is no
> >> equivalent encoding for keywords.  Keywords are *not* meant to be
> directly
> >> viewable by an end-user.  Converting between a keyword and the
> >> representation displayed to the user is the job of the MUA.
> >>
> >> michael
> >>
> >>
> >
>
>