Currently I am running test cases through a client program that I built out 
of exchange2mbox and the 0.8 release of exchange2ical. Right now I have two 
strange cases for which I would need some advice.


The first one was created accidentally. I sent a message with attachments
from OWA and then I moved the message from Sent Items to the Inbox.
In OWA it looks like a regular mail with names and addresses on the
To and CC lines. However, when I use my mapi client to download this
message, I don't get any PR_TRANSPORT_MESSAGE_HEADERS. That's not 
surprising since this message hasn't really been sent, it's a local copy.
But how can I get the To and CC (and BCC) information? I tried all sorts
of tags that have EMAIL, TO or CC in it, but they all come up empty. 
Since I can see this info in OWA, it must be somewhere. (Normally I 
rely only on the transport headers to get all the to & from info.)


The second case is an invitation that I sent from Thunderbird. In OWA
it shows up as an email with the calendar icon. It has a text line in
the body that was apparently generated by TB. It also has an attachment
called invite.ics. Now let's look at a code snippet:
http://www.pastebin.ca/1351665
The debug print statements in lines 33-38 all print some reasonable
information. But the OpenMessage on line 41 fails with MAP_E_INVALID_PARAMETER.
(exchange2ical also calls OpenMessage for each item is processes.)

The obvious question is of course, why does this fail and what kind of test
should I do before calling OpenMessage?
But then I am also wondering what I can do with the table I got from QueryRows 
(line 29), what is the set of tags that could get at this stage, and for what 
operations do I need to call OpenMessage? Can I get the full body and the 
attachments after QueryRows or does that require a message object from 
OpenMessage?



-- 
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel

Reply via email to