blinn@gerbil.dec.com (Dr. Tom @MKO, CMG S/W Mktg, DTN 264-4865) (05/24/88)
Mike Temkin writes, regarding this topic: > Path: decwrl!hplabs!sdcrdcf!csun!mst > Subject: Re: Getting rid of phantom NEW MAIL msgs upon login... > Posted: 20 May 88 15:27:16 GMT > Organization: California State University, Northridge > > In article <400@csdgwy.unsw.edu.au> craig@csdgwy.unsw.edu.au writes: > >In article <11957897978315001@bert.chem.wisc.edu>, LIVINGSTONE@bert.chem.wisc.EDU (Gonzo Fibes) writes: > >> A MAIL.MAI file was accidently erased before two new mail msgs were > >> read. The MAIL.MAI file was re-CREATEd, but now everytime the user > >> logs on, he receives a "You have 2 new MAIL messages" when he doesn't. > >> Real mail sent to this user increments the number from 2 to three and so > >> on, but the baseline always stays 2. My guess is that somewhere, in > >> some file there were some bits set which need to be un-set. Anyone > >> out there know the infrastructure of the MAIL utility well enough to > >> help me get rid of this msg? My SYSOP is stumped. > > > I had the same problem about 2 months ago. Someone was posted a response > that I followed and it worked beautifully. > 1. Mail yourself two messages, you now should see 4 new messages > 2. Copy the mail.mai file to a temporary file > 3. Delete the two messages from the mail.mai file, > this leave you back where you started from. > 4. Copy the temporary file to mail.mai > 5. Delete the two messages and your count will be correct. :-) > > Hope this helps! > -- > Mike Temkin > ...!{ihnp4,sdcrdcf,hplabs,psivax,ttidca}!csun!mst > Cal. State U. Northridge, School of Engineering and Computer Science While the steps he proposes will work, it is certainly a kludgy way of doing something for which there is a SUPPORTED, DOCUMENTED fix. If your MAIL.MAI's NEWMAIL folder is empty, while the system's MAIL database (SYS$SYSTEM:VMSMAIL.DAT) thinks you have new mail, the supported, documented way to get the two back in synch is to issue the READ/NEW command. Doing this once or twice (I don't recall which, it's been a while since I've had the problem) will fix the count in the system's MAIL database file. This is documented in the MAIL manual in the full VMS documentation set, but you sort of have to know how to find it (it's not immediately obvious). When all else fails, RTFM. Regards, Tom Dr. Thomas P. Blinn Channels Marketing Group Digital Equipment Corporation Continental Blvd. -- MKO2-2/F10 Merrimack, New Hampshire 03054 Internet: blinn@dr.dec.com Easynet: DR::BLINN Usenet: {decvax,ucbvax,allegra}!decwrl!dr.dec.com!blinn Phone: (603) 884-4865 Note: Opinions expressed herein are my own, and do not necessarily represent those of my employer or anyone else, living or dead, real or imagined.
info-vax-request%kl.sri.COM%KL.SRI.COM%lbl%sfsu1.hepnet@LBL.GOV (05/28/88)
Received: from KL.SRI.COM by LBL.Gov with INTERNET ; Thu, 26 May 88 19:38:13 PDT Received: from ucbvax.Berkeley.EDU by KL.SRI.COM with TCP; Tue 24 May 88 16:52:43-PDT Received: by ucbvax.Berkeley.EDU (5.59/1.28) id AA09488; Tue, 24 May 88 06:14:44 PDT Received: from USENET by ucbvax.Berkeley.EDU with netnews for info-vax@kl.sri.com (info-vax@kl.sri.com) (contact usenet@ucbvax.Berkeley.EDU if you have questions) Date: 24 May 88 15:42:00 GMT From: gerbil.dec.com!blinn@decwrl.dec.com (Dr. Tom @MKO, CMG S/W Mktg, DTN 264-4865) Organization: Digital Equipment Corporation Subject: RE: Clearling the "new messages" counter Message-Id: <8805241302.AA15053@decwrl.dec.com> Sender: info-vax-request@kl.sri.com To: info-vax@kl.sri.com Mike Temkin writes, regarding this topic: > Path: decwrl!hplabs!sdcrdcf!csun!mst > Subject: Re: Getting rid of phantom NEW MAIL msgs upon login... > Posted: 20 May 88 15:27:16 GMT > Organization: California State University, Northridge > > In article <400@csdgwy.unsw.edu.au> craig@csdgwy.unsw.edu.au writes: > >In article <11957897978315001@bert.chem.wisc.edu>, LIVINGSTONE@bert.chem.wisc.EDU (Gonzo Fibes) writes: > >> A MAIL.MAI file was accidently erased before two new mail msgs were > >> read. The MAIL.MAI file was re-CREATEd, but now everytime the user > >> logs on, he receives a "You have 2 new MAIL messages" when he doesn't. > >> Real mail sent to this user increments the number from 2 to three and so > >> on, but the baseline always stays 2. My guess is that somewhere, in > >> some file there were some bits set which need to be un-set. Anyone > >> out there know the infrastructure of the MAIL utility well enough to > >> help me get rid of this msg? My SYSOP is stumped. > > > I had the same problem about 2 months ago. Someone was posted a response > that I followed and it worked beautifully. > 1. Mail yourself two messages, you now should see 4 new messages > 2. Copy the mail.mai file to a temporary file > 3. Delete the two messages from the mail.mai file, > this leave you back where you started from. > 4. Copy the temporary file to mail.mai > 5. Delete the two messages and your count will be correct. :-) > > Hope this helps! > -- > Mike Temkin > ...!{ihnp4,sdcrdcf,hplabs,psivax,ttidca}!csun!mst > Cal. State U. Northridge, School of Engineering and Computer Science While the steps he proposes will work, it is certainly a kludgy way of doing something for which there is a SUPPORTED, DOCUMENTED fix. If your MAIL.MAI's NEWMAIL folder is empty, while the system's MAIL database (SYS$SYSTEM:VMSMAIL.DAT) thinks you have new mail, the supported, documented way to get the two back in synch is to issue the READ/NEW command. Doing this once or twice (I don't recall which, it's been a while since I've had the problem) will fix the count in the system's MAIL database file. This is documented in the MAIL manual in the full VMS documentation set, but you sort of have to know how to find it (it's not immediately obvious). When all else fails, RTFM. Regards, Tom Dr. Thomas P. Blinn Channels Marketing Group Digital Equipment Corporation Continental Blvd. -- MKO2-2/F10 Merrimack, New Hampshire 03054 Internet: blinn@dr.dec.com Easynet: DR::BLINN Usenet: {decvax,ucbvax,allegra}!decwrl!dr.dec.com!blinn Phone: (603) 884-4865 Note: Opinions expressed herein are my own, and do not necessarily represent those of my employer or anyone else, living or dead, real or imagined.