1.1 Glossary

This document uses the following terms:

conversation: A single representation of a send/response series of email messages. A conversation appears in the Inbox as one unit and allows the user to view and read the series of related email messages in a single effort.

Email object: A Message object that represents an email message in a message store and adheres to the property descriptions that are described in in [MS-OXOMSG].

Folder object: A messaging construct that is typically used to organize data into a hierarchy of objects containing Message objects and folder associated information (FAI) Message objects.

handle: Any token that can be used to identify and access an object such as a device, file, or a window.

Message object: A set of properties that represents an email message, appointment, contact, or other type of personal-information-management object. In addition to its own properties, a Message object contains recipient properties that represent the addressees to which it is addressed, and an attachments table that represents any files and other Message objects that are attached to it.

message store: A unit of containment for a single hierarchy of Folder objects, such as a mailbox or public folders.

Post object: A Message object that represents an entry in a discussion thread stored in a messaging store.

recipient: An entity that can receive email messages. 

remote operation (ROP): An operation that is invoked against a server. Each ROP represents an action, such as delete, send, or query. A ROP is contained in a ROP buffer for transmission over the wire.

ROP request: See ROP request buffer.

search key: A binary-comparable key that identifies related objects for a search.

MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.