1.1 Glossary
This document uses the following terms:
address book: A collection of Address Book objects, each of which are contained in any number of address lists.
calendar: A date range that shows availability, meetings, and appointments for one or more users or resources. See also Calendar object.
Calendar folder: A Folder object that contains Calendar objects.
Calendar object: A Message object that represents an event, which can be a one-time event or a recurring event. The Calendar object includes properties that specify event details such as description, organizer, date and time, and status.
client-side rule: A rule that has at least one action that is executed by a client because it cannot be executed by a server.
Common Views folder: A special folder that contains the data for default views that are standard for a message store and can be used by any user of a client that accesses the message store.
contact: A person, company, or other entity that is stored in a directory and is associated with one or more unique identifiers and attributes, such as an Internet message address or login name.
Contact object: A Message object that contains properties pertaining to a contact.
Contacts folder: A Folder object that contains Contact objects.
Container class: The value of the PidTagContainerClass property on a folder, which indicates the default Message object type for the folder.
conversation action: A limited set of actions that a user applies to all Message objects that have the same PidTagConversationId value. The action is applied to all Message objects that are currently in the store or are delivered in the future.
Deferred Action Message (DAM): A hidden message indicating to a client that it needs to execute one or more rules on another user-visible message in the store.
Deferred Error Message (DEM): A hidden message indicating to a client that it needs to present the user with an error indicating that a server-side rule failed to execute.
delegate: A user or resource that has permissions to act on behalf of another user or resource.
Delegate Information object: A Message object that contains properties specifying delegate access settings for resources in a delegator's mailbox.
Deleted Items folder: A special folder that is the default location for objects that have been deleted.
Drafts folder: A special folder that is the default location for Message objects that have been saved but not sent.
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].
entry ID: See EntryID.
EntryID: A sequence of bytes that is used to identify and access an object.
folder associated information (FAI): A collection of Message objects that are stored in a Folder object and are typically hidden from view by email applications. An FAI Message object is used to store a variety of settings and auxiliary data, including forms, views, calendar options, favorites, and category lists.
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.
free/busy message: A message that is stored in a public folder and contains free/busy data.
Inbox folder: A special folder that is the default location for Message objects received by a user or resource.
Journal object: A Message object that represents an entry in a journal or log and adheres to the property descriptions that are described in in [MS-OXOJRNL].
Junk Email folder: A special folder that is the default location for Message objects that are determined to be junk email by a Junk Email rule.
Junk Email rule: An extended rule that describes a spam filter.
little-endian: Multiple-byte values that are byte-ordered with the least significant byte stored in the memory location with the lowest address.
locale: A collection of rules and data that are specific to a language and a geographical area. A locale can include information about sorting rules, date and time formatting, numeric and monetary conventions, and character classification.
mailbox: A message store that contains email, calendar items, and other Message objects for a single recipient.
message class: A property that loosely defines the type of a message, contact, or other Personal Information Manager (PIM) object in a mailbox.
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.
Note object: A Message object that represents a simple text note in a messaging store and that adheres to the property descriptions that are described in [MS-OXONOTE]. A Note object functions as an electronic equivalent of a paper sticky note.
Outbox folder: A special folder that contains Message objects that are submitted to be sent.
Personal Distribution List object: A Message object that contains properties pertaining specifically to user-created distribution lists.
public folder: A Folder object that is stored in a location that is publicly available.
Really Simple Syndication (RSS): An XML-based syndication format for content, as described in [RSS2.0].
Receive folder: A Folder object that is configured to be the destination for email messages that are delivered.
recipient: An entity that can receive email messages.
reminder: A generally user-visible notification that a specified time has been reached. A reminder is most commonly related to the beginning of a meeting or the due time of a task but it can be applied to any object type.
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.
restriction: A filter used to map some domain into a subset of itself, by passing only those items from the domain that match the filter. Restrictions can be used to filter existing Table objects or to define new ones, such as search folder or rule criteria.
root folder: The folder at the top of a hierarchy of folders in a list.
ROP request: See ROP request buffer.
ROP response: See ROP response buffer.
search criteria: A criteria used to determine which messages are included in a folder with specific characteristics. It is composed of a restriction, which is the filter to be applied, and a search scope, which are the folders that contain the content to search.
search folder: A Folder object that provides a means of querying for items that match certain criteria. The search folder includes the search folder definition message and the search folder container.
Sent Items folder: A special folder that is the default location for storing copies of Message objects after they are submitted or sent.
server object: A class of object in the configuration naming context (config NC). A server object can have an nTDSDSA object as a child.
Server object handle: A 32-bit value that identifies a Server object.
special folder: One of a default set of Folder objects that can be used by an implementation to store and retrieve user data objects.
Store object: An object that is used to store mailboxes and public folder content.
Task object: A Message object that represents an assignment to be completed.
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.