Overview

Represents a type of content that contains email attributes such as sender and receivers. All email messages have email message content as top level content. An email message content can also be embedded in a content hierarchy to represent an attached or forwarded email message.

Members

Show inherited members

Projections
Name Type Required Description

BCCReceivers

emailRecipient[]

"Blind Carbon Copied" recipients. BCC recipients are only visible to the sender of the message.

CCReceivers

emailRecipient[]

"Carbon Copied" recipients. CC recipients are considered secondary recipients of an email message.

TOReceivers

emailRecipient[]

Receivers on the "TO" list. "TO" list of recipients are considered the primary recipients of an email message.

body

content

The body of the message. The body typically is a simpleContent if no attachments are present, otherwise it can be a multiContent that represents a heirarchy of parts and attachments.

contentDisposition

contentDispositionType

Content disposition of this content. The disposition of a content can be INLINE or ATTACHMENT.

contentEncoding

contentEncodingType

Transport encoding of this content. Encoding can be SEVEN_BIT, EIGHT_BIT, BASE64 or QUOTED_PRINTABLE

contentId

string

ID of this content. A content component in a multipart/related content group has a unique ID property that can be used to reference the part in an HTML part within the group.

from

emailParticipant

The envelope sender of this email message. An envelope sender is system-identified with authenticity. Envelope sender is only available to top level email message contents. An embedded message does not have this value

inReplyTos

string[]

The list of message content IDs identifying the conversation context, also known as the In-Reply-To header

mailer

string

Mailer (mail client program) string identifier

mediaType

string

The IANA media type for this content. This is also known as MIME type.

mimeHeaders

mimeHeadersWrapper

The collection of MIME headers associated with this content. Every content object may potentially come from MIME source regardless of its type. Therefore along with content data and attributes there can be arbitrary MIME headers associated with it.

priority

priority

The priority indicator for the message. Priority can be NONE, LOW, MEDIUM or HIGH.

replyTo

emailParticipant[]

The list of Reply-To addresses. The Reply-To addresses if present are to be used as targets to receive a reply message.

sender

emailParticipant

The published sender of this message content. This sender attribute is furnished by the sender and therefore may contain personalized, alternative identity that deviates from the envelope sender.

sensitivity

messageSensitivity

Sensitivity indicator for the message. Sensitivity can be PRIVATE, PERSONAL or COMPANY_CONFIDENTIAL

sentDate

dateTime

Sent date associated with the message as recorded by the sender's mail client program.

size

long

Size of the message content in bytes. The size represents the amount of bytes required to transfer the email message in MIME format, which is not exactly the same as the size of the saved message in other formats.

subject

rawString

The subject of the message in a raw string format. In rare cases subject of a message may come from a source where the declared character set decoding is incorrect or corrupted, in which case the raw format allows the client to preserve the original data and interpret it differently.

threadReferences

string[]

The thread references for the message identifying the conservation chain.

type

contentType

Type of the content. A content can be of type MULTIPART, INLINE, MESSAGE or REFERENCE.

Hierarchy

Inherits From

Examples

Below are examples in XML formats. All examples are shown with all inherited members. Quoting when required is part of the examples, but you must obviously populate with your own data.

XML Example

(show inherited members)

<obh:emailMessageContent xsi:type="obh:emailMessageContent" xmlns:obh="http://www.oracle.com/beehive" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <BCCReceivers>your_emailRecipient_0</BCCReceivers>
        <BCCReceivers>your_emailRecipient_1</BCCReceivers>
        <BCCReceivers>your_emailRecipient_2</BCCReceivers>
        <CCReceivers>your_emailRecipient_0</CCReceivers>
        <CCReceivers>your_emailRecipient_1</CCReceivers>
        <CCReceivers>your_emailRecipient_2</CCReceivers>
        <TOReceivers>your_emailRecipient_0</TOReceivers>
        <TOReceivers>your_emailRecipient_1</TOReceivers>
        <TOReceivers>your_emailRecipient_2</TOReceivers>
        <body>your_content_0</body>
        <contentDisposition>your_contentDispositionType_0</contentDisposition>
        <contentEncoding>your_contentEncodingType_0</contentEncoding>
        <contentId>your_string_0</contentId>
        <from>your_emailParticipant_0</from>
        <inReplyTos>your_string_0</inReplyTos>
        <inReplyTos>your_string_1</inReplyTos>
        <inReplyTos>your_string_2</inReplyTos>
        <mailer>your_string_0</mailer>
        <mediaType>your_string_0</mediaType>
        <mimeHeaders>your_mimeHeadersWrapper_0</mimeHeaders>
        <priority>your_priority_0</priority>
        <replyTo>your_emailParticipant_0</replyTo>
        <replyTo>your_emailParticipant_1</replyTo>
        <replyTo>your_emailParticipant_2</replyTo>
        <sender>your_emailParticipant_0</sender>
        <sensitivity>your_messageSensitivity_0</sensitivity>
        <sentDate>your_dateTime_0</sentDate>
        <size>your_long_0</size>
        <subject>your_rawString_0</subject>
        <threadReferences>your_string_0</threadReferences>
        <threadReferences>your_string_1</threadReferences>
        <threadReferences>your_string_2</threadReferences>
        <type>your_contentType_0</type>
</obh:emailMessageContent>

Referenced By Representaions