2.2.7 [RFC3501] Section 5.1, Mailbox Naming

V0008:

The specification takes no position on case-sensitivity in non-INBOX mailbox names.

Microsoft Exchange Server 2007, Microsoft Exchange Server 2010, Microsoft Exchange Server 2013, Microsoft Exchange Server 2016

Microsoft Exchange Server is case-insensitive regarding non-INBOX mailbox names.

V0009:

The specification states: "Any character which is one of the atom-specials will require that the mailbox name be represented as a quoted string or literal."

Exchange 2007

Microsoft Exchange returns a literal for a mailbox name that includes the backslash character ("\"), but does not return a literal for a mailbox name that includes other atom-specials.

Exchange 2010, Exchange 2013, Exchange 2016

Microsoft Exchange returns a literal for a mailbox name that includes the backslash character ("\") or the double-quote character ("""), but does not return a literal for a mailbox name that includes other atom-specials.

V0010:

The specification states: "Although the list-wildcard characters ('%' and '*') are valid in a mailbox name, it is difficult to use such mailbox names with the LIST and LSUB commands due to the conflict with wildcard interpretation."

Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016

Microsoft Exchange allows a mailbox name to contain a wildcard character and other special characters (such as atom-specials), provided that the characters are escaped.

V0011:

The specification states: "Usually, a character (determined by the server implementation) is reserved to delimit levels of hierarchy."

Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016

Microsoft Exchange uses the forward slash ("/") as the hierarchy delimiter.

V0012:

The specification states: "Two characters, '#' and '&', have meanings by convention, and should be avoided except when used in that convention."

Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016

Microsoft Exchange allows a mailbox name to contain "&", provided that the "&" is encoded as specified in section 5.1.3 of the specification. An unescaped "&" would be treated as a shift to the modified base64 encoding, as described in section 5.1.3 of the specification. Microsoft Exchange allows unescaped "#" in folder names.

C0003:

The specification does not impose any limitations on mailbox hierarchy depth.

Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016

Hierarchy depth is limited to 31 levels.

C0004:

The specification does not impose any limitations on the length of a mailbox name.

Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016

Mailbox names are limited to 250 characters. If a mailbox exists on the server with a name that contains more than 250 characters, the name will be truncated when the mailbox is retrieved.

Show: