I've found another MSG generation problem with Aspose.Email (5.3).
At customer – a lot of messages don't actually contain any
named properties:
Stream: __substg1.0_00040102
Size: 0
However, the same message exported from PST via Aspose results in this:
Stream: __substg1.0_00040102
Size: 1
And the content of this stream:
0000000000: 00
I've included a sample message and the PST file that the message was exported from via Aspose.Email component for you to check.
Our processing library checks MSG violations and fails on this.
I guess there are more than one problem with NamedProperty storage - (1 bug there already – EMAILNET-34810 - not aligned entries on 4 byte boundary). Could you please make sure this violation is fixed along that other bug.
So in case there are NO string NamedProperties - the stream should end up completely empty.
Could you give an rough estimate when these violations will be fixed? Are there any plans to fix them in an upcoming version?
Best regards,
Michal