Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ames!ucbcad!ucbvax!MCMASTER.BITNET!SIBLOCK
From: SIBLOCK@MCMASTER.BITNET
Newsgroups: comp.os.vms
Subject: Synchronizing VMSMAIL.DAT with SYSUAF file
Message-ID: <8712090222.AA03747@ucbvax.Berkeley.EDU>
Date: Tue, 8-Dec-87 11:25:00 EST
Article-I.D.: ucbvax.8712090222.AA03747
Posted: Tue Dec  8 11:25:00 1987
Date-Received: Sun, 13-Dec-87 16:42:47 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 28


We found an interesting little 'feature' of VMS Mail yesterday:
User "AAA" had his mail forwarded (using SET FORWARD) to user
"BBB".  Well, last week we removed user AAA from the SYSUAF file,
only to discover we could still send mail to AAA, and it
did in fact end up in BBB's mailbox.   Presuming
this is because running AUTHORIZE to remove a user does *not*
update the VMSMAIL.DAT file, we would like to know if someone can
suggest a procedure which will get our VMSMAIL.DAT  file in
synch with our current SYSUAF file.    I wonder how many 'ghost'
usernames are still receiving mail this way?


--------
Stephen J. Siblock

Bitnet: SIBLOCK@mcmaster                
        SIBLOCK@mcmvm1                  
VMS:    SSCVAX::SIBLOCK
        profs%"SIBLOCK@mcmvm1.profs"    
CoSy:   siblock
--------
        Computing Services Coordinator, Faculty of Science
        Computing and Information Services
        McMaster University, ABB-149
        Hamilton, Ontario, Canada  L8S 4M1
        (416) 525-9140, x4157.
--------