| Platform SDK: CDO for Windows 2000 |
The majority of relevant properties you set on a body part are mail and MIME header fields that are defined by the various Internet standards. The urn:schemas:mailheader: namespace is reserved for these fields. Translating a mail header to a property name is simple: concatenate the namespace with the name of the header field (in lowercase); for example, the Content-Type header field is called the urn:schemas:mailheader:content-type property in the Fields collection. All properties within this namespace are stores as US-ASCII characters. Other character sets are encoded using the standard mechanism outlined in RFC 1522.
The following table lists the most common fields used with BodyPart objects. These fields share the urn:schemas:mailheader: URI reference namespace.
The default schema for messaging provides the most common mail header fields defined by the Internet standards; however, you can add properties to this namespace and set them on BodyPart and Message objects to add custom headers that are not provided by default. When the message or body part is serialized (to send or post, or a call to the GetStream method), each of these fields is translated back into an appropriate message or MIME header; for example, if you set the "urn:schemas:mailheader:My-Property" property to equal "isokay", the serialized stream for the body part or message would contain the header field My-Property: isokay in the stream.
There are also properties within the urn:schemas:httpmail: namespace that are used with body parts: