MAIL


Setting up the Mail Journaling database
By default, mail journaling is not enabled. You enable journaling from the Configuration Settings document. To set up the Mail Journaling database, you specify where to store journaled messages and then set options for managing the security and size of the database.

After you enable journaling, IBM® Lotus® Domino® automatically creates the Mail Journaling database in the specified location.

To set up the Mail Journaling database
1. Make sure you already have a Configuration Settings document for the server(s) to be configured.

2. From the Domino Administrator, click the Configuration tab and expand the Messaging section.

3. Click Configurations.

4. Select the Configuration Settings document for the mail server or servers where you want to journal mail, and click Edit Configuration.

5. Click the Router/SMTP - Advanced - Journaling tab.

6. Complete the following fields, and then click Save & Close:
FieldDescription
JournalingSpecifies whether the server supports mail journaling. Choose one:
  • Enabled - Domino supports mail journaling on the servers governed by this document. To journal mail, create a server mail rule with the action "Journal this message."
  • Disabled - (default) Mail journaling is not supported on the servers governed by this document.
Field encryption exclusion listSpecifies the names of Notes message fields that Domino does not encrypt when adding messages to the Mail Journaling database. Encrypted fields cannot be displayed in a view. List any fields you want to display in a view. By default, the following fields are not encrypted: Form, From, Principal, and PostedDate.

Note When using a mail-in database for journaling, Domino does not automatically encrypt messages added to the database. To encrypt messages in a mail-in database use the Mail-in database document to specify encryption of incoming messages.

MethodSpecifies the location of the Mail Journaling database. Choose one:
  • Copy to local database - (default) The Router copies each journaled message to a database on the local server. If it does not already exist, Domino creates a local Mail Journaling database on the server. If the Configuration Settings document applies to multiple servers, Domino creates a unique Mail Journaling database on each server.
  • Send to mail-in database - The Router copies each journaled message and sends it to a specified mail-in database. The specified database must already exist and must have a Mail-in database document in the Domino Directory. The mail-in database used for journaling may be on any Domino server, including the local server. Specify the mail file where journaled messages are to be sent in the Mail Destination field. When using a mail-in database for journaling, be sure to encrypt messages when adding them to the database. To encrypt messages sent to a mail-in database, enable encryption on the Administration tab of the Mail-in database document.
Database nameIf you specified "Copy to local database" as the journaling method, specify the file name you want Domino to use when it creates the Mail Journaling database. The default name is MAILJRN.NSF.
Mail destinationIf you specified "Send to mail-in database" as the journaling method, use this field to enter the name of the mail-in database to which the Router forwards messages to be journaled.

Click the down-arrow to select the name of the mail-in database from the Domino Directory.

Note You must create the mail-in database beforehand; Domino does not automatically create mail-in databases for journaling.

Encrypt on behalf of userIf you specified "Copy to local database" as the journaling method, enter the fully qualified Notes Name of the user whose certified public key Domino uses to encrypt messages added to the database. To ensure privacy, consider creating a special user ID for reviewing journaled messages, and protect the ID with multiple passwords.

To encrypt messages sent to a mail-in database, enable encryption on the Administration tab of the Mail-in database document.

Database Management - MethodFor local Mail Journaling databases, the entry in this field specifies how Domino controls the size of the Mail Journaling database. When the database management method in effect calls for Domino to create a new Mail Journaling database, on the day that it creates the new database, it does so at approximately 12:00 AM. Choose one of the following methods:
  • Periodic Rollover - (default) When the current Mail journaling database reaches the age specified in the Periodicity field, Domino renames the existing Mail Journaling database and creates a new Mail Journaling database with the original name.
  • None - Domino does not automatically control the size of the Mail Journaling database. If you do not use one of the available methods for controlling database size automatically, be sure to monitor the database size and use appropriate tools to archive the journal data.
  • Purge/Compact - Domino deletes documents from the database after the number of days specified in the Data Retention field and then compacts the database.
  • Size Rollover - When the current database reaches the size specified in the Maximum size field, Domino renames the database and creates a new Mail Journaling database with the original name.
PeriodicityIf you specified Periodic Rollover in the preceding field, Domino displays this field for specifying the length, in days, of the rollover interval. The default value is 1 day.
Data RetentionIf you specified Purge/Compact in the Database Management-Method field, Domino displays this field for specifying the time, in days, that a message remains in the Mail Journaling database before being deleted.
Maximum sizeIf you specified Size Rollover in the Database Management-Method field, Domino displays this field for specifying a size limit, in megabytes (MB), for the Mail journaling database. After the database reaches the specified size, Domino renames it and creates a new one.
7. The change takes effect after the next Router configuration update. To put the new setting into effect immediately, reload the routing configuration.

Related topics