Some observations about a bug and an imperfect work-around I found: You may already be familiar with the bug (official?) that causes moz to forget that the master password has already been entered when a l/p requiring news server's group has been open long enough without activity that the server wants re-authentication. What happens is you go to read a new message on the open group and the prompt appears for the /server's/ l/p (which was already used via the master password to view the group in the first place.) This can be a major PITA with servers that assign hard-to- crack, hard-to-remember l/p combos, like Giganews. I've found that you can avoid tracking down and entering the server l/p if you collapse the server's tree, wait a few seconds, and re-open it. The server's groups refresh as usual and you can get back to reading without having to re-enter any passwords. This work-around leads to another problem, where the body of the message you clicked on to find that the server wanted to re-up is totally blank, and there's no way I've found to retrieve the text. I suspect that it is entered in the local database as downloaded before it actually is, so when you go to refresh it thinks it already has it. Ideally, when the server want to re-authenticate, mozilla will use it's memory that the master pass has already been entered and take care of it transparently. Next best would be to have the master password prompt appear again, even if you'd have to enter it more than once per session. I could even make due with a way to force the re-download of a message so I can see the blank one if I have to go the collapse route.
HTH
