Archiving mail from SMTP/IMAP mail servers to Vaultastic

Overview

Many organizations operate self-hosted or third-party mail servers that use:

• SMTP (Simple Mail Transfer Protocol) for mail delivery

• IMAP (Internet Message Access Protocol) for mailbox access

These environments may include:

• On-premises mail servers

• Hosted private mail platforms

• Legacy enterprise messaging systems

• Application mail relays

Email data within these systems represents critical business records and must often be archived for:

• Regulatory compliance

• Legal hold and eDiscovery

• Supervisory review

• Business continuity

Vaultastic enables ingestion and preservation of this data into tiered storage optimized for:

• Access frequency
• Retention duration
• Storage cost

Vaultastic Storage Tiers

Vaultastic organizes archived email data into purpose-built storage tiers.

Email data can be archived using:

• Live mail capture
• Historical mailbox ingestion.

Email Ingestion Overview

The following table summarizes supported ingestion methods for SMTP and IMAP mail servers.

Live Email Archival

Vaultastic supports real-time capture of email transactions from SMTP mail servers.

Server Forwarding Configuration

To ensure continuous archival of live mail traffic:

1. Configure server-side forwarding, journaling, or BCC rules.

2. Route a copy of inbound and outbound messages to the Vaultastic ingestion endpoint.

3. Apply rules at

   • Organization level (recommended)

   • Domain level

   • User level (selected users if required)

Supported forwarding mechanisms vary by mail server and may include:

• SMTP journaling

• Global BCC rules

• Transport rules

• Archive mailbox routing

Note: Organization-wide journaling is recommended to avoid gaps.

Mail Flow Architecture

Typical Flow:

1. Email is sent or received via SMTP.

2. The mail server generates a copy using forwarding or journaling rules.

3. The copied message is delivered to Vaultastic.

4. Vaultastic indexes and stores the message in Active Store.

Benefits of this approach include:

• Real-time capture

• No dependency on users

• No archival gaps

• Immediate search availability

This configuration is typically performed once at the mail server level.

Historical Mailbox Archival

Email already stored in mailboxes can be archived using Data Upload application with IMAP connectivity.

IMAP-Based Mailbox Ingestion

Existing mailbox data is archived using the Data Upload Application (IMAP ingestion).

IMAP-Based Mailbox Ingestion

Workflow:

1. Data Upload connects to the mail server via IMAP
2. Authentication using a user or service account
3. Mailbox data is fetched
4. Data is uploaded to the selected Vaultastic store

Supported ingestion modes:

• Full mailbox ingestion
• Date-range-based ingestion
• Selected users or domain-wide ingestion
• Scheduled synchronization

Selecting the Storage Destination

Mailbox data can be archived into different Vaultastic stores depending on the use case.

Data in Open/Deep Store can be moved to Active Store when needed.

Archiving Exported Mail Files

If email is already exported, upload directly to Vaultastic.

Supported formats:

• PST
• EML
• MBOX

Recommended usage:

• Open Store → searchable archive
• Deep Store → long-term retention
• Active Store → active investigation or review

Data archived in Open or Deep Store can later be activated into Active Store if needed.

Why Archive SMTP/IMAP Mail Servers

Regulatory Compliance

Many regulations require organizations to retain communication records with:

• Immutable storage

• Audit trail integrity

• Defensible eDiscovery capability

Legacy or self-hosted mail servers typically lack built-in compliant archival mechanisms.

Risk Mitigation

Self-hosted mail environments face risks such as:

• Hardware failure

• Ransomware attacks

• Accidental deletion

• Insider manipulation

Vaultastic provides durable and isolated archival storage independent of the production mail server.

Operational Continuity

If the primary mail server:

• Fails

• Is migrated

• Is replaced

• Is decommissioned

Archived content remains accessible and searchable in Vaultastic.

Initial Configuration

Follow these steps to configure SMTP / IMAP mail server archival.

1. Define Archival Scope

Identify:

• Users/domains to archive
• Retention policy
• Target storage tier
• Mail server capabilities

2. Configure SMTP Forwarding

• Enable journaling/BCC/transport rules
• Route to Vaultastic ingestion endpoint
• Validate ingestion

This ensures forward-looking coverage

3. Configure IMAP Access

Enable IMAP and collect:

• IMAP host
• Port
• Encryption (SSL/TLS)
• Credentials

Recommendation:
Use a dedicated service account with read-only access

4. Run Historical Mailbox Ingestion

Using Data Upload:

• Perform full or filtered ingestion
• Validate indexing and completeness

5. Configure Ongoing Synchronization (Optional)

• Schedule IMAP sync jobs
• Capture missed or delayed messages
• Monitor via Data Upload dashboard

Recommended Implementation Sequence

A typical deployment follows this sequence:

1. Configure SMTP forwarding to capture live mail flow.

2. Validate Live Ingestion into the Active Store.

3. Configure IMAP connectivity in Data Upload.

4. Run historical mailbox ingestion.

5. Enable incremental synchronization if required.

6. Validate search, indexing, and retention policies.

Benefits of SMTP / IMAP Archival with Vaultastic

Archiving SMTP and IMAP mail servers into Vaultastic provides:

• Continuous capture of live communications

• Complete historical email coverage

• Protection against mail server failures

• Regulatory compliance readiness

• Centralized supervision and auditing

By combining SMTP-based live capture with IMAP-based historical ingestion, organizations achieve comprehensive and defensible email preservation across legacy and modern mail infrastructures.

Security and Access Control

• Use TLS encryption for SMTP and IMAP
• Restrict ingestion endpoint access (IP allowlisting if supported)
• Use least-privilege service accounts
• Rotate credentials periodically
• Audit ingestion and access logs regularly

Validation and Monitoring

After configuration:

Validate:

• Test emails are archived
• Mail count matches source mailbox
• Attachments are preserved
• Metadata (sender, recipient, timestamps) is intact

Monitor:

• Ingestion logs
• Failed messages
• IMAP sync status
• Storage growth

Final Notes

• Always enable SMTP journaling first to prevent data gaps
• Use IMAP ingestion only for historical backfill and sync
• Validate ingestion before moving to the next step