Link to home
Start Free TrialLog in
Avatar of WestonGroup
WestonGroup

asked on

Corporate Wide Email disclosure

Running windows 2000 domain
Exchange 2000
Outlook 2000 and 2003


Is there a way in exchange to set up a corporate wide email disclosure?  So that all emails have this

This email is confidential and intended for the recipients listed in this email and may contain information that is privileged or exempt from disclosure under applicable company rules and regulations. Therefore, dissemination or distribution of this email is strictly prohibited.


I want it so no matter when you open an email its already there.

Thanks

ASKER CERTIFIED SOLUTION
Avatar of LeeDerbyshire
LeeDerbyshire
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jss1199
jss1199

Hi WestonGroup,

As LeeDerbyshire says you cannot add a disclaimer to outgoing messages with Exchange only.  For email sent FROM your organization, you can use an SMTP event sink.  This process will add a disclaimer message to every outgoing message that is sent from your Exchange server.  Use the MS KB article below as an example event sink written in VB.  Keep in mind that this will not place the disclaimer on internal emails.

http://support.microsoft.com/default.aspx?scid=kb;en-us;317327
http://support.microsoft.com/?kbid=317680


If you install GFI Mail Essentials trial version and do not buy it, the disclaimer feature is still enabled.  GFI has decided to allow people who try GFI MailEssentials to continue using the Disclaimer module for free...

Good luck,
jss
Avatar of WestonGroup

ASKER

how do I create the DLL?

Is visual basic a standard install on XP?
Use http://support.microsoft.com/?kbid=317680 in my post from above.  You will not need the dll
Where do I add the disclaimer text?
Mentioned in the Kb Article:-

browse to the ...\Exchange SDK\SDK\Support\CDO\Scripts folder and type the following (make sure that the path to EventSinkScript.vbs is correct):


Thanks,

Kunal
no that shows where to register the event?

I mean where do I get to add my own text

This email is confidential and intended for the recipients listed in this email and may contain information that is privileged or exempt from disclosure under applicable company rules and regulations. Therefore, dissemination or distribution of this email is strictly prohibited.


that has to be somewere in the vbs script I just created...Correct?
On the line TextDisclaimer = vbCrLf & "DISCLAIMER:" & vbCrLf & "Sample Disclaimer added in a VBScript."
replace Sample Disclaimer added in a VBScript. with your text

On the line HTMLDisclaimer = "<p></p><p>DISCLAIMER:<br>Sample Disclaimer added in a VBScript."
Replace Sample Disclaimer added in a VBScript. with your text
I can't find that folder or that specific vbs file on our exchange server.  Its coming up as it doesn't exist

I don't have the exchange software development kit which is required I guess to run this vbs script.

Is that downloadable? Free? Cost money?

Any other suggestions?
Even after downloading and installing that those folders don't exists?  I don't understand
Do a file search on all your drives and locate smtpreg.vbs
I did the search on all the drives for smtpreg.vbs and the search returned zero results??
You can copy/paste the source from here:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/smtpevt/html/6b7a017e-981e-45a1-8690-17ff26682bc7.asp

If you are new to this kind of thing (Event Sinks), I would suggest just using the free GFI Mailessentials for your disclaimer.  Of course, if you enjoy the challenge, that's a different matter :@) .
I like the challenge

Plus we already have anti spam anti phishing software i'm afraid installing the gfi mailessentials will cause a conflict

Once I copy and paste that code? and save the file as smtpreg.vbs  where do I place it?  How to I register it?

I think you can put it anywhere, actually.  You don't register the .vbs script, you use it to register DLLs using that command line from the Q317327 article:

cscript smtpreg.vbs /add 1 OnArrival SMTPDisclaimer SMTPEventSink.Disclaimer "mail from=*@your-domain-here.com"

Q317327 shows you how to create the DLLs using Visual Basic.  smtpreg.vbs registers them so that Exchange can activate them when certain Events happen.
WestonGroup,

I would place the smtpreg.vbs and your disclaimer vbs file in a new directory off root - something like c:\smtpsink.  This will keep both files together in case you bring another Exchange server in the org you can just copy that one folder instead of searching for the files again...

Ok I tried it...and it wouldn't register

When I type in the line that is suppose to register the event  it just gives me a list of commands?  as if I were typing in ipconfig/?

ANy ideads
I can only suggest that you double-double check what you typed in.  It sounds like cscript didn't like one of the parameters.
paste the command that you are attempting to run here
ok this is the error i'm getting now

Binding Display  name:SMTPScriptingHost
Failed to find binding with display name:SMTPScriptingHost
cscript smtpreg.vbs /add 1 onarrival SMTPScriptingHost CDO.SS_SMTPOnArrivalSink "mail from=*@your-domain-here.com"

