| Platform SDK: CDO for Windows 2000 |
Many of the properties defined by the IMessage interface closely follow those defined by the RFC 822 and RFC 850 specifications. The properties derived from RFC 822 and RFC 850 are summarized in the following table. Each property is of the String (BSTR) type. When accessed through the properties on the interface, the values for these headers are decoded if necessary (if the header contains non-ASCII characters encoded according to RFC 1522, they are decoded before being returned.).
RFC 822 and RFC 850 Header Field Properties
| Property | Description |
|---|---|
| To | The RFC 822 To: header field for the message. Identifies the primary recipients of the message. |
| From | The RFC 822 From: header field for the message. Identifies the sender of the message. |
| Subject | The RFC 822 Subject: header field for the message. Identifies the subject of the message. |
| CC | The RFC 822 CC header field for the message. Identifies secondary or carbon copy recipients for the message. |
| BCC | The RFC 822 Bcc header field for the message. Identifies blind carbon copy recipients for the message. |
| Sender | The RFC 822 Sender header field for the message. Identifies the person or entity that actually submitted the message if this person or entity is not the sole identity in the From header. |
| Keywords | The RFC 822 Keywords header field. Identifies one or more words that best summarize the purpose or subject of the message. |
| ReplyTo | The RFC 822 Reply-To header field. Identifies the recipient address or addresses to which replies to the message should be sent. RFC 850 formatted messages also require this header field. |
| FollowUpTo | The RFC 850 optional Followup-To header field. Identifies USENET news groups to which an author should post responses. |
| Organization | The RFC 850 optional Organization header field. Identifies the organization that the posting entity belongs to. |
| SentOn
(Read-only) |
Correlates to the Date header field on an existing message. This property is read-only because it is normally set when the message is originally transmitted. |
| ReceivedTime
(Read-only) |
Correlates to the last Received header field for the message. Each transport (normally SMTP) adds a Received header when the message is received. |
Three properties defined on the IMessage interface are references (COM interfaces) on other objects. These properties are listed in the table below, along with a brief description of each.
IMessage Interface Properties
| Property | Description |
|---|---|
| Configuration | An IConfiguration object reference to a Configuration object that is associated with the message. This object holds configuration information that is used when constructing and sending messages. |
| HTMLBodyPart | An IBodyPart object reference to the BodyPart object containing the HTML representation of the message. This object, if present, is always a sub-object within the message's body part hierarchy. |
| TextBodyPart | An IBodyPart object reference to the BodyPart object containing the text representation of the message. This object, if present, is always a sub-object within the message's body part hierarchy. |
In the CDO object model, many objects can reference the same Configuration class instance to store configuration information in a central manner. In most cases, you can create a single Configuration class instance, populate it with relevant configuration information, and then reference it with each CDO top-level object.
Finally, the IMessage interface provides properties used to navigate to other interfaces on the object, which are described in the following table.
IMessage Interface Properties for Navigation
| Property | Description |
|---|---|
| BodyPart | Returns the IBodyPart interface on the object. Instances of the Message COM class expose the IBodyPart interface. |
| DataSource | Returns the IDataSource interface on the object. Instances of Message COM classes expose the IDataSource interface. |