Outlook 2007 showing presence awareness of the message sender in Software

Encoder QR-Code in Software Outlook 2007 showing presence awareness of the message sender

11:

Microsoft continues to work to improve security and message hygiene in Exchange and Outlook, both separately and together

In an ongoing effort to reduce spam or more accurately reduce legitimate e-mail being tagged as spam Microsoft has added a new feature called an e-mail postmark By default, outbound messages in Outlook 2007, when used with Exchange 2007, are given a postmark based on the characteristics of that message The postmark is created as a pair of custom SMTP X-headers followed by a sample puzzle algorithm output:

>x-cr-puzzleid: {24B75461-3B63-4C9E-91F0-D9A3733C075F} >x-cr-hashedpuzzle: ANCj ASoD B9Wr D64F GeSW G7HL G8Wb HO5P H7VP IsHi NCIV

This unique presolved puzzle or fingerprint uses a little bit of resources to compile and slows outbound e-mail slightly If the recipient uses Exchange 2007 or another mail system capable of validating these client e-mail postmarks, the chances of a message being classified as junk mail can be reduced The Exchange 2007 Content Filter will decrease the Spam Confidence Level (SCL) value assessed for the message Spammers do not tend to spoof postmarking because of the resource cost when sending e-mail in the quantities that spammers need to send Validation of Outlook e-mail postmarks can be toggled off at the Exchange 2007 server using the Exchange Management Shell E-mail postmarks are not applied when the recipients are all within the organization, the message has been encrypted, or it has been restricted through digital rights policy The postmark feature can be toggled off in Tools | Options | Preferences | Junk E-mail at the bottom of the Options tab

Outlook 2007 and Exchange 2007 offer another security and management mechanism in the form of message classification Classifying e-mail content is a way of describing a message for the purposes of meeting regulatory compliance or confidentiality policies Unfortunately, message classification is not operational by default and requires some administration to implement Message classification provides only an informational label to the messages; however, Exchange 2007 Transport rules can be created based on an assigned classification to assist with internal ethical walls for message flow When Exchange 2007 is installed, it creates a script repository with some very useful Exchange Management Shell scripts One script contains basic message classifications for Outlook and Exchange and is by default located at:

To export those classifications to an xml file, we execute the PowerShell script as follows:

Part IV:

The path to the folder level must exist; the script will not create the path if it does not OutlookClassxml creates several default classifications and their descriptions:

< xml version="10" > <Classifications> <Classification> <Name>A/C Privileged</Name> <Description>This message is either a request for legal advice from an attorney or a response by an attorney to a request for legal advice It should be treated confidentially, should only be sent to people with a need to know, and should only be forwarded by an attorney</Description> <Guid>d74dbde8-4cb0-4043-ae4b-2a1b5686c9dc</Guid> <AutoClassifyReplies/> </Classification> <Classification> <Name>Attachment Removed</Name> <Description>A system-generated classification to inform users that an attachment was removed from this message</Description> <Guid>a4bb0cb2-4395-4d18-9799-1f904b20fe92</Guid> </Classification> <Classification> <Name>Company Confidential</Name> <Description>This message contains proprietary information and should be handled confidentially</Description> <Guid>19e795ab-f38c-4d55-a009-0a3ad32ffc1f</Guid> <AutoClassifyReplies/> </Classification> <Classification> <Name>Company Internal</Name> <Description>This message contains sensitive information that should only be delivered to internal recipients</Description> <Guid>f93fcaf3-00b6-4bfe-a84b-40e78f498560</Guid> <AutoClassifyReplies/> </Classification> <Classification> <Name>Partner Mail</Name> <Description></Description> <Guid>030e9e2f-134b-4020-861c-5bfc616f113d</Guid> </Classification> </Classifications>

The xml file reveals the default categories of A/C Privileged, Attachment Removed, Company Confidential, Company Internal, and Partner Mail Using the EMS, administrators can add their own classifications as well The cmdlet New-MessageClassification can create the label and a description for the new classification Exchange will automatically generate a new GUID for the classification An example of this cmdlet in use might be as follows:

>New-MessageClassification Name "Complete Exchange 2007" DisplayName "Exchange2007" SenderDescription "McGraw Hill Exchange Book Project"

Figure 11-16 shows the new classification this command added to the default offerings The xml file must be stored in a location accessible to Outlook 2007 at startup A network share location would prevent it from being used offline The xml file can be pushed out to Outlook 2007 client workstations in a login script, through Group Policy, SMS, or another

11: