Is this article helpful?

Smarsh integration for ShareFile

Updated on Nov 19, 2026

Smarsh is an archiving and eDiscovery platform used primarily by organizations in regulated industries. The Smarsh integration captures ShareFile communications and related content in the Smarsh Enterprise Archive to support compliance, supervision, and record‑keeping requirements such as FINRA, SEC, and MiFID II mandates. For more information, see ShareFile archiving and compliance — Smarsh.

This allows organizations to continue using ShareFile for secure file sharing while maintaining an immutable record of ShareFile‑related communications for compliance and legal review.

Common use cases:

  • Financial services firms archiving ShareFile communications to meet SEC Rule 17a‑4 requirements.
  • Compliance teams monitoring file‑based communications for sensitive or regulated content.
  • Legal and audit teams performing eDiscovery across ShareFile‑related communications stored in Smarsh.

Prerequisites

Before you set up the integration, make sure you have:

  • A ShareFile plan that supports Archiving.
  • A dedicated user configured by ShareFile Support as the email archiving administrator.
  • A custom SMTP server and a journal mailbox configured to capture ShareFile-generated email.
  • An active Smarsh account and a Smarsh administrator who can configure the ShareFile channel.

Note:

Archiving cannot be turned off after it is enabled and may affect the actions available in your account. Contact ShareFile Support to confirm your plan and review the impact before enabling it.

Set up the integration

Enabling the Smarsh integration requires configuration steps across ShareFile, email infrastructure, and Smarsh:

  • The ShareFile account must support and have Archiving enabled.
  • A dedicated service user must be created and designated as the email archiving administrator by contacting ShareFile Support.
  • ShareFile must be configured to use a custom SMTP server so ShareFile‑generated emails are journaled within Smarsh.
  • The Smarsh administrator must authorize and configure the ShareFile channel within the Smarsh platform.

Known limitations

  • Smarsh ingestion is limited to 2 GB per attachment due to Outlook and journaling constraints. When an attachment exceeds this limit, Smarsh may index the message without archiving the attachment.
  • Most integration issues are related to initial configuration (SMTP, journaling, service user setup).
  • Mail server restrictions (trusted IP policies) can prevent Smarsh from receiving ShareFile emails.
  • Search or indexing issues typically originate on the Smarsh side rather than within ShareFile.
In this article
PrerequisitesSet up the integrationKnown limitations