On Wed, 2003-02-19 at 01:42, Mark Crispin wrote: > On Tue, 19 Feb 2003, Timo Sirainen wrote: > > Must parent mailboxes be listed before their children? I don't see this > > defined anywhere, but I know some clients will break if they're not. > > There is no such requirement; and clients which presume such are broken.
OK. OSX's Mail.app might be broken then, except I didn't actually send the parent at all, so it might have been because of that. Have to find out. > However, there is nothing that precludes a mail store from working > differently. Consider a mail store in which the names are flat, but by > convention "." is a hierarchy delimiter and "%" breaks on ".". Unless > that mail store is careful to sort its names, a child could conceivably be > listed before a parent. Right, that's how Courier's Maildir support works. I don't know if Courier does any sorting though. Also LSUB seems to do with UW imapd that if child was subscribed before parent. Although subscribing to directories isn't very useful.. I guess duplicates are permitted too? If there's a/b and a/c subscribed, LSUB "" % gives: * LSUB (\NoSelect) "/" a * LSUB (\NoSelect) "/" a > > Requesting LIST "" mail/% from UW imapd shows also "mail/" in the reply, > > is this required? > > Yes. RFC 2060, bottom of page 31: > > [...] If the "%" wildcard > is the last character of a mailbox name argument, matching levels What about LIST "" mail/* then? :) Oh well, since % wants it I'll just send it with both.
