I can confirm that NotSpilt6 and three previous versions all have problems as described by the problem submitter. I am guessing that the problems can be one or more of the following.
1. A message size in the folder exceeds the Microsoft 32 bit filesize maximum. This can occur quite easily if a multi-megabyte attachment occurs in a message.
2. A message contains the byte x'1A' dec(27) which is the marker for separating messages in PMM files. There should not be any such bytes in a message. It seems likely that Microsoft is issuing these bytes as part of Cloud-based Outlook messages and not converting these bytes to Base64 format. All messages are supposed to be 7-bit text/plain.
I am investigating detecting this condition and will create a new version of NotSplit to handle this.
P.S I am on 64-bit Windows 10 , and cannot test on previous versions of Windows systems.
Martin
<p>I can confirm that NotSpilt6 and three previous versions all have problems as described by the problem submitter.&nbsp; I am guessing that the problems can be one or more of the following.</p><p>1. A message size in the folder exceeds the Microsoft 32 bit filesize maximum.&nbsp; This can occur quite easily if a multi-megabyte attachment occurs in a message. </p><p>2. A message contains the byte x'1A' dec(27)&nbsp; which is the marker for separating messages in PMM files.&nbsp; There should not be any such bytes in a message.&nbsp; It seems likely that Microsoft is issuing these bytes as part of Cloud-based Outlook messages&nbsp; and not converting these bytes to Base64 format. All messages are supposed to be 7-bit text/plain.</p><p>I am investigating detecting this condition and will create a new version of NotSplit to handle this.&nbsp;&nbsp; </p><p>P.S&nbsp; I am on 64-bit Windows 10 , and cannot test on previous versions of Windows systems.
</p><p>Martin</p>