Topic Last Modified: 6/8/2004
The IMailMsgProperties interface defines methods used to access transport envelope properties and message content for a MailMsg object.
Write a property.
Get a property.
Commit properties to disk.
Write a string property.
Get a string property.
Write a UNICODE string property.
Get a UNICODE string property.
Write a DWORD property.
Get a DWORD property.
Write a BOOL property.
Get a BOOL property.
Get the content size in bytes (with asynchronous completion).
Read content from the object.
Write content into the object.
Write (copy) content to the specified file.
Write (copy) content to file starting at the specified byte offset.
Write (copy) content to the object exposing the IStream interface.
Return a new MailMsg object for different recipients.
Allocates storage and re-binds the MailMsg object.
The IMailMsgProperties interface is primary for a MailMsg object. Through this interface, the following functionality is provided:
Read/write access to the transport envelope properties. Properties can be of type BOOL, LPSTR, LPWSTR, and DWORD.
Read/write access the message's content stream.
Write message content to some location using a HANDLE value you create. The handle must have been created with the FILE_FLAG_OVERLAPPED flag and have been associated with an FIO_CONTEXT structure using the AssociateFile function. All I/O functions for the MailMsg object require use of this structure.
Duplicate the MailMsg object (fork) and set new recipients.
Rebind the duplicated MailMsg object to the current store driver.
A MailMsg object that is bound to the store driver has its properties and content automatically persisted to physical storage. Updates to the physically stored contents only occur when the IMailMsgProperties::Commit method is invoked.
Unbound MailMsg objects do not have properties or message content persisted to physical storage.