Closed basinilya closed 2 years ago
What it means is that outlook-message-parser should have better support for the In-Reply-To header (if feasible). Would that solve your problem? In which case, would you be able to provide me with a sample msg that includes this header?
Would that solve your problem?
Partially. I'm porting msgconvert
from perl to java and there are 3 or 4 properties used there, but unsupported here.
would be able to provide me with a sample
Don't have Outlook now, sorry.
Ok great, let's see if we can improve this library and add support for those properties. Which properties are you missing?
0x1042 In-Reply-To
0x1039 References
0x0047 submissionId
But why are you so reluctant to make the getter public? Even the setter is public!
Oh that's easy, because then I wouldn't get to see bug reports like this one and the library would remain in the plane of mediocrity forever. But I might make it public anyway, because users need a backup in case something is missing.
Well, you got your wish (finally). I made the method public. Just got released in 1.8.1
OutlookMessage.getPropertyValue() should be public. It's just common sense. Meanwhile I'll use reflect to extract
1042 In-Reply-To: