dovecot - Aug 2010 - \" character in folder name results in strange LIST

Hi Timo,
>> * LIST (\HasNoChildren) "/" "folder1"
>> * LIST (\HasNoChildren) "/" "folder2"
>> * LIST (\HasNoChildren) "/" {9}
>> six"wafer
>> . OK List completed.
>> 
>> Note the {9} length of the following real folder name. Is this normal
>> handling of special folder names ?
>Yes.

Well, I did try other servers and e.g. on scalix I'm getting this:

* LIST (\X-DirectRef=000d7f94a4731510 \X-ModDate=20100814200222) "/"
"six\"wafer"

I cannot find anything relevant in RFC3501
>> Mail clients do not seem  to like this response.
>What clients? They're buggy then.. Well, of course, way too many clients
are :(
at least Thunderbird will go totally crazy when getting this kind response. (My
old python scripts
expecting string, not a tuple go crazy as well... :-< )

On 14.8.2010, at 21.15, Samuel Kvasnica wrote:
> Well, I did try other servers and e.g. on scalix I'm getting this:
> 
> * LIST (\X-DirectRef=000d7f94a4731510 \X-ModDate=20100814200222)
"/" "six\"wafer"
> 
> I cannot find anything relevant in RFC3501
ABNF is the relevant part. You'll get to the literal from mailbox-list:

mailbox-list    = "(" [mbx-list-flags] ")" SP
                   (DQUOTE QUOTED-CHAR DQUOTE / nil) SP mailbox

mailbox         = "INBOX" / astring

astring         = 1*ASTRING-CHAR / string

string          = quoted / literal

literal         = "{" number "}" CRLF *CHAR8
                    ; Number represents the number of CHAR8s

On 08/15/2010 02:24 PM, Timo Sirainen wrote:
> On 15.8.2010, at 7.54, Samuel Kvasnica wrote:
>
>> 12 subscribe "Trash/aaa/"
>> 12 NO Invalid mailbox name: Trash/aaa/   <=== non-existing child
folder,
>> ERROR
>> 13 unsubscribe "aaa/"
>> 13 NO Invalid mailbox name: aaa/ <=== non-existing child folder,
ERROR
> Set:
>
> imap_client_workarounds = tb-extra-mailbox-sep
>
just swapped shortly back to non-fs maildir layout for a test - that one
works normally. So there must be a bug
in layout=fs implementation, it is listing the parent directory as child !

On Wed, 2010-08-18 at 12:48 +0200, Samuel Kvasnica
wrote:
> This is a very nasty mess. If there are some ancient clients like pine
> or whatever we used on vt100 in the 90th that need broken LIST command,
> there should be a workaround setting for that. 
Hey! I still use pine. With mouse-in-xterm mode enabled it works really
nicely on devices with a touch screen, and it makes excellent use of
small screens and limited network bandwidth.

-- 
dwmw2

On 08/19/2010 01:48 PM, David Woodhouse wrote:
> On Sat, 2010-08-14 at 23:36 +0200, Samuel Kvasnica wrote:
>> Well, it looks like at least Thunderbird v3.1.2 is buggy then. Are
there
>> any non-buggy clients anyway ...? 
> Evolution (>=2.30.2) with the imapx back end gets it right. I know this
> because I fixed it myself a few weeks ago.
>
Well, David, if evolution was not such an instable beast... we did few
evaluations from openSuSE10.3 up to 11.2 recently,
and it was a no-go, except for basic imap usage. As soon as more
connectors/plugins are involved, it is a nightmare.
Plus, we unfortunately want it also on Win32 Platform.
I just wish it had the plugin system of TB and so many usable plugins.
As of TB2, evolution looked more
sexy, eye-candy, compared with TB3+lightning not anymore, maybe except
for the addressbook which is rather weak in TB.

Integration with a groupware is also an important issue: few years ago,
we failed getting it work properly with scalix11, now there is no chance
to get
it work with open-xchange 6.x - and nobody cares, it seems like the
evolution development is stalled for a couple of years.

So for groupware usage in our case, there are 3 more clients left: TB
(seems to be the best), kmail (also few stability issues) and outlook
(but that one does not really work with IMAP...). One would not expect
it is in 2010 still so hard to put together a good, opensource
mail/groupware system... but we are very close now.