Today when enable an archive criteria for a mail database we have only 2 options:
Domino person record needs to contain the location (or replica ID) of the user's primary mail archive.
We need to think of a user's mail file and archive as connected facets of the user mail experience. Right now in most domino shops, the person record contains their mail file location, roaming profile database location, public key, sync'd password for sametime/inotes, even businesscard picture. One thing that's missing from the ...
Currently with Policies they are applied based on OU or explicitly. Further, for archive policies, you can choose either a specific archive server, or choose to archive to the home mail server.
This is not flexible enough if you have many users in the same OU spread across 2 or more ...
Typically, there exist databases which have high informational value but long, even medium term retention may not be desirable.
What I'm proposing is for templated databases to be automatically deleted and re-created on a configured interval.
The typical scenario is databases like domlog.nsf, which provides invaluable insight into ...