This article explains how to configure a generic email system (e.g., Linux-based mail servers, Keri, or other MTAs) to journal emails to a cloud-based journaling recipient address provided by your archiving service.

Requirements
Before starting, ensure you have the following:

• ✅ Admin access to your mail server or MTA (Postfix, Sendmail, Exim, Keri, etc.)
• ✅ The Cloud Journaling Recipient Address (provided by Jatheon Tech Support)
• ✅ TLS support enabled on the mail server (recommended)
• ✅ Outbound internet access on port 25 (SMTP), 465, or 587

General Configuration Steps

Step 1: Identify Your Journaling Method

Most MTAs support journaling using BCC rules, aliases, or custom transport rules. Select the method that best fits your system.

Common journaling methods:

• BCC all outbound/inbound email to journaling address
• Use aliases to forward messages
• Use system filters or hooks to redirect a copy of each message

Step 2: Configure the Mail Server

Step 3: Test the Setup

• Send a test email and confirm that:
• The message arrives at its original destination
• A copy of the message is successfully delivered to the Cloud Journaling Recipient
• The journaling system (e.g., Jatheon Cloud) receives and archives the message
• If errors occur, check mail logs (e.g., /var/log/maillog, /var/log/mail.log) for delivery or TLS issues.

Notes
Do not use distribution lists for journaling—only journal to a dedicated, secure recipient.

The journaling recipient should not auto-reply or bounce messages.

For large mail volumes, ensure your mail server handles high-throughput queuing and retry logic.

Support
If you need help configuring your journaling setup, contact our support team with:

• Your server type (e.g., Postfix, Keri, Exim)
• Sample message headers
• Any error logs
• We’re happy to help verify your journaling flow.