[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

4091.0. "Disable sending mail for one user?" by GIDDAY::JOYCE (Burn me kangaroo down sport) Wed Apr 20 1994 05:37

    
    Here's a bit of a brain-teaser...
    
    A customer wants to know how to prevent ONE user from sending mail; it
    seems the user in question has been a bad boy and they want to clip his
    wings a bit.  They still want him to be able to use WP and have access
    to shared drawers and for TM to function as usual but he's not supposed 
    to be able to create or send mail from EM or WP.
    
    To my knowledge, there is no magic option/flag/field existing in IOS to
    allow this.  Customisation would be a lot of work to get totally
    bomb-proof (this user is in MIS and could probably find any holes).
    
    Given that the MAIN drawer seems to be essential for mail functions I tried
    various combinations of creating a new WP drawer, deleting or disabling
    the MAIN drawer, setting the INDICATOR flag on the MAIN drawer, setting
    ACLs on DOCDB etc. etc.  None of these options work - it becomes
    impossible to select a non-MAIN drawer (I get "drawer does not exist")
    so basically the account is useless because I can't work in the MAIN
    drawer and I can't work in ANY other drawer.
    
    I'm also concerned that a screwed-up MAIN drawer will casue problems
    for TRM and TRU.
    
    Anyone got any bright ideas?
    
    Andy 
    CSC Sydney
    
       
    
T.RTitleUserPersonal
Name
DateLines
4091.1BRUMMY::MARTIN::BELLMartin Bell, NETCC, Birmingham UKWed Apr 20 1994 10:079
It will be tricky to stop EM but still allow full TM functionality, as
he will need to send messages to schedule meetings and may use that
as a hack to send other messages.

Didn't a corrupt NICKNAME.DAT cause addressee validation to access-
violate?


mb