diff xml/libpst.in @ 60:97b7706bdda2

Work around bogus 7c.b5 blocks in some messages that have been read. They appear to have attachments, but of some unknown format. Before the message was read, it did not have any attachments. Use autoscan to cleanup our autoconf system. Use autoconf to detect when we need to use our XGetopt files and other header files. More fields, including BCC. Fix missing LE32_CPU byte swapping for FILETIME types.
author Carl Byington <carl@five-ten-sg.com>
date Sat, 16 Feb 2008 12:26:35 -0800
parents a8b772313ff4
children cfd6175f9334
line wrap: on
line diff
--- a/xml/libpst.in	Thu Feb 14 14:55:32 2008 -0800
+++ b/xml/libpst.in	Sat Feb 16 12:26:35 2008 -0800
@@ -1494,7 +1494,7 @@
 002e  Original Sensitivity
 0036  Sensitivity
 0037  Email Subject
-0039  Date. This is likely to be the arrival date
+0039  Client submit time / date sent
 003b  Outlook Address of Sender
 003f  Outlook structure describing the recipient
 0040  Name of the Outlook recipient structure
@@ -1526,10 +1526,21 @@
 0c1e  Second sender access method (SMTP, EX)
 0c1f  Second Sender Address
 0e01  Delete after submit
-0e03  CC Address?
+0e02  BCC Addresses
+0e03  CC Addresses
 0e04  SentTo Address
 0e06  Date.
-0e07  Flag - contains IsSeen value
+0e07  Flag bits
+          0x01 - Read
+          0x02 - Unmodified
+          0x04 - Submit
+          0x08 - Unsent
+          0x10 - Has Attachments
+          0x20 - From Me
+          0x40 - Associated
+          0x80 - Resend
+          0x100 - RN Pending
+          0x200 - NRN Pending
 0e08  Message Size
 0e0a  Sentmail EntryID
 0e1f  Compressed RTF in Sync
@@ -1802,6 +1813,12 @@
                 and unused here.
             </para>
             <para>
+                We have seen cases where the descoffset in the b5 block is zero, and
+                the index2Offset in the 7c block is zero. This has been seen for
+                objects that seem to be attachments on messages that have been
+                read. Before the message was read, it did not have any attachments.
+            </para>
+            <para>
                 Note the index2Offset above of 0x0080, which again is an index reference. In this
                 case, it is an internal pointer reference, which needs to be right shifted
                 by 4 bits to become 0x0008, which is then a byte offset to be added to