You can go the opposite way. This need some handwork and provides only a snapshot, but it works.
Create a batchfile with one entry for every DAOS enabled database:
“C:\Program Files\IBM\Domino\nserver.exe” -c “tell daosmgr listnlo -o output_mailfile1.txt ALL mail/mailfile1.nsf”
“C:\Program Files\IBM\Domino\nserver.exe” -c “tell daosmgr listnlo -o output_mailfile2.txt ALL mail/mailfile2.nsf”
Run batch
Do a text search for the required nlo file over all the created output_*.txt files
Subject: re How to determine whether or not a nlo is really active
FYI …
NLO’s are cleaned up (deleted) by the DAOS Prune process that is scheduled to run nightly at 2:00 AM. NLO’s are only removed when the DAOS catalog is in a ‘Synchronized’ state, the NLO refcount is zero, and the NLO was marked deleted longer than the prune interval ago…
For listing which .nlo’s are used for a specific database using the following command:
Subject: How to determine whether or not a nlo is really active
I guess I can see where there may be some possible security ramifications of not exposing whom has such large attachments but I’d also like the ability, as an administrator, if I need to start restricting the size of attachments who am I most likely to start affecting. And other legitimate administrator concerns. Perhaps “leaning” on some people as to whether or not they need such stuff.