Shield Connectors

SMTP Mail Connector

Back To Connectors Page

Email Communications | Connector for SMTP Mail

Request a Demo

What Is the Shield Connector for SMTP Mail?

SMTP — Simple Mail Transfer Protocol — is the foundational internet standard governing the transmission of email across networks. Every email sent or received by a regulated financial institution, regardless of the email platform or infrastructure on which it originates, is transmitted via SMTP. Where firms operate email infrastructure that does not provide a native compliance archiving API — including legacy on-premise mail servers, non-standard email platforms, third-party mail relay services, and bespoke internal email systems — SMTP-level capture provides a universal, platform-agnostic mechanism for ingesting all outbound and inbound email traffic directly at the point of transmission.

Shield’s SMTP Mail connector captures email at the protocol level, ingesting all messages routed through the SMTP infrastructure into Shield’s compliance platform, preserving the full fidelity of every message, every attachment, every recipient, and every metadata field. From the moment data enters Shield, it is available for AI-powered surveillance, investigation, regulatory archiving, and eDiscovery, all within a single unified platform.

SMTP-level email capture is particularly relevant for regulated firms in several scenarios: firms operating legacy or non-standard email infrastructure for which no native API connector exists; firms with complex multi-platform email environments where some traffic flows outside of Microsoft Exchange or Google Workspace; firms using third-party mail relay or filtering services through which all email is routed; and firms seeking a belt-and-braces capture mechanism that ensures no email traffic falls outside the compliance archive regardless of its origin platform. Shield’s SMTP connector addresses all of these scenarios, delivering a complete email compliance record from any email infrastructure that transmits via standard SMTP.

Email remains the single highest-volume regulated communication channel at most financial institutions, and SMTP is the universal transmission standard that underpins all of it. A compliance programme that captures only named email platforms — Microsoft Exchange, Office 365, Gmail — without a protocol-level backstop may have gaps it cannot see. Shield’s SMTP connector closes those gaps.

Why SMTP Mail Compliance Is Complex

SMTP-level email capture presents compliance challenges that differ from those of platform-specific email connectors. Several issues arise consistently across regulated firms:

  • Platform heterogeneity and legacy infrastructure. Many financial institutions operate email environments that span multiple platforms, generations, and configurations — including legacy on-premise mail servers, hybrid Exchange deployments, third-party relay services, and bespoke internal systems that predate modern API-based archiving. Each platform may generate email traffic in different formats, with different metadata structures and different transmission characteristics. A single SMTP-level capture point must handle this heterogeneity consistently, preserving the full compliance record regardless of which system originated the message.
  • Metadata completeness at the protocol level. SMTP transmission generates a rich metadata layer alongside message content — including envelope headers, routing headers, message IDs, timestamps, sender and recipient addressing, relay server identifiers, and delivery status information — that is distinct from and complementary to the application-level metadata generated by email platforms. Archiving solutions that capture only application-level email data, without preserving the SMTP envelope and routing metadata, produce records that are incomplete for forensic investigation, chain of custody verification, and regulatory examination purposes.
  • Ensuring capture completeness across all mail flows. In complex email environments, not all mail traffic flows through a single capture point. Internal-to-internal messages, messages routed through multiple relay hops, and emails generated by automated systems or applications may follow different routing paths from standard user-generated email. Ensuring that the SMTP connector captures all relevant mail flows — including non-standard routing paths — requires a deployment configuration that accounts for the full complexity of the firm’s email infrastructure.
  • Deduplication and integration with platform-specific connectors. Firms that deploy SMTP capture alongside platform-specific connectors — such as the Microsoft Exchange or Office 365 connector — must ensure that the same messages are not duplicated in the compliance archive. Effective integration between SMTP-level capture and application-level connectors requires deduplication logic that correctly identifies and reconciles overlapping capture without creating gaps or inconsistencies in the unified archive.
  • Cross-channel continuity. Email communications rarely represent the complete picture of a business interaction. Correspondence that begins over email frequently continues on Bloomberg IB, Teams, or voice. Siloing SMTP-captured email away from other channels makes cross-channel investigation slow, error-prone, and structurally incomplete.

