Microsoft Technology Licensing, LLC

Vikram Kakumani

Lynn Ayres

Mauktik Gandhi

Mashuri R Libman

Anatoly Victor Koretsky

Jack Kabat

Benjamin Travis Stull

Andrey Shur

Wilbert De Graaf

Neeraj Garg

Jason Eric Brewer

Scott David Hoogerwerf

Gregory Gourevitch

Michael B Mitchell

Ram Viswanathan

Vidyaraman Sankaranarayanan

Nipoon Malhotra

Karthik Lakshminarayanan

Sarath Madakasira

Tatiana Shubin

Joseph Schulman

Yehia Ali Zayour

Brian R Hall

Alex Dubovik

Gavarraju Nanduri

Anthony Joseph Girolamo

Yiming Li

Kiran Sagi

Steven C Yee

A simple mail transfer protocol ('SMTP') computer fails to deliver a multi-recipient e-mail to another SMTP computer. The SMTP computer generates a multi-line SMTP response including a per-recipient delivery status for each recipient of the multi-recipient e-mail message. The multi-line SMTP response may include a line for each recipient of the e-mail message. The multi-line SMTP response alternatively may include a line only for recipients for which delivery of the e-mail message has failed.

Communicating per-recipient delivery statuses of multi-recipient messages in multiline simple mail transfer protocol responses

System and methods for the implementation and/or enforcement of an email policy for an organization's email system are presented. A Data Loss Prevention (DLP) policy may be implemented on top of the email system. In one embodiment, the DLP policy may comprise modules and/or processing that tests emails for such sensitive data within emails. If an email comprises such sensitive data, then the DLP policy directives may specify processing to be applied as part of each stage of mail processing, from authoring to mail processing on the server and delivery. A single policy may be authored and managed that will apply the policy directives uniformly across all aspects of the message lifecycle. Each of the message policy enforcement systems may evaluate the single policy definition and apply the policy directives in a manner consistent with the contextual evaluation of the policy.

Uniform policy for security and information protection

Systems and/or methods for deploying and implementing data loss prevention (DLP) policy definition that may encapsulate the requirements, control objectives and directives, and/or the definitions of sensitive data types as stipulated directly or indirectly by the regulatory policy are disclosed. In one embodiment, DLP policies may be identified by an organization to run on top of a set of electronic file systems (e.g., email systems, file systems, web servers and the like). Organizations and their administrators may implement a set of DLP policy instance which are derived from DLP policy templates. DLP policy templates may comprise both structure and meaning&#x2014;and may acquire a given DLP policy by the replacement of parameterized expressions with desired parameter values. In another embodiment, the state of the DLP policy instance may change according to the lifecycle of the policy instance deployment.

Data detection and protection policies for e-mail

In order to allow a single user registered on a single local host or other machine to access multiple shared resources on a remote host, an aliasing mechanism is employed so that multiple concurrent connections can be established by the user to a single remote host, with each connection using a different identity. Each connection can therefore be used to access a different shared resource on the remote host. In some illustrative examples, a user's identifier such as his or her machine log-in identification may be associated with two or more resource sharing aliases. As a result, two or more resource sharing sessions can be established by the user with a single remote host, with each of the sessions using a different one of the aliases. The resource sharing sessions are usually established in accordance with a resource sharing protocol such as the Server Block Message (SBM) protocol.

Software-based aliasing for accessing multiple shared resources on a single remote host

Aspects of the subject matter described herein relate to a mechanism for seamlessly changing a network mode of a network device that is connected to multiple nodes. In aspects, agents reside on the nodes. A master agent communicates with the other agents and receives the capabilities of the nodes on which they execute. The master agent creates a data structure that includes the settings needed to connect using the new network mode. The master agent distributes this data structure to the other agents and each agent stores settings associated with the current network mode in case a rollback is needed. The master agent then instructs the other agents to begin communicating using the new network mode and the network device is reconfigured. If the master agent does not receive success acknowledgments from all of the other agents, the master agent initiates a rollback procedure.

Automated configuration of network mode

Use of software applications is detected by categorizing components of applications into a usage manifest and implementing a usage detection background service on a client PC that monitors the components according to the usage manifest. The application components are categorized based on the mode of user interaction as well as the component's correlation to active use of an application. The background service tracks events and activities associated with the application components to generate usage metrics that include the frequency of unique launches of an application and the duration of each unique use. A usage manager for the background service may utilize the usage metrics for a component independently, or combine metrics for multiple components in cases where applications work in an interactive manner (such as a plug-in to a web browser) in order to compute application usage by comparing the metrics against predefined thresholds.

Reliable and accurate usage detection of a software application

Reputation based firewall policy techniques are described, in which, a computer-implemented method may be employed to collect data from a plurality of clients regarding an application attempting to access a network via the clients. The collected data may be exposed to a community of users to obtain feedback on the application which is used to produce a reputation for the application. The reputation may then be provided to the plurality of clients to determine whether to permit the attempt by the application.

Reputation driven firewall

Targeted rules and action based support techniques are described, in which, operational data collected from a plurality of clients is used to generate support instructions for troubleshooting operational problems of the clients. Clients are provided targeted access to support instructions based upon information included in the support instructions which matches the support instructions to the clients. In an implementation, clients may be placed in one or more groups based on the analysis of the operational data and may receive support instructions corresponding to the group automatically and without user intervention.

Targeted rules and action based client support

Growing community of inventors

Kirkland, WA, United States of America

Vikram Kakumani