Uh Clem's Admin World

I started getting the error below when I launch my Notes 8.0.1 client.  I also get it when I try to set a different bookmark (workspace of course) as my homepage.   I searched the web and only found one posting which was ND8 feedback in the ND8 forum, but this posting related to starting the admin client first, which I am not doing.

So I tried to do the obvious and create a ClientBookmark.nsf file using the bookmark.ntf template.  This seemed to work!

Even though the problem "seems" to be fixed I'm left with some questions.   Why is there a ClientBookmark.nsf in addition to the Bookmark.nsf?   Isn't one enough?  Also, why don't I find any documentation on this?

 So we have over 120 general (MIDB) mailboxes.  You know, those shared mailboxes like "resumes@acme.com".    Well a handful of them have auto-response agents that respond to the sender with a email stating that we have received their email.   I use a simple agent using the "Reply to Sender" action triggered on "After new mail has arrived".  When you do this the Sender address of the auto-response email is the signer of the agent.

I have chosen to use an ID called "No Reply" on these agents.  However I have gotten some push back from Sales telling me this doesn't look that great to the customer.

Do you think it is accepted practice to use the sender address of "No Reply" on auto-response emails?   Do you think email users out there pretty much know what it means when they receive an email from "No Reply"?  Do you recommend a better strategy for auto-response emails?

It was always useful to easily see what point release was installed when you launched Notes.  Not anymore!

Changing the Notes password for the average user is not a trivial task.  It is way more confusing and buried than it should be.

First the user will find the "Change Password" option under "File-Security-User Security", at which point they are challeneged to enter their current password.  How many people would easily find this and know this is where you change your password.

Now the user security screen has 10 different buttons or menus to click on and the "Change Password" button is kinda lost in the middle.  For 98% of my users changing the password would be the ONLY reason they would ever go into the user security screen, so why don’t they make it more prominent?

Now comes the confusing part. When they click on "Change Password" they get a prompt asking for another password.  Now is this the current password, or is this the new password?  It is not obvious.  It is made more confusing because the user is forced to enter their current password TWICE!

How hard would it be so that when they click on "Change Password" the prompt says "Enter CURRRENT Password", and not just "Password".  I never understood why it asks for their current password a second time anyway.  If it is a security requirement, then fine, clarify the prompt.

The usability team at Lotus have done a great job on 8.x, but they need to put some energy in the nooks and crannies of the client.