PR_RTF_COMPRESSED and PR_RTF_IN_SYNC in journaled message Options
Category: MAPI
Hi All:
I'm trying to track down why some of my customers have
PR_RTF_COMPRESSED and PR_RTF_IN_SYNC properties in pairs and others do
not.
Here is the scenario:
- exchange 2003
- envelope journaling
- user a sends user b a message with no body; the message is
journaled.
The "original" email has a PR_RTF_COMPRESSED mapi property of 135
bytes
in both the original message and the journaled message and
PR_RTF_IN_SYNC is set to true.
However, one customer has PR_RTF_IN_SYNC set to true in the journaled
message but there is no PR_RTF_COMPRESSED property (nor is there a
PR_BODY). Since I'm using this field to see if the messages are the
same, the comparison doesn't work. I have checked the exchange
delivery settings and the message formats seem ok.
Does anyone know what would cause this behavior (no PR_RTF_COMPRESSED
in the journaled message)?
Thanks,
Jay
--------------------------------------------------------------------------
The MAPI-L list is hosted on a Windows NT(TM) machine running L-Soft
international's LISTSERV(R) software. For sub/unsub info and archives,
see http://peach.ease.lsoft.com/archives/mapi-l.html .
COPYRIGHT INFO:
http://peach.ease.lsoft.com/scripts/wa.exe?SHOWTPL=COPYRIGHT&L=MAPI-L
Questions or comments? Feel free to post them here. No login or id required.
