Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Microsoft Exchange Server 2007 : Hub Transport Server Policy Compliance Features (part 2) - Disclaimers

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
7/29/2014 9:16:12 PM

Disclaimers

Disclaimers are important to limit liability and comply with security and legal policies, as they make the position of the organization clear on each and every message that is sent by the organization. Disclaimers can take different legal aspects, such as:

  • Breach of confidentiality and accidental breach of confidentiality

  • Transmission of viruses

  • Entering into contracts

  • Negligent misstatement

  • Employer’s liability

They can also be used in interdepartmental email, provide helpful contact information, or simply ensure that the corporate address is on every email.

Note

A sample disclaimer covering breach of confidentiality and accidental breach of confidentiality:

“This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute, or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing, or taking any action in reliance on the contents of this information is strictly prohibited.”


In a welcome change from Exchange 2003, Exchange 2007 offers an easy and effective way to add disclaimers to messages traversing the messaging infrastructure. Historically, this was very difficult to do in the Exchange family.

The position of the disclaimer can be specified by the rule. Disclaimers can be either appended (the default and customary option) or prepended. Prepending the disclaimer is a way to ensure that it is read, but can interfere with the readability of the email.

The font of the disclaimer can be specified, although the font types, sizes, and colors are somewhat limited. Table 1 shows the different settings and values.

Table 1. Disclaimer Font Settings
SettingValues
Font typeArial, Courier New, or Verdana
Font sizeSmallest, Smaller, Normal, Larger, or Largest
Font colorBlack, Blue, Fuchsia, Gray, Green, Lime, Maroon, Navy, Olive, Purple, Red, Silver, Teal, White, or Yellow

An interesting option is the fallback action. Encrypted and other protected email cannot be modified, which interferes with the process of adding disclaimers. To deal with this, the disclaimer rule has three options to choose from when a disclaimer cannot be added directly:

  • Wrap (the default)— The original message is wrapped in a new message and the disclaimer is appended to the new message.

  • Ignore— The disclaimer is not added to the message and the message is delivered as normal.

  • Reject— The message is not delivered. A nondelivery report (NDR) message is sent to the sender notifying them why it was not delivered.

Another useful option is the ability to create a separator line between the disclaimer text and the message. This helps the readability. If specified, the agent is smart enough to put the line in the appropriate position depending on if the disclaimer is appended or prepended.

Exchange does not check if disclaimers have been added to earlier messages, so the transport rule could wind up adding multiple disclaimers if not configured properly or if messages are forwarded or replied to. This tends to be more of a problem with internal disclaimers, rather than external disclaimers.

Disclaimers are basically a form of the transport rule and are implemented using them.

As an example of implementing a disclaimer, suppose an organization wants to add a disclaimer to all email that is destined for external recipients. To do this, complete the following steps:

1.
From the Exchange Management Console, expand the Organization folder, and select the Hub Transport folder.

2.
In the actions pane, select New Transport Rule.

3.
Enter in a name for the rule, such as Corporate Disclaimer on All Outbound Email.

4.
Click Next.

5.
Select the condition, in this case Sent to Users Inside or Outside the Corporation.

6.
Specify outside the corporation by clicking the blue, hypertext “Inside” text.

7.
Select Outside from the Scope drop-down, and click OK.

8.
The word Outside will be displayed in the rule description.

9.
Click Next.

10.
Select the action to take by checking the appropriate box, in this case Append Disclaimer Text Using Font, Color, and Fallback to Action if Unable to Apply.

11.
In the rule description pane, click the blue, hypertext “text” to enter the disclaimer text, and click OK.

12.
Leave the position as “prepend,” and the fallback action as “wrap.”

13.
Click Next.

14.
Leave the exceptions blank, and click Next.

15.
Click New to create the disclaimer transport rule.

16.
Click Finish to exit the wizard.

Now, the disclaimer text will be appended to all outgoing messages.

Other -----------------
- Microsoft Exchange Server 2007 : Implementing Client Access and Hub Transport Servers - Understanding the Hub Transport Server
- Sharepoint 2013 : Office 2013 and an Overview of Integration (part 5) - Live Co-Authoring,Document Information Panel
- Sharepoint 2013 : Office 2013 and an Overview of Integration (part 4) - SkyDrive and SkyDrive Pro
- Sharepoint 2013 : Office 2013 and an Overview of Integration (part 3) - SkyDrive and Office 365
- Sharepoint 2013 : Office 2013 and an Overview of Integration (part 2) - Opening and Saving to SharePoint
- Sharepoint 2013 : Office 2013 and an Overview of Integration (part 1) - The Backstage Area
- Windows Server 2012 : Simplifying the Datacenter (part 4) - Managing Windows 2012 with Performance and Reliability Monitoring Tools, Leveraging the Best Practice Analyzer
- Windows Server 2012 : Simplifying the Datacenter (part 3) - Improvements in Group Policy Management, IP Address Management
- Windows Server 2012 : Simplifying the Datacenter (part 2) - Active Directory Administrative Center
- Windows Server 2012 : Simplifying the Datacenter (part 1) - New Server Manager Tool
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server