I hear an echo  in here ...  I've asked about  this before (no answer
did I see).  My suggestion, to alleviate  one of the two concerns, is to
have a  mode like private which  would allow people in  the same general
domain to  access the server if  the userid and the  general domain part
were the same.
 
   That problem  would help  people on  clusters who  have no  choice of
where their mail comes from (please, I know machines can be changed, but
the people on my list can't do that).  For example:
 
       Current:      [log in to unmask]
                 and [log in to unmask]    are no the same.
 
       New:          [log in to unmask]
                 and [log in to unmask]    are equivalent.
              So is: [log in to unmask]
            But not: [log in to unmask]
 
   I'd settle for just that part.
 
   The other problem  is the one of people on  a re-distribution list of
some sort.  I have two ideas on that:
 
   Either:  a new  field (settable  only  by a  list-owner) could  allow
postings from  a specific  high level domain  which would  be associated
with that entry (up to 3 values, wildcards allowed):
 
           [log in to unmask]
 
           would allow postings from *.cc.school.edu to go through or not.
 
   OR if a posting comes via a NETNEWS type machine, a post through that
machine would be allowed regardless of poster or not.
 
   Failing  all of  that,  I would  settle  for getting  a  copy of  any
postings sent to a  "private list" that were rejected so  I can work out
putting a dummy entry  in it for each person, but I  like the first idea
better.
 
** ------------------------------------------------------------------ **
**  Geert K. Marien : [log in to unmask]  (Bitnet: GKMQC@PUCC)  **
**   ListOwner: AIRLINE, NODEINFO, RAILROAD, STAMPS, The INDIA List   **
**    (All contents are my own opinions - unless otherwise stated)    **
** ------------------------------------------------------------------ **