• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 616
  • Last Modified:

Exchange 2003 VBS Disclaimer Does Not Work

First of all, the Exchange SDK does not include the smtpreg.vbs, but I was able to find it on the msdn site.  So followed the instructions on http://support.microsoft.com/kb/317680 otherwise and it succesfully ran.
So I sent a few test emails to my gmail account and nothing. Tried internally and nothing which is fine (only really need it on external communications). It only works if I send a message by telnetting to my mail server and running it that way...
Anyone?
D:\>cscript smtpreg.vbs /add 1 onarrival SMTPScriptingHost CDO.SS_
MTPOnArrivalSink "mail from=*@masked.suffix"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

Binding Display Name Specified: SMTPScriptingHost
Assigning priority (24575 in 32767)
** SUCCESS **
Registered Binding:
 Event Name  :SMTP Transport OnSubmission
 Display Name:SMTPScriptingHost
 Binding GUID:{02863FF8-5903-473E-BB5F-3EE81AF97933}
 ProgID      :CDO.SS_SMTPOnArrivalSink
   Rule      :mail from=*@masked.suffix   Priority  :24575 (0 - 32767, default: 24575)
   ComCatID  :{FF3CAA23-00B9-11d2-9DFB-00C04FA322BA}

D:\>cscript smtpreg.vbs /setprop 1 onarrival SMTPScriptingHost Sink ScriptName "D:\EventSinkScript.vbs"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

Binding Display Name Specified: SMTPScriptingHost
set property ScriptName to D:\EventSinkScript.vbs

Open in new window

0
pacman_d
Asked:
pacman_d
1 Solution
 
Tony JLead Technical ArchitectCommented:
From the KB article:

Note If you use a MAPI client such as Microsoft Outlook to send the e-mail and if the Exchange mailbox resides on the same server as the event sink binding, the recipient may not receive the modified message. This is because messages that are submitted by using MAPI are not in SMTP format when the e-mail triggers the SMTP transport event. Therefore, changes that are made by the event's code are not persisted.

Which most likely explains why it doesn't work internally - as a quick question, do you use the same recipient in both telnet and from Outlook? And is the recipient an external address?

Does it work from OWA?

Might be worthwhile restarting Exchange services.
0
 
pacman_dAuthor Commented:
I restarted the SMTP Virtual Server, it did not send the disclaimer from OWA either. Only telnet and a mass email application that relays off it (i actually did NOT want the disclaimer on that!). That was weird because I registered the sink with a certain domain and this app sends from another domain we host and it attached the disclaimer.
So it looks like the most important sender (the MAPI client) it doesn't work for... I had to uninstall GFI (free disclaimer) because I was getting reports after I upgraded it that random external recipients were getting blank email bodies/subjects.
I hope I don't have to wait until my next's year's budget to fix with Exchange 2010's transport rules. uggh.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now