One of the biggest and most glaring omissions from Microsoft Exchange 2003 is the facility to add an enterprise wide email signature. This popular choice which as recently become a legal requirement in 2007 has caused tremendous headache for those operating with Exchange. Of course, traditionally not everyone liked the use of E-mail disclaimers, and although it has been proven in some cases that the content be legally worthless they have now become a necessity for most. In the UK at least, law dictates they must be present – hence this page looks at means to deploy these disclaimers. Alas, a number of options exist, each of which has its merits and drawbacks, as shown below: Use your Anti-virus software Perhaps the simplest (if not the most elegant method) would be to use the feature provided by many anti-virus solutions at append a message to all outgoing mail. While this would normally be some template text along the lines of “This message was checked by such a program version x.x”, many enterprises opt to change this to include the legal speil necessary for such a disclaimer. Advantages of this approach are that everyone has company-wide anti-virus (they do, don’t they?) and it’s a no-cost addition. Add to this it can be centrally managed and it seems like a lossless situation. The only conceivable drawback is that some AV solutions do not offer the feature and thus alternate methods must be found. Transport Event Scripts (Using VB) MS KB Artice Q317680 discusses and demonstrates the use of a VB event script that will append your message to each outgoing email. While a relatively simple process to follow, there are a good number of pros and cons, some of which will be noted below. The most significant being it’s a free/no-cost solution (+), adds little overhead to the server (+) and can be updated as frequently as you like (+). Conversely, and the killer for most people is that it does not work with MAPI clients (meaning the 99.9999% of people on using Exchange will also be using Outlook or another MAPI client). Client Side signature appendage OK, if server-side is proving costly or problematic, why not apply it at the client side? Well, if you have hundreds or even thousands of users it becomes an administrative nightmare. Users cannot be entrusted to apply the signature themselves, so some method of centrally pushing the signature and enforcing it client-side is needed. That’s where a quick Windows 2003 logon-script can come in handy. In just a couple of lines of code you can push your signature out to the users machine and set the client to append the signature. How? The first thing you need to do is copy the signature files over to the client side application data folder (nothing more than xcopy /d \\servername\path\to\sig.txt %APPDATA%\Microsoft\Signatures\) making sure you copy over...Read More »
On my blog…
I'm a gadget loving code-junkie who loves to program, create websites and try out new stuff. Married, with two young daughters I am also a keen marathon runner and fitness enthusiast.
- Cloud Technologies (Azure & AWS)
- Mobile application development
- WordPress / Orchard CMS / Alterian ACM
- C#, Asp.net MVC & WebForms, Python
- IIS & Windows Server