Re: Outbound Appending
From: Ben Winzenz [Exchange MVP] (ben_winzenz_at_NOSPAMdotmessageonedotcom)
Date: 02/24/05
- Next message: ayb: "new users can not logon to Exchange server anymore"
- Previous message: Geoff Pearce: "Re: Why am I sending NDR's again?"
- In reply to: Paul Cookson: "Re: Outbound Appending"
- Next in thread: Paul Cookson: "Re: Outbound Appending"
- Reply: Paul Cookson: "Re: Outbound Appending"
- Reply: Jonas, Sylvan R.: "Re: Outbound Appending"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 24 Feb 2005 14:35:48 -0600
No one is asking you to "shell out" for a border server. In fact, there is
nothing that says it has to be an Exchange server. I would guess that this
event sink would work just fine using the SMTP portion of IIS that can be
installed with regular Windows. Or, you can create another SMTP Virtual
Server on your current Exchange server to accomplish this (Have the Default
SMTP VS send outbound mail on port 26, and the 2nd SMTP VS listen on port
26) - this would require having multiple IP's assigned to the server, as
each SMTP VS requires a unique IP. Also, no one is telling you to implement
the "sample" event sink that Microsoft has provided. The KB article that
details how to implement the event sink quite clearly states it's
limitations. If you have implemented custom event sinks, then I again
reiterate that you should easily be able to write your own custom event sink
for outbound e-mail that appends a disclaimer. Exchange server has never
included this ability by default (even 5.5 required customization of
imcext.dll)
If you've been following this thread, then you should know there are several
alternatives out there. GFI MailEssentials provides a free full version
trial of their software, that also includes the ability to put a disclaimer
on outbound messages. Once the free trial expires, the disclaimer portion
still works.
I'm sorry if you don't like my tone. You jumped into the middle of a thread
stating how you think the event sink is a joke and then stated you are a
programmer. What exactly did you expect as a response? How did you expect
me to be more constructive based on the information in your post??? I'm
actually quite curious. I'd ask you to re-read your post and then tell me
what your reply would be if I were the one posting that comment.
-- Ben Winzenz Exchange MVP "Paul Cookson" <PaulCookson@discussions.microsoft.com> wrote in message news:CDE9641C-B9F6-40A7-A667-6DDF52B3E007@microsoft.com... > Hi Ben, Love the tone of your note. Pity you were not a bit more > constructive in your reply. For your information I have implemented > custom > spam and Virus protection for out severs using event sinks for incoming > email. My problem relates to asking a small business to shell out for a > 'BORDER EXCHANGE SERVER' as your (and my) friends at Microsoft call it and > the software to put on it just to add a disclaimer on an outbound email. > I > guess you never asked a MD to shell out for a real world job or perhaps > explained why the £600 email server can't attach a disclaimer. Don't > bother > replying unless you can explain to me how to add an event sink to an email > which is heading outward on a single exchange server (which most are) or > al > least can be a little more good humoured. > > "Ben Winzenz [Exchange MVP]" wrote: > >> If you are a programmer, then it should be quite easy to write and >> implement >> your own event sink. I'm personally sick of people complaining about >> code >> the the folks at Microsoft wrote as an example of how to use event sinks. >> The whole intent behind event sinks is to show people how they can work >> and >> enable them to write their own if the provided examples don't fit their >> needs. You'll find that most of the 3rd party software providers that >> put >> disclaimers on messages have in fact written event sinks to do this. >> Granted, they are much more complex than the sample provided, but it >> drives >> home that point. >> >> You can also implement this event sink on a Front-end server that is >> functioning as an outbound SMTP relay, and it should work just fine. It >> just won't work if you implement it on a mailbox server. >> >> -- >> Ben Winzenz >> Exchange MVP >> >> >> "Paul Cookson" <Paul Cookson@discussions.microsoft.com> wrote in message >> news:6A327735-AEF3-405C-8F93-8741EF6F3749@microsoft.com... >> > This event thing won't work with outlook or any other mapi client. >> > Messages >> > need to be sent to the server using SMTP. This has to be some sort of >> > sick >> > joke. I am a progammer. >> > >> > "Jonas, Sylvan R." wrote: >> > >> >> Thanks. I'll look at that. >> >> >> >> Sylvan >> >> "Ben Winzenz [Exchange MVP]" <ben_winzenz@NOSPAMdotmessageonedotcom> >> >> wrote >> >> in message news:e6xqtv6EFHA.4052@TK2MSFTNGP14.phx.gbl... >> >> > Yeah - I was going to mention that as well because it caught my eye >> >> > too. >> >> > >> >> > You are basically left with writing your own even sink, or trying >> >> > something else, such as GFI's Mailessentials to do it for you. >> >> > >> >> > The following link may help if you are interested in writing your >> >> > own >> >> > event sink, but if you aren't a programmer (I'm not!), it may be >> >> > overwhelming in terms of information. >> >> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsmtps/html/writingmngsinks.asp >> >> > >> >> > -- >> >> > Ben Winzenz >> >> > Exchange MVP >> >> > >> >> > >> >> > "Jonas, Sylvan R." <sjonas@brouse.com> wrote in message >> >> > news:OuIIfg6EFHA.3928@TK2MSFTNGP15.phx.gbl... >> >> >>I just noticed something in the original KB article you sent me. It >> >> >>says, >> >> >>"If you use a MAPI client such as Microsoft Outlook to send the >> >> >>e-mail, >> >> >>the recipient does not receive a modified message. This is because >> >> >>messages submitted 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." >> >> >> >> >> >> That poses a problem since we all use Outlook!!! We used to have a >> >> >> disclaimer before and considering that we are a law firm, it is >> >> >> VERY >> >> >> important to us that we continue to have it. >> >> >> >> >> >> Any work arounds to this? (Thanks for all your help so far!) >> >> >> >> >> >> Sylvan >> >> >> "Ben Winzenz [Exchange MVP]" >> >> >> <ben_winzenz@NOSPAMdotmessageonedotcom> >> >> >> wrote in message news:OYztGe6EFHA.2828@TK2MSFTNGP09.phx.gbl... >> >> >>> Yes - you are right. Run each line as a separate command. You >> >> >>> should >> >> >>> get the notification on the first one that the smtp event sink was >> >> >>> registered. I did not see a notification following the second >> >> >>> command >> >> >>> >> >> >>> Following registration, you may need to restart the SMTP service, >> >> >>> but >> >> >>> it >> >> >>> should work. >> >> >>> >> >> >>> -- >> >> >>> Ben Winzenz >> >> >>> Exchange MVP >> >> >>> >> >> >>> >> >> >>> "Jonas, Sylvan R." <sjonas@brouse.com> wrote in message >> >> >>> news:%23QghOR6EFHA.228@TK2MSFTNGP15.phx.gbl... >> >> >>>> That DEFINITELY did not work when I put them both together! It >> >> >>>> came >> >> >>>> back with a usage screen telling me the proper way to use the >> >> >>>> CSCRIPT >> >> >>>> command. >> >> >>>> >> >> >>>> Sylvan >> >> >>>> >> >> >>>> "Ben Winzenz [Exchange MVP]" >> >> >>>> <ben_winzenz@NOSPAMdotmessageonedotcom> >> >> >>>> wrote in message news:uBdpCN6EFHA.1932@TK2MSFTNGP14.phx.gbl... >> >> >>>>> It also looks like you may be missing part of the line. The >> >> >>>>> command >> >> >>>>> should be all together. If you put it all together, you should >> >> >>>>> then >> >> >>>>> see the message that it registered the event sink. Here's the >> >> >>>>> command >> >> >>>>> again from the KB article. >> >> >>>>> >> >> >>>>> 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" >> >> >>>>> >> >> >>>>> -- >> >> >>>>> Ben Winzenz >> >> >>>>> Exchange MVP >> >> >>>>> >> >> >>>>> >> >> >>>>> "Jonas, Sylvan R." <sjonas@brouse.com> wrote in message >> >> >>>>> news:uKJq9u5EFHA.2156@TK2MSFTNGP10.phx.gbl... >> >> >>>>>> Well, I tried the new code and didn't get any errors, but I >> >> >>>>>> didn't >> >> >>>>>> get a succesful message either. When I tried to test the >> >> >>>>>> outbound >> >> >>>>>> disclaimer feature, it didn't work. >> >> >>>>>> >> >> >>>>>> Sylvan >> >> >>>>>> "Ben Winzenz [Exchange MVP]" >> >> >>>>>> <ben_winzenz@NOSPAMdotmessageonedotcom> >> >> >>>>>> wrote in message news:eLlulY5EFHA.3504@TK2MSFTNGP12.phx.gbl... >> >> >>>>>>> Hmmm - It looks like the code there might be off. Try the >> >> >>>>>>> code >> >> >>>>>>> from >> >> >>>>>>> the following KB article. There is a section that deals with >> >> >>>>>>> code >> >> >>>>>>> for smtpreg.vbs. >> >> >>>>>>> http://support.microsoft.com/default.aspx?scid=kb;en-us;324021 >> >> >>>>>>> >> >> >>>>>>> -- >> >> >>>>>>> Ben Winzenz >> >> >>>>>>> Exchange MVP >> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>> "Ben Winzenz [Exchange MVP]" >> >> >>>>>>> <ben_winzenz@NOSPAMdotmessageonedotcom> >> >> >>>>>>> wrote in message news:uUzbjR5EFHA.560@TK2MSFTNGP15.phx.gbl... >> >> >>>>>>>> Er, line 145 is the following, at least on the code that I >> >> >>>>>>>> pulled. >> >> >>>>>>>> I'm not a programmer, so I don't know what is missing. >> >> >>>>>>>> Perhaps >> >> >>>>>>>> someone else will know. >> >> >>>>>>>> >> >> >>>>>>>> If Err.Number 0 Then >> >> >>>>>>>> >> >> >>>>>>>> -- >> >> >>>>>>>> Ben Winzenz >> >> >>>>>>>> Exchange MVP >> >> >>>>>>>> >> >> >>>>>>>> >> >> >>>>>>>> "Jonas, Sylvan R." <sjonas@brouse.com> wrote in message >> >> >>>>>>>> news:O7rAiJ5EFHA.2456@TK2MSFTNGP10.phx.gbl... >> >> >>>>>>>>> Well, I don't know what I'm doing wrong, but I copied to >> >> >>>>>>>>> code >> >> >>>>>>>>> to a >> >> >>>>>>>>> NOTEPAD (I even used the Copy Code link at the top) and >> >> >>>>>>>>> saved >> >> >>>>>>>>> it >> >> >>>>>>>>> as SMTPREG.VBS. Then from a DOS prompt on the Exchange >> >> >>>>>>>>> server, >> >> >>>>>>>>> I >> >> >>>>>>>>> ran the following command: >> >> >>>>>>>>> >> >> >>>>>>>>> cscript smtpreg.vbs /add 1 onarrival SMTPScriptingHost >> >> >>>>>>>>> CDO.SS_SMTPOnArivalSink "mail from=*@mydomain.com" >> >> >>>>>>>>> >> >> >>>>>>>>> (I did put in my actual domain name). When I hit enter, I >> >> >>>>>>>>> got >> >> >>>>>>>>> the >> >> >>>>>>>>> following error: >> >> >>>>>>>>> >> >> >>>>>>>>> C:\Program Files\Exchange SDK\Tools\smtpreg.vbs(145, 26) >> >> >>>>>>>>> Microsoft >> >> >>>>>>>>> VBScript compilation error: Expected 'Then' >> >> >>>>>>>>> >> >> >>>>>>>>> Any ideas why that is? I checked line 145 and there wasn't >> >> >>>>>>>>> even >> >> >>>>>>>>> an IF statement. I do know a bit about programming and I >> >> >>>>>>>>> understand that every IF needs a THEN as well as and END IF. >> >> >>>>>>>>> I >> >> >>>>>>>>> checked the entire code to make sure nothing was missing in >> >> >>>>>>>>> regards to that. >> >> >>>>>>>>> >> >> >>>>>>>>> Sylvan >> >> >>>>>>>>> >> >> >>>>>>>>> "Ben Winzenz [Exchange MVP]" >> >> >>>>>>>>> <ben_winzenz@NOSPAMdotmessageonedotcom> wrote in message >> >> >>>>>>>>> news:e6Rvb84EFHA.2232@TK2MSFTNGP14.phx.gbl... >> >> >>>>>>>>>> Looks like it is available on the MSDN site. Just copy the >> >> >>>>>>>>>> code >> >> >>>>>>>>>> into a text editor and save it as smtpreg.vbs. >> >> >>>>>>>>>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/smtpevt/html/6b7a017e-981e-45a1-8690-17ff26682bc7.asp >> >> >>>>>>>>>> >> >> >>>>>>>>>> -- >> >> >>>>>>>>>> Ben Winzenz >> >> >>>>>>>>>> Exchange MVP >> >> >>>>>>>>>> >> >> >>>>>>>>>> >> >> >>>>>>>>>> "Jonas, Sylvan R." <sjonas@brouse.com> wrote in message >> >> >>>>>>>>>> news:ODlNJj4EFHA.936@TK2MSFTNGP12.phx.gbl... >> >> >>>>>>>>>>> The only problem I have now is that I can't find the >> >> >>>>>>>>>>> smtpreg.vbs >> >> >>>>>>>>>>> file it refers to. I've downloaded and installed the >> >> >>>>>>>>>>> Exchange >> >> >>>>>>>>>>> SDK Tools, but it's nowhere around! Any ideas how I can >> >> >>>>>>>>>>> get >> >> >>>>>>>>>>> a >> >> >>>>>>>>>>> hold of this from Microsoft? >> >> >>>>>>>>>>> >> >> >>>>>>>>>>> Sylvan >> >> >>>>>>>>>>> "Ben Winzenz [Exchange MVP]" >> >> >>>>>>>>>>> <ben_winzenz@NOSPAMdotmessageonedotcom> wrote in message >> >> >>>>>>>>>>> news:OFZ2vl3EFHA.3536@TK2MSFTNGP15.phx.gbl... >> >> >>>>>>>>>>>> Like I said, you can write your own event sink to do this >> >> >>>>>>>>>>>> if >> >> >>>>>>>>>>>> you want. GFI's solution is, as I mentioend, free. You >> >> >>>>>>>>>>>> get >> >> >>>>>>>>>>>> the >> >> >>>>>>>>>>>> trial, then when it expires, the disclaimer portion will >> >> >>>>>>>>>>>> still >> >> >>>>>>>>>>>> work just fine. >> >> >>>>>>>>>>>> >> >> >>>>>>>>>>>> If you want to look into your own event sink without 3rd >> >> >>>>>>>>>>>> party >> >> >>>>>>>>>>>> software, then you can refer to the following KB article. >> >> >>>>>>>>>>>> http://support.microsoft.com/default.aspx?scid=kb;en-us;317680 >> >> >>>>>>>>>>>> >> >> >>>>>>>>>>>> -- >> >> >>>>>>>>>>>> Ben Winzenz >> >> >>>>>>>>>>>> Exchange MVP >> >> >>>>>>>>>>>> >> >> >>>>>>>>>>>> >> >> >>>>>>>>>>>> "Jonas, Sylvan R." <sjonas@brouse.com> wrote in message >> >> >>>>>>>>>>>> news:uV$VXe3EFHA.2232@TK2MSFTNGP14.phx.gbl... >> >> >>>>>>>>>>>>>I find it very hard to believe that I could do this in >> >> >>>>>>>>>>>>>Exchange >> >> >>>>>>>>>>>>>5.5 with a registry hack, but now I have to buy a >> >> >>>>>>>>>>>>>software >> >> >>>>>>>>>>>>>to >> >> >>>>>>>>>>>>>do it for me. Only because I don't know what event sinks >> >> >>>>>>>>>>>>>are. >> >> >>>>>>>>>>>>> >> >> >>>>>>>>>>>>> Sylvan >> >> >>>>>>>>>>>>> "Ben Winzenz [Exchange MVP]" >> >> >>>>>>>>>>>>> <ben_winzenz@NOSPAMdotmessageonedotcom> wrote in message >> >> >>>>>>>>>>>>> news:OXzYYW3EFHA.4072@TK2MSFTNGP10.phx.gbl... >> >> >>>>>>>>>>>>>> You have to get something else to do this for you. >> >> >>>>>>>>>>>>>> GFI's >> >> >>>>>>>>>>>>>> MailEssentials will append a disclaimer on messages. >> >> >>>>>>>>>>>>>> The >> >> >>>>>>>>>>>>>> disclaimer portion continues to work even after the >> >> >>>>>>>>>>>>>> rest >> >> >>>>>>>>>>>>>> of >> >> >>>>>>>>>>>>>> the product is expired. They use an Event sink to do >> >> >>>>>>>>>>>>>> this, >> >> >>>>>>>>>>>>>> IIRC, so if you don't want to use their software, you >> >> >>>>>>>>>>>>>> can >> >> >>>>>>>>>>>>>> write your own event sink to append the disclaimer. >> >> >>>>>>>>>>>>>> >> >> >>>>>>>>>>>>>> -- >> >> >>>>>>>>>>>>>> Ben Winzenz >> >> >>>>>>>>>>>>>> Exchange MVP >> >> >>>>>>>>>>>>>> >> >> >>>>>>>>>>>>>> >> >> >>>>>>>>>>>>>> "Jonas, Sylvan R." <sjonas@brouse.com> wrote in message >> >> >>>>>>>>>>>>>> news:uuC0VG3EFHA.4004@tk2msftngp13.phx.gbl... >> >> >>>>>>>>>>>>>>> In Exchange 5.5, we used to have a disclaimer message >> >> >>>>>>>>>>>>>>> that >> >> >>>>>>>>>>>>>>> was automatically attached to all outbound messages. >> >> >>>>>>>>>>>>>>> That >> >> >>>>>>>>>>>>>>> was configured by modifying the registry. Now that we >> >> >>>>>>>>>>>>>>> have >> >> >>>>>>>>>>>>>>> 2003, how do we add that disclaimer again? Is it >> >> >>>>>>>>>>>>>>> another >> >> >>>>>>>>>>>>>>> registry hack or has Microsoft figured out a way to >> >> >>>>>>>>>>>>>>> make >> >> >>>>>>>>>>>>>>> that easier? >> >> >>>>>>>>>>>>>>> >> >> >>>>>>>>>>>>>>> Sylvan >> >> >>>>>>>>>>>>>>> >> >> >>>>>>>>>>>>>> >> >> >>>>>>>>>>>>>> >> >> >>>>>>>>>>>>> >> >> >>>>>>>>>>>>> >> >> >>>>>>>>>>>> >> >> >>>>>>>>>>>> >> >> >>>>>>>>>>> >> >> >>>>>>>>>>> >> >> >>>>>>>>>> >> >> >>>>>>>>>> >> >> >>>>>>>>> >> >> >>>>>>>>> >> >> >>>>>>>> >> >> >>>>>>>> >> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>> >> >> >>>>>> >> >> >>>>> >> >> >>>>> >> >> >>>> >> >> >>>> >> >> >>> >> >> >>> >> >> >> >> >> >> >> >> > >> >> > >> >> >> >> >> >> >> >> >>
- Next message: ayb: "new users can not logon to Exchange server anymore"
- Previous message: Geoff Pearce: "Re: Why am I sending NDR's again?"
- In reply to: Paul Cookson: "Re: Outbound Appending"
- Next in thread: Paul Cookson: "Re: Outbound Appending"
- Reply: Paul Cookson: "Re: Outbound Appending"
- Reply: Jonas, Sylvan R.: "Re: Outbound Appending"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading
