TeleMessage Recording is a next generation instant messaging solution that captures text messages and attachments sent and received on any mobile device via WhatsApp, WeChat/WeCom and TeleMessage Native Applications for iPhone and Android.
...
For a general description of Verba Import sources, please refer to Import sources.
| Info |
|---|
Effective October 1, 2022, Microsoft began disabling Basic authentication for Outlook, EWS, RPS, POP, IMAP, and EAS protocols in Exchange Online. This means that for TeleMessage import sources using Exchange will no longer work with simple username and password authentication, instead OAuth 2.0 authentication must be used. Read this page on how to set up OAuth 2.0 for Exchange Online: Microsoft Exchange IMAP configuration with OAuth 2.0 |
Creating a TeleMessage import source with OAuth 2.0
Follow the steps below to create a new Verba Import source for TeleMessage TeleMessage. Before creating the Import source, an application must be registered in Azure.
Step 1 - Open the Verba Web interface then select Data > Import Sources from the top menu
Step 2 - Click on the Add New Import Source link on the top right
Step 3 - Complete the configuration according to the requirements in the following table
| Configuration Item | Description |
|---|---|
| IMAP Server | e-Mail account receiving TeleMessage data Server address format should be: <hostname or ip>:<port number> Note: The e-Mail account receiving TeleMessage data must have the TeleMessage e-Mail server IP addresses and sender account whitelisted |
| IMAP Username | e-Mail account username |
| Authentication Mode | Basic* / OAuth 2.0 (*not supported by Exchange Online) |
| Application (Client) ID | Client ID for application registered in Azure |
| Application (Client) Secret | A valid client secret for application registered in Azure |
| Directory (Tenant) ID | Tenant ID for the account |
| Forward Proxy Address | Proxy configuration (optional). |
| Forward Proxy Port | Proxy configuration (optional). |
| Forward Proxy User | Proxy configuration (optional). |
| Forward Proxy Password | Proxy configuration (optional). |
| TLS Certificate File | Certificate file / certificate thumbprint used for the IMAP connection. |
| TLS Key File | File system location where the certificate key is stored. |
| TLS Key Password | Specify the password for the file that contains the certificate keys. |
| CA Certificate Chain File | Certificate chain (or Chain of Trust) is made up of a list of certificates that start from a server's certificate and terminate with the root certificate. If your server's certificate is to be trusted, its signature has to be traceable back to its root CA. |
| Use TLS | Tick to use TLS between the e-Mail account receiving TeleMessage data and Verba. |
Step 4 - Click Save to save the settings
Creating a TeleMessage import source with username and password
Basic authentication no longer works for Microsoft Exchange Online mailboxes. VFC cannot login with username and password as an application. Please setup client application in Azure and use OAuth 2.0 authentication (see previous section).
Follow the steps below to create a new Verba Import source for TeleMessage:
Step 1 - Open the Verba Web interface then select Data > Import Sources from the top menu
...
| Configuration Item | Description |
|---|---|
| IMAP Server | e-Mail account receiving TeleMessage data Server address format should be: <hostname or ip>:<port number> Note: The e-Mail account receiving TeleMessage data must have the TeleMessage e-Mail server IP addresses and sender account whitelisted |
| IMAP Username | e-Mail account username |
| IMAP Password | e-Mail account password |
| TLS Certificate File | Certificate file / certificate thumbprint used for the IMAP connection. |
| TLS Key File | File system location where the certificate key is stored. |
| TLS Key Password | Specify the password for the file that contains the certificate keys. |
| CA Certificate Chain File | Certificate chain (or Chain of Trust) is made up of a list of certificates that start from a server's certificate and terminate with the root certificate. If your server's certificate is to be trusted, its signature has to be traceable back to its root CA. |
| Use TLS | Tick to use TLS between the e-Mail account receiving TeleMessage data and Verba. |
...
Step 4 - Click Save to save the settings
TeleMessage e-Mail Formatting
The TeleMessage Import Source requires particular e-Mail formats. If e-Mails are not received directly from TeleMessage, ensure the e-Mail provider configures a message passthrough policy to avoid changing the e-Mail format. For example:
Map TeleMessage Users to Verba Users
...