ATT_A_B_C_D_E_F_G.dat

When the driver is used to retrieve a message, it creates a file to store attachments that are parsed from the incoming message with the naming convention ATT_A_B_C_D_E_F_G.dat where:

• A is the process ID of the application that loads the driver.

• B is the Siebel Communications API handle of the driver.

• C is the Siebel Communications API handle of the service.

• D is the time when the service that received the message is created.

• E is the number of messages that are received during the current POP3 or IMAP session.

• F is the number of attachments that are found so far in the message.

• G is the number of milliseconds that elapsed since the application was started.

When the message is parsed, all non-inline message parts and textual parts of the message are used to create the attachment files in the bin/incoming directory.

Another special instance of this type of file is created when an embedded message is found in the message that is parsed. Embedded messages cause the creation of one of the following two types of files:

• A file with the internal name of EmbeddedMsgX.xml that contains the embedded message header and all plain text parts of the mail. The purpose of this file is the same as the purpose of the OriginalMessageText_A_B_C_D_E_F.txt file.

• A file with the internal name EmbeddedMsgX.eml that contains the MIME message of the embedded message. You can open this file with any application that can read an EML file, such as Microsoft Mail. This file is created only if the Parse Embedded Messages profile parameter is explicitly set to False, and the EmbeddedMsgX.xml file is not created.