wieseljonas / java-libpst

Automatically exported from code.google.com/p/java-libpst
1 stars 1 forks source link

Missing methods? #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I'm tring to use the library in an application and it has been very 
successful. However, I have a problem with some missing information. On 
some emails sent by the owner of the PST file the getSender methods are 
empty but looking at the PstMessage's toString, it seems to have the 
correct information inside but no methods to access it. They are appearing 
in table items keyed on 33068, 59, 3097, 3624, 3625.

I think this is happening when the emails are internal in the organisation 
so they don't leave the exchange server and don't get a transport message 
header.

Is it possible some methods to get at this information are missing? Or is 
it just we don't know exactly what it is they are refering to that there 
is no direct get method to those item ids?

Thanks for all the good work

Stuart 

Original issue reported on code.google.com by stuarthe...@gmail.com on 28 May 2010 at 3:32

GoogleCodeExporter commented 9 years ago
Stuart, totally possible that we are missing some methods.

Most of the keys were ripped directly from this document:

http://sourceforge.net/projects/libpff/files/documentation/MAPI%20definitions/MA
PI%20definitions.pdf/download

Some attributes have been worked out since I did my stuff, and there is 
probably better documentation available in MSDN somewhere...

Looks like you might be finding some "One-off entry identifier" entries?  I 
don't think there is any code for interpreting these, but looks pretty straight 
forward.  Would be happy to help if I could get my hands on a PST file with 
some of these entries...

Glad it's (partly) working for you.

Richard

Original comment by rjohnson...@gmail.com on 18 Jun 2010 at 3:51

GoogleCodeExporter commented 9 years ago
Best document is [MS-OXPROPS].pdf - should be easy to find with google.

Can't help with 33068 - need the reverse mapping to the named ID.
59=0x3B - PidTagSentRepresentingSearchKey - Binary
3097=0x0C19 - PidTagSenderEntryId - Binary
3624=0x0E28 - PidTagPrimarySendAccount - String (I don't even have this in my 
PropertyNames.txt file)
3625=0x0E29 - PidTagNextSendAcct - String (nor this)

I'll add access methods for these to PSTMessage in my patches.

Orin.

Original comment by orin.e...@gmail.com on 22 Jul 2010 at 6:34

GoogleCodeExporter commented 9 years ago

Original comment by rjohnson...@gmail.com on 10 Sep 2010 at 1:20