Mark, thanks for your response. Please allow me to share this with you.

Summarizing follow-ups on the mulberry-discuss at mulberry.com list in
response to my post there, these different LIST responses are what's
confusing Mulberry:

----- 2006g ----- (Mulberry works)
A00010 LIST "" "a/a2/a3/%/%"
* LIST () "/" a/a2/a3/a41
* LIST () "/" a/a2/a3/a42
A00010 OK LIST completed
----- 2006h ----- (Mulberry broken)
A00010 LIST "" "a/a2/a3/%/%"
* LIST () "/" a/a2/a3/a41/
* LIST () "/" a/a2/a3/a42/
A00010 OK LIST completed
-----2007d ----- (Mulberry broken)
A00010 LIST "" "a/a2/a3/%/%"
* LIST (\HasNoChildren) "/" a/a2/a3/a41/
* LIST (\HasNoChildren) "/" a/a2/a3/a42/
A00010 OK LIST completed

As an aside, it seems that Mulberry ignores the \HasChildren and\HasNoChildren attributes. Instead, it uses LIST .../%/% to
determine this.

Cyrus Daboo, author of Mulberry, stated:

Yes it does look like the trailing slash is the issue. The spec is not at
all clear on what it means to have a mailbox with a trailing slash and
how it might differ from one without. In theory what the server is doing
is perfectly "legal", so this does represent a bug in Mulberry. The
trivial fix would be to ensure the trailing slash (or appropriate
hierarchy delimiter) is removed from names returned by LIST.

I, too, wondered about what the trailing slash means. It appears the
intention is to make the answer more closely match the format of the
question.

I took the "trivial fix" cue and patched 2006h and 2007d to be like
2006g. Besides, I'm not equipped to patch Mulberry on Windows.

In src/osdep/unix/dummy.c (slightly reformatted here):

@@ -312,7 +312,7 @@
             }
                               /* try again with trailing / */
             else if (pmatch_full (path,pat,'/') &&
-                 !dummy_listed (stream,'/',path,LATT_NOSELECT,contents))
+                 !dummy_listed (stream,'/',tmp,LATT_NOSELECT,contents))
               break;
           }
           if (dmatch (path,pat,'/') &&

This avoids confusing Mulberry, but it probably reintroduces a bug. Therefore, I hope the community of Mulberry programmers effect a fix.

Thanks again and best wishes!
--
Bart

--On Tuesday, November 11, 2008 08:42 -0800 Mark Crispin <[EMAIL PROTECTED]> wrote:


It looks like Mulberry is confused by the CHILDREN extension.
Given that other clients don't work well without CHILDREN, your
best bet is to contact the author of Mulberry and ask him for
assistance in getting Mulberry fixed.

-- Mark --
8< clip 8<
_______________________________________________
Imap-uw mailing list
Imap-uw@u.washington.edu
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Reply via email to