Key Features of the Shield SMTP Mail Connector

Universal Email Capture at the Protocol Level. Shield’s SMTP connector captures all email traffic routed through the SMTP infrastructure — regardless of the originating email platform, server configuration, or transmission path — ingesting full message content, file attachments, and all SMTP envelope and routing metadata. All data is ingested in full, with zero data loss, providing a complete email compliance record that is not dependent on any specific email platform’s API or export mechanism.

Full SMTP and Application-Level Metadata Preservation. Shield retains and enriches the complete metadata layer for every SMTP-captured email — including envelope headers, routing headers, message IDs, timestamps, sender and recipient addressing, relay server identifiers, delivery status information, and application-level metadata where available. This metadata is preserved in its original form, made fully searchable, and stored as part of the immutable compliance record — ensuring that investigations, chain of custody verification, regulatory examination responses, and eDiscovery productions are accurate and legally defensible.

Immutable, Audit-Ready Archive. All SMTP Mail data captured by Shield is stored in a tamper-evident, WORM-compliant archive with a complete audit trail of every access and action taken on the record. Data is indexed for rapid search and retrieval, supporting regulatory examination responses, eDiscovery requests, and internal investigations. Retention periods are fully configurable to meet jurisdiction-specific requirements — including the six-year standard under SEC Rules 17a-3 and 17a-4, the five-to-seven-year requirements under MiFID II and MAR, and the five-year requirements under CFTC Regulation 1.35.

Out-of-the-Box AI Surveillance Models. Shield ships with pre-configured AI surveillance models for SMTP-captured email, targeting behaviours including market manipulation, information leakage, MNPI sharing, front-running, conflicts of interest, and personal misconduct — calibrated to the specific language patterns of financial services email communications. Models can be customised to reflect a firm’s specific risk appetite, restricted lists, and internal policy requirements.

Deduplication and Integration with Platform-Specific Connectors. Shield’s SMTP connector includes deduplication logic that correctly identifies and reconciles messages captured at the SMTP level alongside those captured via platform-specific connectors such as Microsoft Exchange or Office 365 — ensuring that the unified compliance archive is complete without creating duplicate records that would distort surveillance outputs or inflate review volumes.

Unified Cross-Channel Surveillance. SMTP-captured email does not exist in isolation. The same employees communicating by email are also using Bloomberg IB, Microsoft Teams, Symphony, and other channels — often about the same trades, clients, and decisions. Shield ingests SMTP Mail into the same unified compliance platform as every other channel, enabling compliance teams to correlate email communications with every other source in a single workflow. This cross-channel context is essential for accurate misconduct detection and complete trade reconstruction.

Data Governance and Chain of Custody. Shield’s SMTP Mail connector preserves a complete, verifiable chain of custody from capture through archiving and retrieval. The SMTP envelope and routing metadata provides a forensically robust record of the message’s transmission path — from originating server to delivery — giving compliance officers and legal teams the confidence that SMTP-captured records are admissible, complete, and unaltered throughout their lifecycle.

Regulatory Coverage

