importaNt in Visual C#

Painting PDF 417 in Visual C# importaNt

Message classifications in Exchange Server 2010 are informational only;

they are not integrated with any transport rules or messaging records management functionality. however, they can be used as a predicate in transport rules, and transport rules can be configured to apply a message classification as an action. In addition, Exchange Server 2010 message classifications set on a message are only visible to the recipient when viewed in Outlook Web app, or with Outlook 2007 or Outlook 2010; Outlook 2007 and Outlook 2010 require additional configuration to apply and view Exchange Server 2010 message classifications.

When a user composes a message in Outlook Web App and Outlook 2007 and higher, the message classifications configured in Exchange Server 2010 are listed in the Permissions dialog

box, along with AD RMS templates, as shown in Figure 8-28. In this example, Privacy Act is a message classification, whereas the rest of the entries in the list are AD RMS templates.

Message classifications are created using the EMS and the New-MessageClassification cmdlet. It is worth noting that the message classification selection seen in Figure 8-28 is just the display name of the classification. You specify the classification s display name with the DisplayName parameter; this defines the label seen from the selection menu by the sender. The SenderDescription parameter defines the description that is shown to the sender in the composed message, as shown in Figure 8-29.

You can configure separately the text displayed to recipients of a classified message with the RecipientDescription parameter; the recipient description for the message composed in Figure 8-29 as seen in Outlook Web App is shown in Figure 8-30. If the recipient description is not configured, the text configured for the sender description is displayed.

ll too often organizations will attempt to place rigid or complex policies on their end users in the name of governance, compliance, security, privacy, or a

whole collection of laws and regulations. For example, I ve heard of organizations that prompt their employees to classify every single e-mail and that process involves understanding the definition of hundreds of classification tags and picking the right one. I ve also heard of organizations that give their employees complex instructions on when to IrM-protect documents or when it s appropriate to S/MIME encrypt versus sign an e-mail. While the intent is to keep the organization and employees out of trouble, this approach results in employee frustration and ultimately leads to the click the default and ignore mentality, which is contrary to the original goal and intent of the policy. Instead of pushing complex rules to employees, organizations need to consider ways to reduce confusion and streamline the process. an easy way to do this out of the box in Exchange 2010 is via message classifications and transport rules. Message classifications are informational policies that can be tagged (either manually or automatically) to e-mail messages that can display a user-friendly description in Outlook or OWa. These message classifications can then trigger transport rules in the background. Take a look at the following example. Contoso is a healthcare provider with patient information that needs to be kept confidential. Today they instruct their employees to include a disclaimer on all e-mails that contain patient data and they also require that these e-mails be encrypted. half the time, employees forget to do this or they only include the disclaimer but don t encrypt the mail. To simplify, Contoso creates a set of message classifications: patient Data, Financial Data, and public. When an employee marks and sends a message as patient Data, a transport rule is triggered that automatically adds the proper disclaimer to the message and protects the message using aD rMS such that the content cannot be viewable outside of Contoso. For Financial Data e-mail, a transport rule applies a different disclaimer and forces the message to be moderated before the message can leave Contoso. This ensures that no financial data is sent outside the company without approval. as this example shows, you have access to simple and straightforward ways to use message classifications to abstract complex policies and actions from employees while encouraging them to properly handle and classify sensitive information.