tencati@JPL-VLSI.ARPA (08/18/86)
There are two methods I know of to clear out the "newmail" messages that sometimes crop up on VMS: 1) Have the user get into MAIL and type READ/NEW about 4 times, then EXIT. This usually clears their record in VMSMAIL.DAT. 2) Have the system manager run @SYS$UPDATE:MAILUAF.COM. This procedure can be used to REMOVE a user, then ADD them again. This will erase and re-create their entry in VMSMAIL.DAT thus clearing the count. The problem with this method is that it causes MAIL to "forget" about any subdirectory or forwarding that was enabled, as well as the other user-settable features of MAIL. Notice though, that the bogus mail count could be caused by some otherwise priviliged user telling mail to SET FILE to another user's MAIL.MAI file. If USER-A read's USER-B's mail with priviliges turned on, unless USER-A has changed his username (via cmkrnl) so that he "becomes" USER-B, when USER-B logs on, he is informed he has "n" new messages, but when he runs mail, there are no messages marked "new" because USER-A has already read them, but was not able to clear the newmail count for USER-B in VMSMAIL.DAT. So be alert for security holes. Have the affected users check the protection of their mail.mai files. MAIL runs with sysprv, so the GROUP and WORLD protections can be set to NO ACCESS with no adverse ramifications. Ron Tencati Sys. Mgr./ JPL-VLSI.ARPA