I have been feeling a bit thick as well, reading this thread and struggling
to understand the issues involved. With the last few messages, I think I
may have finally seen the light.
Consider a store that can contain email messages, appointments, addresses,
notes, etcetera, with items of each class restricted to separate containers
but with all such containers in a common hierarchy. Am I correct in
thinking that this would be an example of a situation where the foo/ issue
arises? If so, then I well appreciate the desirability of a client's being
able to determine that it is unable to create a mailbox called, say,
Reminders because there happens to already be a notes-container with that
same name. I am not sure that I like the solution though.
But there is still something I seem to be missing. Is the idea that a
server should list such non-mail containers in, say, a LIST "" * or only in
a specific case such as LIST "" Reminders/%?
Pete Maclean
- RE: LIST Larry Osterman
