1.1 Glossary
This document uses the following terms:
action: A discrete operation that is executed on an incoming Message object when all conditions in the same rule are TRUE. A rule contains one or more actions.
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.
Contacts folder: A Folder object that contains Contact objects.
domain: A set of users and computers sharing a common namespace and management infrastructure. At least one computer member of the set has to act as a domain controller (DC) and host a member list that identifies all members of the domain, as well as optionally hosting the Active Directory service. The domain controller provides authentication of members, creating a unit of trust for its members. Each domain has an identifier that is shared among its members. For more information, see [MS-AUTHSOD] section 1.1.1.5 and [MS-ADTS].
extended rule: A rule that is added to, modified, and deleted from a server by using a mechanism other than standard rules, but is otherwise functionally identical to a standard rule.
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.
Inbox folder: A special folder that is the default location for Message objects received by a user or resource.
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.
mailbox: A message store that contains email, calendar items, and other Message objects for a single recipient.
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.
phishing: The luring of sensitive information, such as passwords or other personal information, from a recipient by masquerading as someone who is trustworthy and has a real need for such information.
phishing message: An email message that is designed to trick a recipient into divulging sensitive information, such as passwords or other personal information, to a non-trustworthy source.
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.
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.
ROP request: See ROP request buffer.
rule: An item that defines a condition and an action. The condition is evaluated for each Message object as it is delivered, and the action is executed if the new Message object matches the condition.
Simple Mail Transfer Protocol (SMTP): A member of the TCP/IP suite of protocols that is used to transport Internet messages, as described in [RFC5321].
spam: An unsolicited email message.
spam filter: A filter that checks certain conditions in a message to determine a spam confidence level.
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.