Specifications

Lotus Redbooks Wiki – IBM Lotus Notes and Domino V8.5 Deployment Guide
113
New mail template file name: type filename of new template, for example “mail85.ntf”
Ignore 200 category limit. Select “Yes”, some old releases had a limitation of opening databases with more
than 200 folders, Lotus Notes 85 has much higher limits.
Mail file to be used by IMAP mail client, check this field if you want to enable this mailfile for IMAP access.
Upgrade folder custom design – check this field if you want upgrade all folders to design of Inbox.
Prompt user before upgrading custom folders – check “Yes” if you want user to decide whether (s)he want to
upgrade folders to new Inbox design.
When user receives Mail Upgrade Notification, two buttons will appear in message. One which upgrades a
client software and the second which converts mailfile to new template.
Another option to automatically upgrade design of mail file, after client upgrade is SeamLess upgrade.
For more information, consult the Technote 1164125 – How to perform a silent upgrade by mail
(http://www.ibm.com/support/docview.wss?rs=203&uid=swg21164125
)
Seamless Mail Upgrade
Seamless mail upgrade, which uses a desktop settings document assigned to a master policy document,
only works at the time that a user upgrades his client.
In the Desktop Settings document, you can choose to upgrade the user's mail template based on the version
of the user's Notes client. After the client has completed the upgrade, it will retrieve policy settings from the
user's mail server. If it recognizes that the user has a policy document assigned to him or her that contains
the Seamless Mail Upgrade Desktop Settings document, then it will automatically upgrade the user's mail
template to the version specified in the Desktop Settings document.
Here are some possible reasons seamless mail upgrade could fail for some users:
1. The user's mail server does not contain the policy document necessary for Seamless Mail Upgrade
because either the NAMES.NSF has not been replicated or it has not been refreshed on the server.
The user's mail server could be using a cached copy of the NAMES.NSF, which does not have the
policy documents.
2. The policy document may be too restrictive as far as the organizational hierarchies are concerned.
For instance, you may have an organizational policy document for an organizational unit (OU) that