I have no idea what that Web page is sending out. If it meets the normal
RFC's for Internet email then it should be providing message headers and
those should be in the PR_TRANSPORT_MESSAGE_HEADERS property.

If the MAPI property is there (x-header MAPI property) instead of the
correct PR_TRANSPORT_MESSAGE_HEADERS property then I can only assume the Web
page is using Exchange and not sending over the Internet.

If it was truly Internet email sent out by the Web page then the MAPI
property would mean nothing to it. That sort of MAPI property is translated
into an x-header by MAPI when the email goes out through the message
transport. And the MAPI property can only be added using MAPI or an
equivalent API. The property means nothing to something like SMTP mail, or
SQL Server mail or whatever. Certainly a MAPI extended property wouldn't be
preserved except by MAPI.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Ashish" wrote in message
...
Yes you are right if we add headedr then we can read as MAPI property on
exchange server.
Thanks for clear understanding.
In outlook addin we can read mail header using PR_TRANSPORT_MESSAGE_HEADER

For all mails we can read header using PR_TRANSPORT_MESSAGE_HEADER in
outlook addin. and using MAPI property on exchange server.
But below case(send mail using webpage) MAPI property on exchange server
can read header, but outlook addin fail to read header. It shows empty
header.

Is there any reason why it's happening