On Sat, 2013-05-25 at 02:12 +0300, Timo Sirainen wrote:
IMAP protocol requires that one character is reserved for being hierarchy separator. There's no way around that. But with listescape plugin you can use any other character. Okay... than IMAP really sucks in that matter ^^... why not allowing it to be used quoted ... weird...
IIRC, clients can find out that character via the LIST command, right? So there should be no need for them to block anything else but that specific character (per server).
Right. It encodes those chars that can't be used in filesystem, but can be used in IMAP protocol. With Maildir the separator is always '.' in the filesystem well unless one use LAYOUT=fs
, but it can be something else visible to IMAP clients, which allows using '.' in IMAP protocol but not in filesystem unescaped.
but that basically also means that the plugins will never encode characters but . and / (okay and that ~ case, which AFAIU wouldn't be strictly necessary), right?
It will encode "/" because it can't be used in the POSIX filenames. And it will encode "." only when LAYOUT=fs is _not_ used. Other Unicode chars are already encoded by IMAP via UTF7 and can go straight into the FS.
And the virtual separator cannot be used, regardless what one does... Is this just an IMAP issue or also a POP issue?
And how are other unicode chars encoded in POP? I ask cause then I'd update the wiki a bit.
Cheers, Chris.