Mark Crispin <[EMAIL PROTECTED]> writes: > The answer is simple: > > The "#driver.mbx/" prefix is a recognized only in the CREATE and (in the case > of zero-length files only) APPEND commands. [...] > Finally, the "#driver.mbx/" is not part of the IMAP protocol. IMAP > specifically shields the user from details of what format a mail > store may happen. The "#driver.mbx/" prefix is specifically a power > tool for people who know what they are doing.
Ok. I interprete this as IMAP client users should never try to create "#driver.mbx/foo" because it will not work with the IMAP client, as the IMAP client have no way of knowing about the server-specific hack but will rather assumes that the server behaves as in the RFC. The users should use telnet or some server-specific tool to send the CREATE command and then subscribe to the unprefixed name in their IMAP clients. I still think the server behaviour isn't really compliant though, from RFC 2060 on the CREATE command ,---- | The CREATE command creates a mailbox with the given name. An OK | response is returned only if a new mailbox with that name has been | created. `---- and protocol output ,---- | 456 CREATE "#driver.mbx/try" | 456 OK CREATE completed | 458 SELECT "#driver.mbx/try" | 458 NO SELECT failed: Can't open mailbox #driver.mbx/try: no such mailbox `---- the CREATE command did not create a new mailbox with the name the client gave it, so it is incorrect to return OK.
