Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!tiamat!jim
From: jim@tiamat.fsc.com (Jim O'Connor)
Newsgroups: comp.mail.elm
Subject: Re: Local and remote signatures - a solution(?)
Keywords: signatures
Message-ID: <589@tiamat.fsc.com>
Date: 5 Jun 89 02:59:17 GMT
References: <398@sirius.ua.oz> <581@tiamat.fsc.com> <1430@itivax.iti.org>
Organization: Filtration Sciences - Chattanooga,TN
Lines: 26

In article <1430@itivax.iti.org>, scs@vax3.iti.org (Steve Simmons) writes:
> In article <581@tiamat.fsc.com> jim@tiamat.fsc.com (Jim O'Connor) writes:
> :This would be a workable solution for "configuration file literate" users,
> :but most of my users still don't understand that .elm/elmrc and .newsrc
> :exist and/or what they are used for, much less a .elm/local-users file.
> 
> True, but you as site admin can make it unnecesary for them.  Suppose
> we have the following rules for pattern matching: first look in the users
> .elm/local-users file.  If a definitive match is not found, look in
> /usr/local/lib/elm (or wherever you install the elm helpfiles and such)
> for a local-users file.  Reasonable?

If users become dependent on the system-wide file though, then everytime
a user starts corresponding with someone from a new site or domain that he
or she would like to be considered 'local', the user will call me and ask
why it isn't working right, and if I would fix it so it will.  Thus, the
burden will end up on me. (Remember, they don't care about their own
local-users file, so it won't do any good to tell them to edit that.)

The menu option would be something they would easily see and be able to
deal with.
------------- 
James B. O'Connor			jim@tiamat.fsc.com
Filtration Sciences Corporation		615/821-4022 x. 651

*** Altos users unite! mail to "info-altos-request@tiamat.fsc.com" ***