Email Message (EML) discovery update (Advanced Access)

Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature.

Overview

Relativity is updating the underlying engine that handles EML file discovery. The new handler improves processing performance and stability, reduces existing EML-specific limitations, and aligns EML discovery output more closely with what the native viewer displays. As part of this update, Relativity is introducing Email Hashes V2, a new hashing algorithm designed to address known limitations in the current approach.

For most customers, the transition requires no action. The exception is if your workflows use EML email hash metadata outside of standard deduplication — for example, in custom scripts, field mappings, or exports to other systems. Relativity will provide specific transition guidance for those scenarios during the Initial Rollout phase.

What's Included in This Program

During Advanced Access, you will have access to EML file discovery using the new engine on your selected workspaces, along with on-demand reports comparing metadata, extracted text, and attachments between the current and new engine. Reports are also available comparing deduplication behavior between the current hashing algorithm (V1) and the new one (V2).

Note that performance improvements will be rolled out incrementally throughout the program rather than all at once. A UI-based hash comparison option is also not part of this release.

Supporting Tools

Relativity uses three internal tools to support validation throughout the program. Reports from these tools contain only anonymized or metadata-level information — no customer content or personal data is exposed to Relativity personnel. Any access to actual source files requires explicit written consent from you.

The Parity Checker runs silently in the background during Phase A, analyzing EML files in your workspaces without affecting your data or workflows. It generates comparison reports between V1 and V2 hashing that include Workspace ID and File ID for any identified discrepancies.

The File Troubleshoot Workflow is available across all phases and allows the Relativity team to review anonymized EML file properties from both the current and new engine — with your permission. This minimizes the need to request access to source files directly.

The Hashes Migrator runs during Phase C and generates Email Hashes V2 for EML files that were processed before the migration, making them available for deduplication without requiring reprocessing.

Program Timeline

The AA program runs July 1 through September 30, 2026 across three overlapping phases. Features will be enabled dynamically at the workspace level, so scope can be expanded or rolled back quickly. Enablement on any given workspace takes up to one business day.

Phase A — Historical Data Validation (July 1–30): The Parity Checker analyzes EML files in your active workspaces in the background. There is no impact to your workflows. If discrepancies are found, Relativity may share a list of affected files and ask for structural details or sample file access to investigate.

Phase B — Dual Mode Validation (July 1–August 30): The new EML handler is enabled in selected workspaces alongside the current one. Discovery results will come from the new handler, and Email Hashes V2 will be available as a separate metadata field. You can use existing Processing deduplication workflows to compare V1 and V2 deduplication behavior directly. Dual Mode may introduce up to 20% performance degradation during this phase; Relativity will monitor and optimize continuously. Before reviewing discovery results, Relativity will ask you to run a processing job in a Dual Mode workspace to observe stability — the data can be deleted afterward.

Phase C — Initial Rollout (September 1–30): The new EML handler becomes the sole handler in selected workspaces, and Email Hashes V2 is used for deduplication. If you have custom workflows that reference email hash values, Relativity will provide specific guidance on migrating them to V2 based on your workflow details.

Throughout all phases, Relativity recommends using test data or copies of real data in early validation, with real matter data introduced as confidence builds.

Installation and Configuration

No installation or configuration is required on your end. Relativity handles all enablement and rollback within one business day of your approval. If your workflows map or export hash values to external systems and you want to use V2 hashes within them, reach out and Relativity will provide tailored instructions based on your setup.

To request disablement at any point, contact Relativity and it will be completed within one business day.

Feedback

Your feedback is the primary purpose of this program. Relativity is particularly interested in hearing about discrepancies in discovery results and how they affect your workflows, differences in deduplication behavior between V1 and V2, the clarity of hash updates during the Initial Rollout phase, and any unexpected behavior during EML discovery. You will have scheduled check-in points throughout the program to share this feedback.

For questions or issues, contact the advance access program team.