Hi Paul,

In this case can we still go with the temporary change that you suggested as 
the issue is little different with this PST?

Thank you
Sai Kalyan

From: Paul Wise <p...@debian.org>
Sent: 19 March 2021 08:26 AM
To: Surla, Sai Kalyan <saikalyan.su...@arcserve.com>; 984...@bugs.debian.org
Subject: Re: Bug#984581: pst-utils: Fails to extract email addresses for emails 
having ARC headers from PST file

On Fri, 2021-03-19 at 09:03 +0800, Paul Wise wrote:

> The specs indicate that 0x39fe is indeed the recipient address:

The issue in libpst when there are no MIME headers in the PST file is:

There are some MAPI properties for To/CC/BCC:

https://docs.microsoft.com/en-us/office/client-developer/outlook/mapi/pidtagdisplayto-canonical-property<https://docs.microsoft.com/en-us/office/client-developer/outlook/mapi/pidtagdisplayto-canonical-property>
https://docs.microsoft.com/en-us/office/client-developer/outlook/mapi/pidtagdisplaycc-canonical-property<https://docs.microsoft.com/en-us/office/client-developer/outlook/mapi/pidtagdisplaycc-canonical-property>
https://docs.microsoft.com/en-us/office/client-developer/outlook/mapi/pidtagdisplaybcc-canonical-property<https://docs.microsoft.com/en-us/office/client-developer/outlook/mapi/pidtagdisplaybcc-canonical-property>

These contain *only* the names and not the addresses.

Outlook fills them automatically from the list of recipients.

Outlook stores the recipients in a separate table to email properties.

libpst stores them in the sentto/cc/bcc fields of the email structure.

libpst has no storage of the recipients table of the PST file.

libpst processes the MAPI types one-by-one rather than in separate
tables and only has one action per MAPI type.

So this is not going to be easy to fix.

I will discuss this with upstream.

--
bye,
pabs

https://wiki.debian.org/PaulWise<https://wiki.debian.org/PaulWise>

Reply via email to