Look at security policies. You can set the password complexity rules to match minimum length, number of capitals & digits etc. in the Custom Password Policy section.

I use All Documents instead. The Folder column shows which folder(s) the message is in so I don't need to go fishing to find it.

I agree with Bill. If you want by sender, click the Who column header - size, click Size etc
Adding views to a database adds performance overhead and additional index processing, and that means slower responses, particularly in larger Inboxes/databases.

I've always recommended using Bcc for recipients when sending notices to an enterprise for two reasons - messages are smaller (the complete recipient list isn't stored in each message) and to prevent Reply to All from being used.

I still believe the messages are valid and should be issued, as are the ones issued for mail databases for users that are no longer in the NAB.
As for checking user configuration - I'd go to the NAB for verifying the use of forwarding. It's a lot easier to use a view in the NAB than search the logs.

Can you not use DDM/events to suppress the messages in your environment?

You are prompted to confirm a database deletion in the client. If that's not enough you should have a backup available.
My problem with the Recycle bin is when do you empty it? There's no option like soft deletions to say keep it for x days, and you can't expect admins to go in and remove items based on their age from the bins on each server. The only option available is to restrict the size of the bin so the more you delete, the less they last in the bin . . . .
I think the architecture of Notes/Domino allows for enough protections already, particularly if you consider backups, that we don't need yet another data repository to worry about. If you let users know that you can bail them out, they're not going to think about the implications of deleting things so all this will do is increase your workload, not reduce it.
As for @27 comments about corporate issues - I hope you're joking. The larger the environment, the less access Domino Admins get to the OS of the servers that Domino runs on.

There's probably a better way to deal with this than bombarding IBM with NSDs from our environments. I think the reason they make it "inconvenient" to upload diagnostic data is so that they don't get overloaded with irrelevant information or have too much data to process.
I think adding an option to the Fault Reporting database to interact with IBM support would go a long way to making things easier for all, in conjunction with LND (see below).
@4, 5 - there is a tool to locally diagnose NSD - Lotus Notes Diagnostic. In many cases it will save a call to IBM, and will also help you identify the similarities between crashes on multiple servers.

Control access to the id files - that's how you prevent it.

Discussed this today and was going to post this as an idea.

notes.ini variable - poll_remote_mailfile=1
{ Link }

Chris,
Just because you can do it with M$ products doesn't mean every product should do it. As has already been mentioned, meeting attendance should be controlled by the Chair - Wiki style attendance can be an nightmare, particularly when attendees are not expected or the room capacity cannot handle the numbers.
I would suggest however that a "request to add attendee" option that sends the information to the chair may be a suitable middle ground. Allows for additional attendance, but with the control still staying with the Chair.

@4 Just because you haven't delegated in 15 years doesn't mean it isn't used. Try it some time - it's nice to have someone else work for you now and again :-)

As a QB user, I'd have to say it would be nice, but I think this is something Intuit would have to provide as much as IBM. Their integration with email clients is non-existent.

Local replica?

Can be controlled with script if needs be, but I would agree a policy option would be beneficial. For those of us who have performed migrations TO Notes/Domino, this option would be invaluable.

A move involves creation of a new replica and deletion of the old one (IIRC) - more steps than is really needed when just renaming a database on the same server

Given that in most cases purged deletion stubs are the root cause of many documents reappearing in DBs in situations like this, perhaps an option could be added to space savers in Replication Settings to permit/prohibit replication when the gap to the last replication is greater than the deletion stub purge interval?

@19 - { Link }

verb (used with object)
4. to veto; refuse to agree to; prohibit: to nix the project.

Fix, not nix!

I guess this would be possible using a contact type of Company with all the relevant info that you associate with a contact type of Person . . . .
I agree this would be a great feature to have.

I agree with Jeff - use Nomad.

How about taking this one step further and having policy options for Citrix clients?