The other problem with MTA forced disclaimers is that it breaks PGP encryption.. So if you ever need to encrypt or checksum your emails, you will have to lose the disclaimer.
This would be better set as a company wide policy and have a "smaller" sig file attached by the users email client. (where it won't break RFC's or encryption.) rgds Franki >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Tony S. Sykes >All, > >I have sent this email to my MD to try to solve the problem; > >A few people have mentioned the size of our email disclaimer, and the >fact that after a few emails between BCP and customers we can have >several of our disclaimers against the email. We also put the disclaimer >at the end of the email. This poses a problem for somebody who receives >it by mistake. They have read the email before they read the disclaimer. >While we don't send out much information which could harm us in anyway >we could be placing ourselves in a tricky position. I would like to >suggest the solution of putting the disclaimer on an web page and >putting a link to it at the top of the email. This would also save a >little bandwidth in the email server. > >Who says this list does not help Windows? (God help us) > >Tony.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
