Re: FW: I-D ACTION:draft-gahrns-imap-namespace-00.txt

[John Gardiner Myers <[e-mail]>]

"Mike Gahrns (Exchange)" <[e-mail]> writes:
> In the draft, we state that ..."if INBOX exists, it MAY also appear in
> the #personal namespace as #personal/INBOX".   The way I read Chris's
> suggestion, was that if a server decided to include a #personal/INBOX
> then it should be the same as INBOX.  
> 
> INBOX remains as  the only guaranteed mailbox name.  #personal/INBOX is
> not guaranteed to be there, and in fact many servers (like cyrus) might
> map #personal to INBOX, and not provide a #personal/INBOX.

With a cyrus-style server, a user may request that a mailbox named
"#personal/INBOX" (or "user.myself.INBOX", etc.) be created.  On that
type of server, that would be a different mailbox than "INBOX".

With Chris' suggestion, such a server would have to check for and
prohibit such a mailbox from being created.  If the "INBOX" portion of
"#personal/INBOX" is further defined as being case-insensitive, this
gets really hairy on servers which are otherwise case-sensitive.

There are some mailbox name components, such as "INBOX" and
"#personal", which are defined in protocol for the convenience of
clients.  There are others, like the preferred namespace and the stuff
following the "#personal/" prefix, which are intended to be presented
to and interpreted by the user.  For internationalization and language
issues, it is important to keep the two types of name components
distinct and separate.

-- 
_.John Gardiner Myers	Internet: [e-mail]
			LoseNet:  ...!seismo!ihnp4!wiscvm.wisc.edu!give!up