On Mon, 15 Sep 2003, Timo Sirainen wrote: > Hmm. So is it necessary to send "foo/" at all if at least one of it's > children is listed?
IMHO, yes. Otherwise the behavior is inconsistent > 1 create dir/ > 2 list "" dir/% > Is it required to show the "dir/" entry? Yes, it is. The only difference between "dir" and "dir/" in the CREATE command is that "dir/" says "\NoInferiors must not be set in the name." It does *not* say "\NoSelect must be set." So, for a Maildir type name structure, I would claim that "CREATE dir" and "CREATE dir/" are exactly the same command. It is only for a structure in which a mailbox is the terminal node of hierarchy that it makes a difference. > Or if mailbox can contain children but currently doesn't, should list > "" mailbox/% show anything? Yes, it should show the mailbox. > > IMHO, "foo" and "foo/" should be treated as equivalent in all cases > > except for CREATE. > I've just returned NO to all such requests. I don't think that your server should do that. Note that I did not say "MUST NOT" do that; I am speaking my opinion, not necessarily what IMAP requires. However, this opinion is based upon the observation that other behaviors are likely to confuse clients even worse than they already are -- or worse, get clients to start claiming that flat-file structures are somehow "broken" because they do \NoSelect differently than Maildir. IMHO, a Maildir type structure should never use \NoSelect except in LSUB. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
