incorrectly encoded string property raises exception

[srepmub]

one of our customers provided a PST file which contains an incorrectly encoded PR_BODY property somewhere. looking at it, it contains the following byte sequence:

0x3d 0xd8 0xd 0x0

so a surrogate pair is started, but the next 2 bytes to complete it aren't there.. or something. it seems useful for your version to at least add errors='ignore' to the decode call, so the whole process will just go on.

elif self.ptype == PTypeEnum.PtypString:

•        return bytes.decode('utf-16-le') # unicode
  

•       return bytes.decode('utf-16-le', errors='ignore') # unicode
  

[bli-dn]

Long time to respond, sorry :) if you do a PR I will merge for you