1.1 Glossary

This document uses the following terms:

best body: The text format that provides the richest representation of a message body. The algorithm for determining the best-body format is described in [MS-OXBBODY].

Hypertext Markup Language (HTML): An application of the Standard Generalized Markup Language (SGML) that uses tags to mark elements in a document, as described in [HTML].

message body: The main message text of an email message. A few properties of a Message object represent its message body, with one property containing the text itself and others defining its code page and its relationship to alternative body formats.

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.

plain text: Text that does not have markup. See also plain text message body.

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.

Rich Text Format (RTF): Text with formatting as described in [MSFT-RTF].

rights-managed email message: An email message that specifies permissions that are designed to protect its content from inappropriate access, use, and distribution.

ROP request: See ROP request buffer.

S/MIME (Secure/Multipurpose Internet Mail Extensions): A set of cryptographic security services, as described in [RFC5751].

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.