Abstract: Systems and methods for monitoring a plurality of mailboxes by a plurality of computer nodes. The plurality of computer nodes comprises a first computer node and a second computer node. The first computer node is configured to detect an update to a database record associated with a message store; determine, in response to detecting the update to the database record, a second computer node in the plurality of computer nodes to monitor the message store, based at least in part on an attribute stored in the database record; and update the database record to store an identifier corresponding to the second computer node. The second computer node is configured to: detect the update to the database record by the first computer node based at least in part on the identifier; and configure a monitoring process for the message store based, at least in part, on the attribute stored in the database record.

Abstract: Systems and methods for monitoring a plurality of mailboxes by a plurality of computer nodes. The plurality of computer nodes comprises a first computer node and a second computer node. The first computer node is configured to detect an update to a database record associated with a message store; determine, in response to detecting the update to the database record, a second computer node in the plurality of computer nodes to monitor the message store, based at least in part on an attribute stored in the database record; and update the database record to store an identifier corresponding to the second computer node. The second computer node is configured to: detect the update to the database record by the first computer node based at least in part on the identifier; and configure a monitoring process for the message store based, at least in part, on the attribute stored in the database record.

Abstract: Techniques for reconciliation and remediation of messages sent by a server for storage in an archive are described. Some techniques may comprise receiving a message to be reconciled corresponding to a message sent by a server to be stored in an archive. The received message may be categorized for reconciliation, and a delivery confirmation query may be issued to the archive according to categorization of the message for reconciliation. Based on the response to the delivery confirmation query, it can be determined with certainty whether the message sent to the archive for storage is indeed stored at the archive. Other embodiments are described and claimed.

Abstract: Architecture that facilitates cross-boundary message tracking based on a trust relationship in existence between a sender network and a recipient network. A tracking service is deployed in each network as a proxy to obtain message events for each hop that passes the message on to the recipient. Tracking can include a search task and a get task. Messages can be found in reports that match message search criteria. The search task returns an array of search results objects, each object identifying a single tracking report. A selected object is pipelined into the get task to return the detailed tracking report for the selected message.

Abstract: A schema for a rule transport engine to be applied to an email having multiple recipients. The schema defines a rule which executes one or more specific actions for a particular recipient or a particular group of recipients receiving a message instance of a bifurcated message when the message meets certain conditions.

Abstract: Policy rules for a particular communication mode are adapted and implemented for other communication modes in a dynamic and/or automated manner. Organization level and/or personal policies for one communication mode are evaluated and modified as necessary for other communication modes, which may be integrated with each other or distinctly managed. Rules may be adapted based on user, groups, or policy types.

Abstract: Architecture that facilitates cross-boundary message tracking based on a trust relationship in existence between a sender network and a recipient network. A tracking service is deployed in each network as a proxy to obtain message events for each hop that passes the message on to the recipient. Tracking can include a search task and a get task. Messages can be found in reports that match message search criteria. The search task returns an array of search results objects, each object identifying a single tracking report. A selected object is pipelined into the get task to return the detailed tracking report for the selected message.

Abstract: Policy rules for a particular communication mode are adapted and implemented for other communication modes in a dynamic and/or automated manner. Organization level and/or personal policies for one communication mode are evaluated and modified as necessary for other communication modes, which may be integrated with each other or distinctly managed. Rules may be adapted based on user, groups, or policy types.

Abstract: Techniques for reconciliation and remediation of messages sent by a server for storage in an archive are described. Some techniques may comprise receiving a message to be reconciled corresponding to a message sent by a server to be stored in an archive. The received message may be categorized for reconciliation, and a delivery confirmation query may be issued to the archive according to categorization of the message for reconciliation. Based on the response to the delivery confirmation query, it can be determined with certainty whether the message sent to the archive for storage is indeed stored at the archive. Other embodiments are described and claimed.

Abstract: A notification mechanism that aggregates multiple email tracking status updates into a new type of aggregated message, and transports this new type of message according to a configured interval. The tracking status transported in this aggregated status message can be a positive delivery event, a negative delivery event, hand-off of ownership, or any information to be communicated. This information can be delivered to email users to provide information about the message delivery and, routed to messaging system applications such as journaling (to allow rich delivery information in a journal report) and/or high-availability transport (to allow resubmission of a message in case of hardware failure).

Abstract: A schema for a rule transport engine to be applied to an email having multiple recipients. The schema defines a rule which executes one or more specific actions for a particular recipient or a particular group of recipients receiving a message instance of a bifurcated message when the message meets certain conditions.

Abstract: A schema for a rule transport engine to be applied to an email having multiple recipients. The schema defines a rule which executes one or more specific actions for a particular recipient or a particular group of recipients receiving a message instance of a bifurcated message when the message meets certain conditions.

Abstract: A schema for a rule transport engine to be applied to an email having multiple recipients. The schema defines a rule which executes one or more specific actions for a particular recipient or a particular group of recipients receiving a message instance of a bifurcated message when the message meets certain conditions.