It is important to add disclaimers to your internal and external mails, since this can help protect your company from liability. Consider the following scenario: an employee accidentally forwards a virus to a customer by email. The customer decides to sue your company for damages. If you add a disclaimer at the bottom of every external mail, saying that the recipient must check each email for viruses and that it cannot be held liable for any transmitted viruses, this will surely be of help to you in court (read more about email disclaimers). Another example: an employee sues the company for allowing a racist email to circulate the office. If your company has an email policy in place and adds an email disclaimer to every mail that states that employees are expressly required not to make defamatory statements, you have a good case of proving that the company did everything it could to prevent offensive emails.
A lot of people don’t bother to read an email before they send it out, as can be seen from the many spelling and grammar mistakes contained in emails. Apart from this, reading your email through the eyes of the recipient will help you send a more effective message and avoid misunderstandings and inappropriate comments.
Only use Reply to All if you really need your message to be seen by each person who received the original message.
When sending an email mailing, some people place all the email addresses in the To: field. There are two drawbacks to this practice: (1) the recipient knows that you have sent the same message to a large number of recipients, and (2) you are publicizing someone else’s email address without their permission. One way to get round this is to place all addresses in the Bcc: field. However, the recipient will only see the address from the To: field in their email, so if this was empty, the To: field will be blank and this might look like spamming. You could include the mailing list email address in the To: field, or even better, if you have Microsoft Outlook and Word you can do a mail merge and create one message for each recipient. A mail merge also allows you to use fields in the message so that you can for instance address each recipient personally. For more information on how to do a Word mail merge, consult the Help in Word.
In business emails, try not to use abbreviations such as BTW (by the way) and LOL (laugh out loud). The recipient might not be aware of the meanings of the abbreviations and in business emails these are generally not appropriate. The same goes for emoticons, such as the smiley :-). If you are not sure whether your recipient knows what it means, it is better not to use it.
Remember that when you use formatting in your emails, the sender might not be able to view formatting, or might see different fonts than you had intended. When using colors, use a color that is easy to read on the background.
Be aware that when you send an email in rich text or HTML format, the sender might only be able to receive plain text emails. If this is the case, the recipient will receive your message as a .txt attachment. Most email clients however, including Microsoft Outlook, are able to receive HTML and rich text messages.
Do not forward chain letters. We can safely say that all of them are hoaxes. Just delete the letters as soon as you receive them.
This will almost always annoy your recipient before he or she has even read your message. Besides, it usually does not work anyway since the recipient could have blocked that function, or his/her software might not support it, so what is the use of using it? If you want to know whether an email was received it is better to ask the recipient to let you know if it was received.
Biggest chances are that your message has already been delivered and read. A recall request would look very silly in that case wouldn’t it? It is better just to send an email to say that you have made a mistake. This will look much more honest than trying to recall a message.
Do not copy a message or attachment belonging to another user without permission of the originator. If you do not ask permission first, you might be infringing on copyright laws.