Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Needs Review
Workspace Domino
Categories General
Created by Guest
Created on Jul 21, 2023

Disable rename users by adminp on archives for Government(s) use

Some departments of some governments treats the archives as static archives. Deletions and renames are not allowed, because of the fact that your name was static on the date/time when you received or wrote an email or meeting.


If you change your name from User-A/ORG to User-B/ORG...that's from the date and time you started/requested the rename. Your name was not User-B/ORG 2 years ago.

The rename in your live mailbox is no problem, because governments mostly have a strict archive policy: 3 months or less.


Therefor we need a way to tell adminp to leave the archives as they are. Compact -A moves the ACL to the archive database, even the Advanced ACL properties ( when the ACL of the mailfile changes ). Therefor the archives gets the Administration Server of the maildatabase, and mostly that's wrong. We don't have archives on the mailserver, but on a seperated mailserver.


HCL please accomplish 2 things:


1) Let compact -a only change the ACL, and leave the Advanced properties alone.

2) Don't delete and rename users by adminp ( deletions are solved by notes.ini parameter )

  • Attach files
  • Guest
    Reply
    |
    Aug 23, 2023

    Updating the ACL afterwards can be done, but should not be the case. Compact -A should leave the Advanced ACL alone on the Archive server.

  • Guest
    Reply
    |
    Aug 23, 2023

    @Thomas: Yes, that should be doing the trick....but every time when I perform a compact -a, and when the ACL on the maildatabase has changed, the entire ACL on the archivedatabase is overwritten with the one from the maildatabase.


  • Admin
    Thomas Hampel
    Reply
    |
    Aug 22, 2023

    Changing ACL settings to not modify name fields (under Advanced) is not an option?
    //Edit: e.g. running an agent after compact -a , that will update the ACL again?