Extend the principles a little further
The mail domain that person records are in could be specified on a dialog, or we could check the mail domain on the person record against the maildomain on their specified mail server and see if they're the same.

Make an assumption
We could also assume that the user who runs the code is the one who should be emailed the resulting report, again removing the need for code changes.

Make verbose and condensed versions
You could make verbose and condensed versions. The condensed version would only report severity 1 items, for example, and would save output by skipping reporting users where no problems were found. This would make it easier to concentrate on things that need to be fixed. If we have a dialog to specify options, this would be one of them.

Add error-handling code
As it stands, there's no error-handling code, so if there were problems outside of the code's ability to cope, it would die at that point and not report anything. A simpler method might be to save the report document in the database as we go along, maybe after each person record is checked, so that the incomplete report could be retrieved if it does fail.

Put the code in a script library
You might want to put the code in a script library and break it up into smaller procedures. I nearly did some of this for this article because it might have made it easier to explain. However, I resisted. Doing this would make the code easier to restructure for the future and make it easier to reuse bits of the code.

Lastly, I have a question. I've written other pieces of code like this that check issues in a Domino infrastructure, particularly to do with mail. Examples are code that checks that mail databases actually exist where the directory says they exist, checks of mail database ACLs for standards compliance, checks that mail databases that reside on a clustered server also reside on another server in the cluster, and so on. Tell me, via the Powerboards or email me at mick_moignard@unipart.co.uk, whether these would be of interest to you as future articles.

Mick Moignard has been working and traveling with Notes since Release 2.0 in 1991. He is a Principal CLP with Unipart Advanced Learning Systems, a Lotus Advanced Partner in the UK. If you want a copy of the code discussed in this article, or want to discuss anything to do with this article, or indeed anything else to do with Notes and Domino, email Mick at mick_moignard@unipart.co.uk. UALS, at http://www.uals.co.uk, will also happily discuss any Notes and Domino application development opportunities or infrastructure projects with which you need help.