Notes.ini Entry - CacheMail

Notes.ini Entry

Name:	CacheMail
Syntax	CacheMail=Value
Applies to:	Workstations
Add-on:
First Release:	8.5.2
Obsolete since:
Category:	Managed Replica
Default:	None
UI equivalent:	None

Description:
If you've ever wished using Mail were free of delays, but don't have the mind space for creating and maintaining a local replica, the new managed replica feature might be for you. When you create or convert an existing local replica to a managed replica in Notes, or your Domino administrator sets it for you via a policy, Notes creates a local mail replica and marks it as a managed replica. The next time you open Mail, you'll be using the managed replica, which will remain synched with the server copy without your doing anything.

Valid (known) Values are (They look like a Binary number):
1 - (0001 binary) Create a local replica of the user's mail file. If a local managed replica exists, convert it to a standard local replica.
3 - (0011 binary) Create a local managed replica of the user's mail file. If a local replica already exists, do nothing.
7 - (0111 binary) Create a local managed replica of the user's mail file. If a local replica already exists, convert it to a managed replica.
8 - (1000 binary) Delete the local replica of the user's mail file (managed or not).

A managed replica differs from a local replica in the following ways:

* It is created in the background while the user continues to use the server copy.
* The managed replica can be limited to the last N days of mail/calendar entries if local space is a consideration.
* Initial creation of a managed replica is controlled to minimize impact to server of multiple users/clients creating managed replicas.
* After creation, the user is automatically switched to the managed replica.
* If the managed replica needs to be fixed up, the fixup will occur in the background and the user will be redirected to their server copy.
* If the managed replica becomes corrupt, it will be deleted and recreated.
* To speed up initial creation of the managed replica, documents beyond 30 days are initially truncated bringing down part of the document and omitting attachments.
* New mail polling and notification is performed against the server copy.

In conjunction with a managed replica, there are additional settings that complete the managed replica experience:

* If the user opens a truncated document, the rest of the document and/or attachments can be retrieved in the background.
* All mail sends will route immediately through the local mail.box to avoid any delays sending mail messages and attachments.

To set your Mail to be a managed replica (if your Domino administrator has not set the policy for you), do the following:

1. Make sure that you have enough disk space (the size of your mail application plus its full-text index, plus 1GB).
2. If you want the cache to have a full-text index, either create one now in your server-based mail application (File > Application > Properties, Full Text ) or set the default settings for local replicas to create a full text index for faster searching either in the NOTES.INI file or using Domino policy.
3. Close Lotus Notes.
4. Set the following variables in the NOTES.INI file or enable using Domino desktop policy settings available with release 8.5.2.
* CacheMail=7 – creates or converts a local mail replica to a managed replica
* ReplicateOnNewMail=1 – when the client learns of new mail, it triggers a replication
* DocAutoRetrieve=1 – if a document is truncated, the client automatically gets the rest of the document, minus attachments, when the document is opened – double click on the attachment icon(s) in the email to fetch the attachments
* OutgoingMailSendThreshold=1 – forces Notes to route mail through the local mail.box (improves performance)
5. Ensure that you have the desired replication schedule.

A replication schedule is enabled automatically if not otherwise set. By default, a managed replica is flagged as high priority. The high priority replication schedule is hourly.

If you're an administrator you can set a replication schedule using Domino policy. Otherwise you can click File > Preferences > Replication and Synch to specify a replication schedule.
6. Ensure that the location documents specify to use a server-based mail file, and that the path in the location is correct. Note: The client will automatically managed the use of the local/managed replica, as opposed to the server replica, based on the current state of the managed replica.
7. Open Lotus Notes.
8. After a short interval, the client will create the managed replica and begin replicating its contents. Note: If there is a problem, it will be reported in the log files.

You can work in Lotus Notes mail while Notes is building the managed replica. Once the managed replica has been built (replication completes and the views are built), it will be switched to at the next opportune time. You do not need to close Notes to switch to the managed replica. If Notes has a problem with the managed replica, you are directed to the server copy, and the managed replica is rebuilt.

Initially, the cache contains full copies of the last 30 days of mail. Large document that are older than 30 days and documents with attachments may be truncated. When you open a truncated document, the full document (no attachments) is retrieved in background.

To revert to using server-based Lotus Notes mail, do one of the following:

* Specify the NOTES.INI setting CacheMail=1 to specify an unmanaged replica.
* Change the Domino policy to specify creation of a local replica.

An administrator can control how many managed replicas are created concurrently. By default, the client will allow at most 25 concurrent managed replica creations against any given server. For finer control, an administrator can make the following changes:

1. Enable the "Smart Upgrade Governor" on the Server configuration document.
2. Set the number of simultaneous Smart Upgrade downloads to a desired value.

Note: Initial managed replica creation will not exceed 90% of this value.

Note: The Smart Upgrade Governor is used to support existing servers. Enabling the governor does not require the use of Smart Upgrade, it just facilitates a mechanism for multiple clients to coordinate impact and load against a given server.