What Are the Pros and Cons of Using Email Disclaimers?

Skip to end of metadata
Go to start of metadata

What Are the Pros and Cons of Using Email Disclaimers?

Topics:

Deciding to Implement Email Disclaimers

Use the following information to decide whether you want every sent email from every employee to carry a company disclaimer message:

To Implement Email Disclaimers

If you do decide in favor of email disclaimers, be aware that there is no way to fully implement them at the server level.

  1. The only proper way to do disclaimers is to have a policy requiring users to insert them in their mail clients.
  2. The next best approach is to write a conversion channel to add the disclaimer.
    The conversion channel can be used to perform arbitrary processing on each message on a per-body-part basis. In this case, you want the processing to be that of appending a disclaimer. Modify the MTA configuration files so that all your mail passes through this conversion channel. At a minimum, construct one conversion to account for text/plain message body and one to account for HTML. Add more conversions if the actual messages being sent have some other sort of MIME structure unique to your deployment.

For more information, see Using Predefined Channels#The Conversion Channel.

Troubleshooting Email Disclaimers

If you configure the MTA as previously described, and run into problems where the disclaimer is not appearing, begin by looking at your conversions file, and get a master_debug conversion channel debug log file. The tcp_local_slave.log-* file, and the mappings file, provide information about getting the message to the conversion channel. The appending of the disclaimer would be done by the conversion channel, so you need to see what the conversion channel itself is doing.

Labels:
messagingserver messagingserver Delete
faq faq Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.