Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

disclaimers

Status
Not open for further replies.

ianedwards

IS-IT--Management
Oct 1, 2002
90
Hi

according to the web there is no easy way to set up a standard disclaimer on exchange server and that the best way is third party software. ie this email is intended for the recipient etc ect.

True or false? and if true has anyone any recommendations as to software?

thanks

Ian
 
True

A couple of 3rd party products that have been previously recommended in the Exchange forums here in no particular order: GFI Mail Essentials and Marshal Software's MailMarshal
 
The newer versions of GFI are time bombed unfortunately. Exclaimer.com have one that seems to be pretty popular at tek-tips.

There is an MS event sink that you can use, I dont have a link to hand at the moment unfortunately, its not particularty popular with the TT regulars though
 
>its not particularty popular

Because it isn't particularly good.
 
The MS sink doesn't work with MS Outlook. Go figure.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
Oh it will, you just need a second SMTP gateway.

The issue is that MAPI clients (of which Outlook is one)effectively wrap their messages. The first gateway unwraps the message into a temporary SMTP message, the sink fires and modifies the temporary message, and then the gateway passes along the original contents of the MAPI message as SMTP, thus discarding your changes in the temporary version.

If you set up a second gateway and put the sink on that instead, and ensure that all outbound MAPi traffic goes from the first gateway to the second gateway before heading off to the Internet then the sink will work.

But setting all of that up is a pain.
 
Or you could just upgrade to Exchange 2007 ;-)

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
Exchange best practices would be to have a second Exchange server in the DMZ doing antivirus/antispam/OWA/OMA and generally handling external mail delivery and receipt. As long as your internal Exchange servers are configured to route traffic via that server, then the event sink works fine. It's when you have a single server doing everything that you'll run into the problem. Unfortunately most smaller companies don't want to spring for an Exchange Enterprise license for the front-end functionality.

I have used Exclaimer in the past and it works well enough. However, all it really does is the exclaimer, and it seems odd to me to purchase a piece of software that does just one simple thing like that. There are many other mail utilities that provide the disclaimer functionality along with others like logging, spam filtering, etc.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top