This section explains the values of regular email headers and the unique TeleMessage X-headers used in delivering mobile communications.
The table below provides details on SMTP headers and unique Capture Mobile X-headers:
Field | Description | Example | Notes |
Return-Path | Email address of the Capture Mobile archive system. | Capture Mobile Archive Return Path <ndr@archive.telemessage.com> | |
Date | The actual time when the original message was sent, in long date format, using the UTC (GMT) time zone. | Sun, 12 Feb 2017 16:33:55 +0000 (UTC) | This entry represents the time the original message was sent.
|
RCPT TO | The archiving email destination refers to the address used to send emails for the company whose messages are being archived by the vendor. | Company_or_user@archive.vendor.com
| This is the SMTP Delivered-To field, which is generated automatically. It may represent the specific archiving email for an individual user or a central archiving address for the entire company's archival vault. |
MAIL FROM | Capture Mobile system central email archiving address. | This is the actual email address from which the messages are sent. | |
To | For registered employees under the same company admin, the format is:
Otherwise, the following format is used: | Registered users: Temp user:
| This is included in the MIME SMTP headers in the body (not the actual destination) to indicate the recipient of the original mobile message. |
From | The same as the To field. | The same as the To field. | This is the SMTP MIME header in the body (not the actual destination) used to indicate the sender of the original mobile message. |
Subject | P2P:
WhatsApp/WeChat: P2P:
Chat Group:
Broadcast Group:
Groups: Chat Group Message:
Voice Calls:
Conference Calls:
| SMS - " WhatsApp - | |
Sender | Applicable only for Generic SMTP: This is the Capture Mobile Mail relay used for sending emails. It should not be confused with the 'From' field. | Targeted to bypass SPAM filter. | |
Content-Transfer-Encoding | Email encoding type. | 8BIT 7BIT | The default setting is 8BIT. |
X-TELEMESSAGE-MessageType | Delivery channel of the archived item | SMS – actual SMS MMS – actual MMS APP Message- WhatsApp, other IM and ENA/Secure Messaging IP messages. Call Log – established calls without recording or unanswered calls Voice Call – established calls with recording including incoming voicemail. FAX Video Call | Use APP Message for WhatsApp messages. |
X-TELEMESSAGE-Status | For text messages, archiving is always done under Status updates such as Delivered or Read are not archived. However, Non-Delivery Reports (NDRs) are archived for specific messages. For calls, archiving occurs at the end of the call. | All message types, except for voice calls and call logs, are archived as 'Sent' or with an NDR status. Voice calls and call logs are archived with a status based on one of the eight defined call status values. | Status updates such as Delivered and Read are not archived. However, Non-Delivery Reports (NDRs) are archived for certain messages. |
X-TELEMESSAGE-ArchiveMessageID | A unique message identification of this message in the Capture Mobile Archive system | 531050683 | Running unique number |
X-TELEMESSAGE-Network | The network operator from which the message originated, applicable only for the Network Carrier Capture. | Verizon Telefonica O2 | |
X-TELEMESSAGE-ArchiveSource | The source from which the message arrived in Capture Mobile:
| Enterprise Number Capture | Based on channel source or product used |
X-TELEMESSAGE-GroupName | The name of the chat group to which the message was sent. Applicable to chat groups, broadcast groups, and MMS groups. | App Message from A to Sales chat group | NULL for the all other scenarios and interfaces |
X-TELEMESSAGE-GroupID | Unique ID of the group. Applicable to chat groups, broadcast groups, and MMS groups. | 54357 | |
X-TELEMESSAGE-ThreadName | EMPTY | ||
X-TELEMESSAGE-Thread_ID | The ID of the thread, created by hashing all participant and sender mobile numbers. | 645623432 | Identical for all groups with the same participants, unlike the Group ID, which is unique. |
X-TELEMESSAGE-ArchiveInitiator | Identical to To. Must be a registered user with an archive plan. | 17819988776 <sam@supernova.com> | On behalf of which user the item is archived in the case of multiple entries for an archived item, through sender and recipient(s). |
X-TELEMESSAGE-Thread-Index | 27-character hash code created from the participants list, similar to ThreadID. | 000000000000000000563284207 | Microsoft standard for aggregating email threads. Base64 representation of X-TELEMESSAGE-Thread_ID. |
Body | The full text and attachments exchanged in the mobile call, text, or chat. | Let us know if you need any other combination or content. |