Re: OnSyncSave and MAPI

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Alan Borland (alan.borland_at_dsl.pipex.com)
Date: 08/06/04 

Date: Fri, 6 Aug 2004 22:28:40 +0100

Thanks for the advice. It seems that PR_ENTRYID is setup for MAPI in the
OnSave, but not the OnSyncSave event. Shame I can't globally register an
OnSave event!

Alan.

"Victor Ivanidze" <no@spam.please> wrote in message
news:eNHpEgqeEHA.3348@TK2MSFTNGP12.phx.gbl...
> Alan,
>
> we did the same thing using asynchronous event sink (OnSave) and MAPI
quite
> successfully.
> Hope that helps.
>
> Regards,
>
> Victor Ivanidze,
> software developer
> www.ivasoft.biz
>
>
>
> > Hi,
> >
> > I have a requirement to move a message between two mail boxes that may
> exist
> > on different Exchange Servers. The functionality has to work without
any
> > clients running. Easy I thought, use an OnSyncSave event to trap the
> > message and forward it onto the other user. However, these messages use
> > custom forms and all of the 'custom' information is dropped because the
> > CDOEX 'forward' method seems to drop the TNEF - Can this be overcome?
> >
> > Next I tried to use the ADO CopyRecord function. I started by copying
the
> > message to a local folder within the same mailbox - this worked. I then
> > copied the message to the other mailbox, but this fails, despite being
> able
> > to view the other mailbox from Outlook and having all the permissions I
> > could want. Other posts suggestion this isn't possible?
> >
> > Third attempt has been to logon to MAPI inside my OnSyncSave event and
> then
> > extract the PR_ENTRYID / PR_STORE_ENTRYID from the ADO record and
perform
> an
> > OpenEntry / OpenMsgStore respectively. These fail with 0x80040107 and
> > 0x80040201.
> >
> > My Server has Windows 2003 & Exchange 2003 and I've started to notice
that
> > some of the Microsoft sample apps don't function on my server (Q259570),
> but
> > do function on the client. It would appear that the version of MAPI on
> the
> > server is different to that on the client (could this be my problem?).
I
> > tried moving MAPI32.dll around but the Exchange System Manager
> complained -
> > does a technique exist for accessing MAPI on Windows 2003?
> >
> > Am I trying the impossible? Any suggestions are greatly received.
> >
> > Thanks,
> >
> > Alan.
> >
> >
> >
>