Focus: Archiving with iQ.Suite Safe

1. How and where do I set rights for the Safe database (mailsafe.nsf)?
2. How do I avoid "space problems" on my server?
3. How does matching the Safe database work in a cluster?
4. How should I encrypt my Safe database?
5. What is used to sign the Safe database?
6. How and where is a DXL archive file created?

How and where do I set rights for the Safe database (mailsafe.nsf)?

The rights for the Safe database are set in the database itself (see sample database in the standard configuration), not in the database template.
Exercise great care when assigning access rights to this database, as it provides access to the entire mail traffic.

How do I avoid "space problems" on my server?

Safe provides various options for recreating the Safe database according to the e-mail volume. Experience shows that creating a new database on a weekly basis is a reasonable setting. With such a limited period of time, access to archived e-mails is relatively easy. For higher e-mail traffic, you may also set a maximum size, e.g. 650 MB, of the database.
Once completed, databases can be saved on CD ROMs to provide additional disk space.

How does matching the Safe database work in a cluster?

A mailsafe.nsf is created on each of the servers. When the databases are matched, the database with the lowest Replicate ID has the highest priority.

How should I encrypt my Safe database?

A key is created with the User ID or Server ID. The key created with the Server ID is exported for all users having access to the Safe database. The name of the key matching the Server ID has to be specified in the Safe job.

What is used to sign the Safe database?

The Server ID is always used to sign the Safe database.

How and where is a DXL archive file created?

The creation of a DXL archive file is selected in the settings for a Safe job in iQ.Suite. To do so, select DXL Export under "New database" in the "Operations" tab.
The archive path is set in the "Advanced" tab.