Arctera™ Insight Capture Configuration Guide
- INTRODUCTION
- DASHBOARD
- IMPORTERS
- File-Based Collector Options
- Amazon S3
- Audio Video
- BlackBerry
- Bloomberg
- Box
- CellTrust
- Chatter
- Chatter Cipher Cloud
- Cisco Webex Teams
- Citrix Workspace & ShareFile
- Dropbox Business
- Dubber Speik Recordings
- Dubber Speik SMS
- EML
- EWS
- Exchange Graph API
- FX Connect
- Google Drive
- IceChat
- JSON
- LSEG (Refinitiv)
- Microsoft Teams
- Microsoft Teams via Webhooks
- NTR-X
- OneDrive for Business
- Pivot
- Redtail Speak
- RingCentral
- ServiceNow
- SharePoint
- Slack eDiscovery
- Symphony
- Text-Delimited
- X (Twitter)
- UBS
- Web Page Capture
- Workplace from Facebook
- XIP
- XSLT/XML
- Verint
- Viva Engage (Yammer)
- Yieldbroker
- YouTube
- Zoom Chat
- Zoom Meetings
- Zoom Meetings Chats
- Zoom Meetings via Archiving API
- MONITORED USERS
- FILTERS
- TARGETS
- SETTINGS
- REPORTS
- APPENDIX
EML
The EML collector is used to process EML type files from various sources. EML format is widely used by various compliance and archiving solutions and helps the organization avoid the need to develop a specific-source parser. The collector is used for importing EML data from Symphony. Files with md5 extension should be excluded from the import, as content from Symphony is exported in a single Zip file containing EML files for each active conversation. There are some drawbacks in using EML instead of Symphony collector for processing files from Symphony. They include:
EML does not have a subject line to do conversation threading when searching.
EML has poorer look (XML to HTML looks better than EML).
EML misses information about room created, when joined, etc..