Skip to main content

Adding a Disclaimer to email messages in Office 365

In most emails, you could notice some disclaimer like below...
"The information of this e-mail is strictly confidential and...."
"This email and all contents are privileged..."

You can add those disclaimer in your office 365 environment too.
Here is steps for how-to,

To add a disclaimer to your company's outgoing messages, follow these steps:
- Sign in to the Office 365 portal (http://login.microsoftonline.com) as an administrator and open the Exchange Administration Center. ( See below sample screenshot)


- In the left navigation pane, click Mail Flow, and then click Rules.
- Click New, and then select "Apply disclaimers..."on the new rule page.
- In the Name of rule box, type a name for the new rule.
- Under *If, select the conditions that must met for a message to include the disclaimer.
- Under *Do the following, point to "Applend the disclaimer", and then Click Enter text, and then type the disclaimer text that you want.
- Specify any other settings that you want for the rule.
- Click Select one, and then specify a fallback action to take if the rule can't be applied.
- Under Choose a mode for this rule, click Enforce this rule.
- Click Save.

That's the how-to guide for adding a disclaimer in office 365 environment. I've attached sample screenshot for your reference. You can try to play for other option how those work.





May you all be happy.
(Be knowledgeable, pass it on then)

Comments

Popular posts from this blog

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason. Below error was come out when you try to edit VM setting. Below error was come out when you power on the VM. How to solve those error? Here is how I resolve the error! Login to the Host that errored VM exist by using Terminal or Direct Console. Enter below command and press enter. services.sh restart Wait until all VMware Services are restarted. After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up. This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist. You can check log file deeply if you willing to know precisely on this. May you all be happy. (Be knowledgeable, pass it on then)