On Mon, 15 Sep 2003, Arnt Gulbrandsen wrote: > That client is asking information about mailboxes whose names start with > "foo/" and contain exactly one "/", right? > "foo" does not match that, so why should the server mention "foo" at all? > "foo/" is just one of the umpteen million possible names that don't > actually correspond to a mailbox. Why should the server mention any of > them?
In the case where foo has children (which was Timo's question), that makes sense. But what if foo does not have children? If the server doesn't list "foo/" in that case, then it's saying that the hierarchical name foo doesn't exist. IMHO, "foo" and "foo/" should be treated as equivalent in all cases except for CREATE. This means that if foo is \NoSelect then foo/ should also be \NoSelect; but if foo is selectable then foo/ should also be selectable. If you work out the causes and effects, it's only sane way to do it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
