On Wed, 2021-03-10 at 09:28 +0000, Surla, Sai Kalyan wrote: > Hope you got a chance to at the issue that we reported.
I am looking at the issue today. I managed to reproduce the issue that you have reported using the sample PST file that you have provided. I acknowledge that I am seeing both the issues you reported: * only a limited set of headers are being extracted * email address is missing from the To header - but the From header is correct The readpst -d option to output debug information was instrumental in reproducing this, it causes all the info in the PST file and the entire sequence of decoding steps to be output to a debug file. I modified the valid_headers function to also accept the ARC-Seal header but that does not fix the problem. Looking at the debug output I noticed that the X-GM-THRID header is the first header. I then added a X-GM-THRID to the valid_headers function and that fixed the problem. I think that messages with a different first header will not work though, you would have to add all of the first headers that could exist to the valid_headers function, which seems like an incorrect thing to do. If you have any sample PST files that *do* work with the current code, that would allow me to compare the working PST with the broken PST, which would be very helpful in tracking down where the problem is. Until I can figure out the correct fix, I suggest you workaround this bug by adding "return 1;" without quotes as the first line in the valid_headers function. This way you can keep readpst working for your customers while the correct fix is found. I believe that the modern PST files that you have available are all valid files, while the valid_headers function aims to detect broken files, so there should be no risk to the conversion process for your case. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