Email communications captured via SMTP are classified as business records subject to capture, retention, and surveillance requirements across multiple regulatory frameworks. The Shield SMTP Mail connector supports compliance with:

  • SEC Rules 17a-3 and 17a-4 — requiring broker-dealers to capture, preserve, and produce records of all communications related to their business, stored in WORM-compliant, non-rewriteable format with an audit trail, for a minimum of six years.
  • FINRA Rules 4511 and 3110 — requiring member firms to archive all communications relating to their business as such — including email — with written supervisory procedures, supervision requirements, and full audit trail capability in place.
  • MiFID II Article 16(7) and Market Abuse Regulation (MAR) — requiring investment firms to record and retain electronic communications related to orders and transactions for a minimum of five years, with trade reconstruction capability within three days, and to monitor communications for indicators of insider trading, front-running, and market manipulation.
  • CFTC Regulation 1.35 and 17 CFR § 23.202 — requiring swap dealers, major swap participants, and futures commission merchants to retain records of all communications relating to commodity interests and swap transactions as part of a complete audit trail for trade reconstruction.
  • FCA Rules (SYSC 10A and MAR) — requiring FCA-regulated firms to record and retain relevant electronic communications, including email, for a minimum of five years, and to implement effective surveillance arrangements to detect and prevent market abuse.
  • GDPR and applicable data privacy regulations — Shield’s architecture supports data residency requirements and privacy-compliant data handling across jurisdictions, enabling firms with EU operations or EU data subjects to meet GDPR obligations alongside their financial services recordkeeping requirements.

Other Related Connectors

Shield’s connector portfolio spans the full range of eComms channels and trading platforms used across regulated financial institutions. All connectors feed into a single unified compliance platform — so SMTP Mail data is always reviewed in the context of every other channel your workforce uses.

Frequently Asked Questions

When should firms use the SMTP connector rather than a platform-specific email connector?

The SMTP connector is most relevant in four scenarios: firms operating legacy or non-standard email infrastructure for which no native API connector exists; firms with complex multi-platform email environments where some traffic flows outside of Microsoft Exchange, Office 365, or Google Workspace; firms using third-party mail relay or filtering services through which all email is routed; and firms seeking a protocol-level backstop to ensure no email traffic falls outside the compliance archive regardless of its origin. For firms already operating the Microsoft Exchange or Office 365 connector, the SMTP connector may be deployed as a complementary belt-and-braces mechanism to capture any residual mail flows not covered by the platform-specific connector.

Does the Shield SMTP connector handle deduplication with platform-specific email connectors?

Yes. Shield’s SMTP connector includes deduplication logic that correctly identifies and reconciles messages captured at the SMTP level alongside those captured via platform-specific connectors — ensuring that the unified compliance archive is complete without generating duplicate records. This deduplication capability is essential for firms deploying SMTP capture alongside Microsoft Exchange or Office 365 archiving.

What metadata does Shield capture from SMTP Mail?

Shield captures the complete SMTP metadata layer — including envelope headers, routing headers, message IDs, timestamps, sender and recipient addressing, relay server identifiers, and delivery status information — alongside application-level message metadata where available. The SMTP envelope and routing metadata provides a forensically robust transmission record that is distinct from and complementary to the application-level metadata captured by platform-specific connectors.

Which regulations does the Shield SMTP Mail connector help firms comply with?

The Shield SMTP Mail connector supports compliance with SEC Rules 17a-3 and 17a-4, FINRA Rules 4511 and 3110, MiFID II, Market Abuse Regulation (MAR), CFTC Regulation 1.35 and 17 CFR § 23.202, FCA SYSC 10A, and applicable data privacy regulations including GDPR — applicable to all email communications conducted in connection with regulated activity regardless of the email infrastructure through which they are transmitted.

Can SMTP-captured email be reviewed alongside other communication channels during an investigation?

Yes. Shield ingests SMTP-captured email into the same unified compliance archive as every other channel — Bloomberg IB, Teams, Symphony, voice, and mobile. Investigators can search and reconstruct the complete sequence of a business interaction across all communication types in a single workflow, regardless of which email infrastructure the messages were transmitted through.

How does the SMTP connector handle emails generated by automated systems or applications?

Automated systems — including trading systems, order management platforms, risk systems, and client-facing applications — frequently generate email communications that are transmitted via SMTP but not generated by human users. Shield’s SMTP connector captures all email traffic routed through the SMTP infrastructure, including system-generated messages, ensuring that automated communications that may be in scope as business records are captured and available for compliance review alongside human-generated email.

Related Terms