O

OID

(object identifier) A value specifying the nature of an X.400 object. MAPI uses OIDs for various purposes, such as indicating the types of attached files. "Object" is a much more generalized concept in X.400 than in object-oriented programming. It can mean an algorithm, application, body part type, character set, external parameter, or message type, among other things. Also, it usually refers to a class of things, such as CRC-32, rather than one particular implementation of a 32-bit CRC (cyclic redundancy code).

one-off

British jargon for something that is used only once and not retained permanently. Also referred to as one-shot.

one-off address

A messaging address that represents a recipient that is not in the current address book. A one-off address is created by a client application or a service provider, either by presenting a complete address string for name resolution or by using a template supplied by an address book provider. An address string without an explicit address type is assumed to be an Internet address. Also referred to as a custom recipient. See also one-off template entry identifier.

one-off entry identifier

An entry identifier created from a one-off address and a display name. Also referred to as a custom recipient entry identifier. For more information, see Address Book Identifiers.

one-off table

A MAPI table object that provides access to information about supported one-off templates. Also referred to as a custom recipient table.

one-off template

A template for creating a one-off address.

one-off template entry identifier

An entry identifier held in an address book provider's one-off table and used to access a one-off template for creating a one-off address. Also referred to as a custom recipient template entry identifier. For more information, see Address Book Identifiers.

Outbox

A folder within the interpersonal message (IPM) subtree that is designated to hold outgoing messages until they are sent. See also IPM subtree.