AV> This suggests that my idea should work.  However, when I use
 AV> the following ACS for my WRITING conference:
 AV> Limited/!W!R!I
 AV> and the following ACS for my CIVLIB conference:
 AV> Limited/!C!I!V
 AV> assigning a user the keys "WRI" excludes him from both conferences,
 AV> apparently because both conferences share the key "I".
three solutions - only use one lock-out key per area.. set it so that those 
areas need to HAVE a certin key to access, and take one away if there isn't 
that key..
or use barricade files (which do away with keys all together).
If you're trying to ban people from a certain area, using this type of 
barricade fiel would help:
!Joe_User               Twit
!Arty_Smith             NoAccess
!John_Johnson           NoAccess
!All
would let Joe User have twit access, and would tell Arty Smith and Johny that 
the area does not exist
        Each line in an extended barricade file has the following
        format:
     
           !  
             or
           !All          [priv]
         is the name of the user whose access level is to
        be promoted. No spaces can be present in , so re-
        place spaces with underscores. (For example, to use Joe SysOp
        in an extended barricade, you would have to use "Joe_SysOp"
        for the .)
   
        If Maximus matches the name for the user trying to enter the
        barricaded area, the user's privilege level is altered to
         with no questions asked.
        In addition, if you specify "NoAccess" in the  field, a
        user who enters the specified password will be denied access
        and told that the area does not exist.
        If you use "!All" by itself, without specifying a privilege
        level, Maximus will let other users into the area using their
        real privilege levels. If you do specify a privilege level
        after the "!All" keyword, Maximus will let all users enter
        the area and promote all of them to a level of [priv].
ttyl, greg
--- Maximus/2 3.01
---------------