Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!UMDHEP.BITNET!MANAGER
From: MANAGER@UMDHEP.BITNET
Newsgroups: mod.computers.vax
Subject: BITNET mail follows
Message-ID: <8510312256.AA02164@ucb-vax.berkeley.edu>
Date: Thu, 31-Oct-85 20:45:04 EST
Article-I.D.: ucb-vax.8510312256.AA02164
Posted: Thu Oct 31 20:45:04 1985
Date-Received: Sat, 2-Nov-85 07:08:15 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 23
Approved: info-vax@ucbvax.berkeley.edu

For VMS 4.x there is a command procedure in SYS$EXAMPLES
called MAILUAF.COM that is self-documented and will fix
the corruption of VMSMAIL.DAT, the data file containing
general user mail info. To correct the incorrect number
of mail messages reported, just keep typing READ/NEW in
MAIL until you have 0 new messages, or read MAILUAF.COM
and use that to correct the problem.  I have written a
program that will fix a given user's (or all users')
mail info to correctly reflect the number of NEWMAIL
messages, but unfortunately it has some quirks that I
haven't yet worked out (for lack of effort, since I
found out about MAILUAF.COM later). You might utilize
the part of the program that determines the number
of new mail messages and feed that to a command proc
that will drive MAILUAF, and presto! you should have
fixed everyone's problems (with mail, not personal).
I'll send the FORTRAN source to the program on a demand
basis. Please indicate your path CLEARLY, since I'm
on BITNET only.

Todd Aven
Softwear Sweatshop, High Energy Physics
University of Maryland