Developer Forum

I've read in the MAPI-L mailing list that if you create a named property
with a GUID of {00020386-0000-0000-C000-000000000046}, the property name
will become the custom header name and its value will be the header value.

I can't find any documentation on this GUID on the MSDN site. Where is it
documented?

Is this supported on specific versions of Exchange Server or all versions?
--

Mark Wilson

It is not documented anywhere of course. That's why there is MAPI-L list and
this newsgroup :-)
It worked in all versions of Exchange (5.5, 2000, 2003, I did not test 5.0)
as well as in the SMTP provider in all versions of Outlook in my tests.

Dmitry Streblechenko (MVP)
http://www.yqcomputer.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

Thanks Dmitry.

That was hte answer I needed.

Mark Wilson.

Hi Dmitry.

Is there any way to control the case of the header?

In my code I name the property "X-Header" and when the message is sent from
Outlook 2000 through an Exchange 5.5 server, the received SMTP header says

X-Header: SOME_VALUE

However when I use the same code to send through Outlook 2003 to a POP3
server I name the property "X-Header" and the received header says:

x-header: SOME_VALUE

Is there any way to prevent Outlook from forcing the custom x-header name to
all lower case characters?

I don't think you can do that. Why does it matter? According to RFCs, the
headers are case independent.

Dmitry Streblechenko (MVP)
http://www.yqcomputer.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

I just don't like somebody changing my selection for me. I guess its not
really important. Outlook 2003 seems to be the only version that forces
lower case.

Thanks.

--Mark