Re: Outbound Appending
From: Paul Cookson (PaulCookson_at_discussions.microsoft.com)
Date: 02/25/05
- Next message: manoa: "CDO call to SMTP"
- Previous message: Gregg Hill: "Max size of distribution list in Exchange 2000 or 2003?"
- In reply to: Ben Winzenz [Exchange MVP]: "Re: Outbound Appending"
- Next in thread: Paul Cookson: "Re: Outbound Appending"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 25 Feb 2005 10:05:23 -0800
Hi Ben,
I’ve been thinking about this problem over night. Please correct me where I
go wrong as I only have a practical knowledge of Exchange. When a mapi
processed message is passed to exchange it is temporarily converted to an
smtp message and therefore DOES fire the event sink code. The message is
available to the event sink code and can therefore be manipulated, read etc.
Once the event sink has finished its code and loses scope the temporary smtp
message is discarded and the original mapi message sent.
I think I would be able to white an event sink handler to take the temporary
smtp message, duplicate it and append the disclaimer. Then send the
duplicated and modified message to the final recipient. Do you know of a
way in which we can delete the original mapi message AFTER it has been
submitted to the event sink?
Regards,
Paul
"Ben Winzenz [Exchange MVP]" wrote:
> If you think a disclaimer should be a basic function of a world-class e-mail
> server such as Exchange server, then I would suggest to send an e-mail to
> mswish@microsoft.com (yes it actually gets read, and no I'm not joking).
> I'm sure it's not too late to make code changes to E12, but I doubt you will
> find any Microsoft-provided solutions for the current version that go beyond
> what has already been discussed. For the record, I don't necessarily
> disagree that implementing some sort of basic disclaimer function should be
> included, but I would argue that the majority of companies that actually
> require disclaimers would probably require or want more functionality than a
> simple basic disclaimer provides. Rest assured that Exchange is not the
> only "World-class" e-mail server that doesn't provide disclaimer
> functionality out of the box. Lotus Domino, what many would consider
> another world-class e-mail server, also does not provide this functionality
> natively, but has the same type of ugly workaround.
> http://www-1.ibm.com/support/docview.wss?rs=474&uid=swg21087361 details how
> to do this with current versions of Domino. Our Domino guy here says that
> solution is pretty ugly. Domino 7 (still in Beta) will apparently include
> the ability to add disclaimers by default, so I supposed kudos go to them
> for that. In working with Groupwise in the past as well, I found no ability
> there to add disclaimers. I'm not trying to be argumentative on this point,
> and again, I don't disagree that it should be there (Lotus apparently feels
> it should), just pointing out that 2 other major "world-class" e-mail
> systems also don't include this functionality by default either.
>
> As far as the time and effort required to add an additional SMTP Virtual
> server, if you choose to implement the event sink in that manner, it should
> take less than 30 minutes to get set up and working. I'll do this tomorrow
> on one of the Exchange VM's I run to test it. I do understand your point
> about other methods (such as writing your own). Heck, I'm sure that it took
> the 3rd party software providers plenty of time to write their's wih a slew
> of developers working on it. The point I was simply trying to make there is
> that it *is* possible to write your own, and that if you don't like the
> functionality of the sample Microsoft provided, then you ought to pursue
> that. You obviously feel you shouldn't have to write your own, so that's
> fine too. I don't blame you for not wanting to install trial software - I
> was merely pointing out that is one of the current solutions available, and
> it is free to boot. It doesn't mean I would use it, just that it is out
> there.
>
> Further, I also disagree that the disclaimer won't work with Outlook
> Express. OE cannot connect via MAPI. As such, it must submit messages via
> SMTP, and the disclaimer should work just fine. For that matter, Outlook
> clients that connect via IMAP or POP3 would be treated the same, as they
> must submit messages via SMTP. Of course, I could be wrong here as I
> haven't "personally" tested it, but I'll take the chance.
>
> I also don't agree with your take on MAPI. While it is true that normal
> communication between Outlook and Exchange is done via MAPI, and that it is
> a customized version of MAPI, you'll find that practically ANY e-mail server
> that provides groupware capabilities (shared calendaring for example)
> communicates via it's own proprietary protocol. Lotus Domino, for example,
> uses the Notes Remote Procedure Calls (NRPC, or Notes Routing Protocol) by
> default for communication between the Notes client and Domino server. I've
> also worked with Groupwise in the past, and can guarantee you that that
> Groupwise client doesn't communicate with the Groupwise server over standard
> SMTP either. The fact is, SMTP doesn't provide groupware functionality.
> It's an messaging protocol.
>
> --
> Ben Winzenz
> Exchange MVP
>
>
> "Paul Cookson" <PaulCookson@discussions.microsoft.com> wrote in message
> news:FF6B8A50-9887-481E-8A15-7547C03C5A85@microsoft.com...
> > I'm sure people looking for a solution to this most basic of requirements
> > are
> > quite fed up with reading this rubbish, although i have to say your last
> > email was far more useful than the previous opinionated, condescending
> > post.
> > I did take the time to read all your meanderings regarding this problem
> > and
> > have to say although you clearly didn't know the answer to the question I
> > did
> > admire your persistence. I appreciate your loyalty to Microsoft (I also
> > admire Microsoft and the progress made since the 70's, whence I first
> > started
> > using their software.) but your defense of the indefensible is ridiculous.
> > How can you justify the time and effort involved in adding an SMTP server,
> > virtual, third party or otherwise just to add a disclaimer to an email.
> > You
> > say as a programmer it should be easy. Well why should I, as a programmer
> > spend two days (or if I were as clever as you or one of my bosses two
> > hours )
> > adding a function which is such a basic requirement for what is billed as
> > a
> > world class email server. Perhaps you would like to fund such a project
> > because I certainly don't. This problem stems from MS using a proprietary
> > format (mapi) for communications between outlook and exchange (when the
> > rest
> > of the world uses SMTP) or if you like treating mapi messages differently
> > to
> > SMTP submitted messages. Why on earth changes to the mapi submitted
> > message
> > are not persisted are beyond me. I'm sure there must be good reason for
> > this
> > but we are still left with the problem. Where is the "tick box" which
> > attaches the "text box" to the bottom of all outgoing emails. I never
> > jump
> > into the middle of any thread. The soul reason for searching for (and
> > reading) it were only to learn something which I didn't know. That's why
> > my
> > post was at the end. I don't think I said event sinks were a joke. At
> > least
> > my intension was to state, "Not being able to append a disclaimer to an
> > email
> > was a joke and the pretension that event sinks were a viable alternative
> > is a
> > joke." And I have to laugh when I say, "especially when it doesn't work
> > with
> > OUTLOOK or OUTLOOK EXPESS". I would like to hear from other users of
> > exchange
> > who think it's not and ask them to please tell me the answer to the
> > problem.
> > I don't want to install trial software and I don't want to pay for any
> > more
> > software although I have as a short term measure. There must be a way to
> > do
> > this, I just don't know how.
> >
> > "Ben Winzenz [Exchange MVP]" wrote:
> >
> >> How do you expect to get help on these forums when acting like this?
> >>
> >> --
> >> Ben Winzenz
> >> Exchange MVP
> >>
> >>
> >> "Paul Cookson" <PaulCookson@discussions.microsoft.com> wrote in message
> >> news:396DB9A8-C925-49D9-92DC-C25686F21A9B@microsoft.com...
> >> > Ben has worked in the IT field for over 5 years and especially enjoys
> >> > the
> >> > hardware aspect of computers.
> >> >
> >> > Hey Ben, ever heard of lego. Perhaps you should try this in your next
> >> > life.
> >> > And dood, do something with your hair...;-)
> >> >
> >> > "Paul Cookson" wrote:
> >> >
> >> >> 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: manoa: "CDO call to SMTP"
- Previous message: Gregg Hill: "Max size of distribution list in Exchange 2000 or 2003?"
- In reply to: Ben Winzenz [Exchange MVP]: "Re: Outbound Appending"
- Next in thread: Paul Cookson: "Re: Outbound Appending"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
