comparison 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
comparison
equal deleted inserted replaced
59:7d5c637aaafb 60:97b7706bdda2
1492 0029 Read Receipt 1492 0029 Read Receipt
1493 002b Reassignment Prohibited 1493 002b Reassignment Prohibited
1494 002e Original Sensitivity 1494 002e Original Sensitivity
1495 0036 Sensitivity 1495 0036 Sensitivity
1496 0037 Email Subject 1496 0037 Email Subject
1497 0039 Date. This is likely to be the arrival date 1497 0039 Client submit time / date sent
1498 003b Outlook Address of Sender 1498 003b Outlook Address of Sender
1499 003f Outlook structure describing the recipient 1499 003f Outlook structure describing the recipient
1500 0040 Name of the Outlook recipient structure 1500 0040 Name of the Outlook recipient structure
1501 0041 Outlook structure describing the sender 1501 0041 Outlook structure describing the sender
1502 0042 Name of the Outlook sender structure 1502 0042 Name of the Outlook sender structure
1524 0c1a Name of second sender structure 1524 0c1a Name of second sender structure
1525 0c1d Second outlook name of sender 1525 0c1d Second outlook name of sender
1526 0c1e Second sender access method (SMTP, EX) 1526 0c1e Second sender access method (SMTP, EX)
1527 0c1f Second Sender Address 1527 0c1f Second Sender Address
1528 0e01 Delete after submit 1528 0e01 Delete after submit
1529 0e03 CC Address? 1529 0e02 BCC Addresses
1530 0e03 CC Addresses
1530 0e04 SentTo Address 1531 0e04 SentTo Address
1531 0e06 Date. 1532 0e06 Date.
1532 0e07 Flag - contains IsSeen value 1533 0e07 Flag bits
1534 0x01 - Read
1535 0x02 - Unmodified
1536 0x04 - Submit
1537 0x08 - Unsent
1538 0x10 - Has Attachments
1539 0x20 - From Me
1540 0x40 - Associated
1541 0x80 - Resend
1542 0x100 - RN Pending
1543 0x200 - NRN Pending
1533 0e08 Message Size 1544 0e08 Message Size
1534 0e0a Sentmail EntryID 1545 0e0a Sentmail EntryID
1535 0e1f Compressed RTF in Sync 1546 0e1f Compressed RTF in Sync
1536 0e20 Attachment Size 1547 0e20 Attachment Size
1537 0ff9 binary record header 1548 0ff9 binary record header
1800 (0xea, 0xf0) pair. That gives us (0xf0 - 0xea)/6 = 1, so we have a 1811 (0xea, 0xf0) pair. That gives us (0xf0 - 0xea)/6 = 1, so we have a
1801 recordCount of one. The actual data between 0xea and 0xf0 is unknown 1812 recordCount of one. The actual data between 0xea and 0xf0 is unknown
1802 and unused here. 1813 and unused here.
1803 </para> 1814 </para>
1804 <para> 1815 <para>
1816 We have seen cases where the descoffset in the b5 block is zero, and
1817 the index2Offset in the 7c block is zero. This has been seen for
1818 objects that seem to be attachments on messages that have been
1819 read. Before the message was read, it did not have any attachments.
1820 </para>
1821 <para>
1805 Note the index2Offset above of 0x0080, which again is an index reference. In this 1822 Note the index2Offset above of 0x0080, which again is an index reference. In this
1806 case, it is an internal pointer reference, which needs to be right shifted 1823 case, it is an internal pointer reference, which needs to be right shifted
1807 by 4 bits to become 0x0008, which is then a byte offset to be added to 1824 by 4 bits to become 0x0008, which is then a byte offset to be added to
1808 the above indexOffset plus two (to skip the count), so it points to the 1825 the above indexOffset plus two (to skip the count), so it points to the
1809 (0xf0, 0x155) pair. This is an array of tables of four byte integers. 1826 (0xf0, 0x155) pair. This is an array of tables of four byte integers.