MAPI Issues - can anyone help?

[MerlinB]

I am trying building an exchange archive system. I can archive (journal) to a mailbox, including the bcc information. However:

1. The MAPI properties for each recipient does not initially say if it is a distribution list or not. So I have to go to the address book to get additional properties for each recipient. Is there any way to make this very efficient?
1.1 The bcc recipients refer to temporary entry IDs. I have to use the Display Name to do an address book lookup. This is most inefficient. Surely I can use the SEARCH_KEY or some other identifier to search the addres book - any tips on doing this would be appreciated.

2. MAPI exposes a property that includes the EML file name of the email in Exchange2000 - the file stored on the M: drive.
However, this property does not escape the file name correctly - so £$%^" type characters come out as %2E in the MAPI property, when they are not always escaped in the file system.
If I use CDO for Exchange2000 (which does NOT expose the BCC recipients), it does provide the correct EML file name in the DAV:href property.
2.1 I cannot see a way to link a mail item in MAPI to its corresponding entry in CDO for Exchange2000. Is there any way? I am sure that a unique entry id should exist in both systems - and that these entry ID's can be converted either way.

http://www.corporateinternet.com

 

[wibbe]

I think you are trying to move/archive items within the exchange database. Is it correct?
Then I think it is easier to change the attributes for the object and link the item to the archive-store and dont use mapi to extract the message. In this case you will keep the singel store and dont overload the server.

// Wibbe

 

[MerlinB]

I move the items out of exchange to a separate (MIME complient) system. MAPI is the only product that provides the BCC information that I need (CDO blanks it out). But MAPI, which does not know or care about the message file format - it does not understand SMTP or offer a Stream to access the original mail. But in Exchange 2000, the mail is stored in MIME format in the normal filing system - just what I need. And MAPI even exposes a property with this file name - except that it is incorrectly encoded. So I get so close to a solution, but then I am thwarted again.

http://www.corporateinternet.com