Summarizing Fields in Exported EML Format

Prerequisites

Ensure that the sufficient space in the folder available in the SFTP server.

If the number of messages per folder exceeds the maximum value, the current folder is zipped and sent, and a new folder is created to archive new messages.
If the folder size exceeds the maximum limit, the current folder is zipped and sent, and a new folder is created to archive new messages.

Sample EML

The ZIP file contains the EML files with attachments and manifest file (.mf)

The sample EML file: Sample ZIP

Manifest File Validation

Each ZIP file includes a manifest file (.mf) listing all EML files inside.

When performing post-processing on the manifest file, make sure of the following:

Count check: The Count: value in the manifest must exactly match the number of EML files in the ZIP.
File-name match: Each file name listed in the manifest must be present in the ZIP file with the exact same name.
File integrity: Verify that all listed files are present and not zero-byte files.

Sample Manifest File

Count: 5
File: telemessage_034a4494-7753-4fcf-8515-37f29e54ff7a_2024080510.eml
File: telemessage_aaa97a14-71b0-47d0-9514-6c2819703af1_2024080510.eml
File: telemessage_de13bd6e-87ab-44d3-b026-53efea798749_2024080510.eml
File: telemessage_b26078a3-5a69-41c8-bf53-3dc995d39857_2024080510.eml
File: telemessage_b43ad1fc-0866-4997-8fb8-1d9d1774530f_2024080510.eml

After you validate the manifest file and confirm that all EML files are present and correct, the data can be enriched in the EML files with the details stored under each user in the Managing Users section.

For more information about how captured messages are delivered and displayed, see Capture Mobile Delivery Options and Display Formats.

This enrichment ensures that user-specific metadata (such as name, department, or compliance attributes) is appended to the EML records, enabling more complete reporting and analysis.

Naming Convention for the ZIP File

The naming convention for the ZIP file follows this format:

YYYYMMDD0000-TeleMessage_<file#>_<TimeZipped>.zip

Where:

YYYYMMDD: Represents the year, month, and day of file creation.
0000: A static value placeholder.
TeleMessage: The fixed prefix for identifying the type of data.
<file#>: A sequential number assigned based on the file size or the number of messages. If the contents exceed a set limit (file size or number of messages), additional files are created with incrementing numbers.
<TimeZipped>: Denotes the time when the file was zipped, expressed in HHMMSS format.

For example: 202409080000-TeleMessage_1_224500.zip

EML Format

The following table summarizes all fields in the exported EML format:

Fields	Description
Date	The date and time when the email was sent, including the time zone. For example, `Mon, 5 Aug 2024 14:00:23 +0000 (GMT)`
From	The sender's email address or phone number. For example, `15747591156 prouser_sftp_eml1@tm.com`
TO	The recipient's email address or phone number. For example, `972526782396 972526782396@archive.telemessage.com`
Message-ID	A unique identifier for the email message, generated by the mail server. For example, `142761991.39.1722854080597@package-pre-service-86cd89d57f-v68fd`
Subject	The subject line of the email, summarizing its content. For example, `SMS from 15747591156 to 972526782396`
X-TELEMESSAGE-ThreadName	The name of the thread (if any) associated with this message.
X-TELEMESSAGE-ArchiveInitiator	The identifier of the entity that initiated the archiving process. For example, `15747591156 prouser_sftp_eml1@tm.com`
X-TELEMESSAGE-ArchiveMessageID	A unique identifier for the archived message. For example, `104_1722866423000_53307709215`
X-TELEMESSAGE-ArchiveSource	The source of the archived message. For example, `Network Archiver`
X-TELEMESSAGE-GROUP_NAME	The name of the group (if any) associated with this message. It is empty in this instance.
X-TELEMESSAGE-GroupID	The identifier for the group associated with this message. It is empty in this case.
X-TELEMESSAGE-MessageType	The type of message sent. For example, `SMS`
X-TELEMESSAGE-Network	The network provider associated with the message. For example, `TELEFONICA_O2`
X-TELEMESSAGE-Status	The status of the message, indicating that it has been archived. For example, `Archived` The following are some of the status that will be displayed: Success Failed Archived Missed Call Failed Call Voice Mail Rejected Call Busy Call Blocked Call Answered Externally DELETED - UNREAD DELETED - READ If you encounter any other status that you do not understand, reach out to support.
X-TELEMESSAGE-THREAD_ID	A unique identifier for the thread associated with this message. For example, `2045662248`