cscript smtpreg.vbs /setprop 1 onarrival SMTPScriptingHost Sink ScriptName "C:\EventSinkScript.vbs"
Did you see the ** SUCCESS ** message after you did the /add ?
No I received the error above

Binding Display  name:SMTPScriptingHost
Failed to find binding with display name:SMTPScriptingHost
This isn't my speciality, so I can't give you an exact cause.  I can help you find out, though.  You will need to add some debugging lines to the script at various places.  When you /add a sink, the script calls Sub RegisterSink.  The first thing that does is to call GetBindings, so I would add a line like this

  WScript.Echo "Enter GetBindings"

immediately after the line

  Function GetBindings(iInstance, szEventName)

Note that it 'GetBindings' in the plural - there is a similarly named GetBinding which does not interest us yet.

Also add a line

  WScript.Echo "Exit GetBindings"

at the end of the function, just before the line

  End Function

Make sure that you can see both of these lines displayed on the console next time you try the /add .  If so, we'll move further on in the code.
ok I enter those lines and re ran the command prompt code

I typed this

cscript smtpreg.vbs /add 1 onarrival SMTPScriptingHost CDO.SS_SMTPOnArrivalSink "mail from=*@your-domain-here.com"


This was the result

Binding Display Name Specified : SMTPScriptingHost
Enter GetBindings
Exit GetBingdings
Assigned prority (24575 in 32767)
**success**
Registered Bindings
Event Name:SMTP Transport on submission
Display name: SMTPScriptingHost
(then there were a bund of binding characters)

Then i typed this

cscript smtpreg.vbs /setprop 1 onarrival SMTPScriptingHost Sink ScriptName "C:\EventSinkScript.vbs"

this was the result

Binding Display name specified : SMTPScriptingHost
set property scriptname to : c:\EventSinkScript.vbs


and that was it?

It looks like it works okay now.  That would be nothing to do with my extra lines, by the way.  Probably some temporary condition earlier.
I tested it though and the disclaimer is not showing up at the bottom of the emails though?
Did you send the email to an external email account.  This Event Sink does not work for internal emails.
Weston - I meant to ask you this yesterday afternoon but got tied up at work.  I want to ensure you are using the SMTP Event Sink on a front end or SMTP Gateway.  Are you a single Exchange server?  If you are using MAPI (Outlook) to send messages and are not utilizing a SMTP gateway/FE box, an event sink will not work for you.  Should have clarified this up front and hope this is not the case.

If you are not using a SMTP gateway, you are resigned to using a 3rd party product such as Exclaimer http://www.exclaimer.com/:(

http://support.microsoft.com/default.aspx?scid=kb;en-us;273233
We are using a single exchange server.  I'm not sure what you mean by MAPI Outlook

Outlook is our mail program  outlook 2000/2003

Is that what your referring too?  How else could we send mail?
Outlook Express.  Basically, the sinks do not work for MAPI-submitted (i.e. Outlook) messages.

From the bottom of the article:

http://support.microsoft.com/kb/317327/en-us

Note If you use a MAPI client, such as Microsoft Outlook, to send the e-mail message, the recipient does not receive a modified e-mail message. This is because the e-mail message that is submitted by using MAPI is not in an SMTP format when the e-mail message triggers the SMTP transport event. Therefore, changes that are made by the code of the event are not persisted.
Well that stinks
Indeed.  For most people, this is no use at all, so I avoid recommending it.  That is why I asked if you 'liked the challenge' - in most situations it is only really of interest as an academic excercise.  Sorry.
hahah oh well.

Maybe i'll have everyone switch over to outlook express
And a lot of installs these days use a SMTP gateway in the DMZ to send mail.  If you HAD to use this event sink and cannot purchase a product such as Exclaimer, you could setup a windows box with SMTP on the perimiter, register the heat sink, and have your exchange send outbound messages to the perimiter SMTP box to add the disclaimer and then send the message  on to the Internet.
Any windows box?  Xp? 2000?

whould that box go behind our router or in front?

How would I set the smtp up on it and point exchange to that box?
I have to go way back to my very first reply above.  www.gfi.com for a free solution , or www.exclaimer.com or similar for a paid solution .
Will that gfi solution interfear with out current anit spam phishing spyware program?
It should not, especially if you disable all the other features.  It's impossible to guarantee that any two applications will not occasionally fall out, though.
GFI is a fairly solid product and is designed for use with Exchange and several antivirus vendors...  I have implemented several of their products and have never come across compatibility issues.  With that said, re-read LeeDerbyshire's last statement...

Good Luck,
Jss