Siebel Communications Server Administration Guide > Administering Siebel Communications Server > Administering Communications Inbound Receiver >

Activity Attachments Stored for Inbound Email

For each inbound email message that has been processed by Communications Inbound Receiver or Communications Inbound Processor, an activity record is created, using activity type Email - Inbound. The original email content is saved in the form of one or more attachments to this activity record.

The entire original email message content (the entire MIME message as received by the POP3 server) is saved in an attachment file named OriginalMsg.txt.

If the original message is more than 16,000 characters long (including any HTML markup), then the full message is saved as another attachment, named SiebelLongEmailBody.txt (for plain-text messages) or SiebelLongEmailBody.htm (for HTML messages).

Additional files may be created and saved as attachments to the activity, depending on the existence of embedded message content and on the setting of the Parse Embedded Messages parameter for the Internet SMTP/POP3 Server driver. For more information about this parameter, see Driver Parameters for Internet SMTP/POP3 Server Driver.

• When Parse Embedded Messages is FALSE, the following behavior applies:
  • For each embedded message, a single attachment file is created that contains the entire MIME embedded message. These files are named EmbeddedMsgpartspecifier.eml, where partspecifier represents the file's placement in the original message's structure—for example, EmbeddedMsg01.eml, EmbeddedMsg3.4.eml, and so on. These files can be opened using any application that can read an EML file, such as Microsoft Outlook Express.
• When Parse Embedded Messages is TRUE (the default), the following behavior applies:
  • For a plain-text email message, all text components are saved in one or more attachment files. These files are named textplainpartspecifier.txt, where partspecifier represents the file's placement in the original message's structure—for example, textplain01.txt, textplain3.4.txt, and so on.
  • For an HTML email message, all HTML components are saved in one or more attachment files. These files are named texthtmlpartspecifier.htm, where partspecifier represents the file's placement in the original message's structure—for example, texthtml01.htm, texthtml3.4.htm, and so on.
  • Any attachments to the original email message are also saved as attachments to the activity record, using their original file names.