Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!csd4.milw.wisc.edu!lll-winken!uunet!wugate!wubios!david
From: david@wubios.wustl.edu (David J. Camp)
Newsgroups: comp.mail.elm
Subject: Re: Local and remote signatures - a solution(?)
Keywords: signatures
Message-ID: <490@wubios.wustl.edu>
Date: 8 Jun 89 01:04:04 GMT
References: <398@sirius.ua.oz> <581@tiamat.fsc.com> <1430@itivax.iti.org> <21069@winchester.mips.COM>
Reply-To: david@wubios.UUCP (David J. Camp)
Organization: Washington University (St. Louis)
Lines: 27

>>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?
> 
Why not look in both files?  The users personal file can take precedence
if there is any conflict, and the system file would still be available
when the user has just a few additions.

If elm were really smart it would place the appropriate signature file
in the edited file, and replace it with the newly appropriate signature
file (modifying the edited file) when leaving the headers menu.  It
would be necessary to check for an exact match of the previous signature
file against the last several lines of the file.

It is probably good enough to just use the correct signature at the time
of initial composition, since the user then has complete control over
the message in his edit buffer.

I still think an elmrc option whether to include the signature file in
the edited message is best.
-- 
Bitnet:   david@wubios.wustl                ^      Mr. David J. Camp
Internet: david%wubios@wucs1.wustl.edu    < * >    Box 8067, Biostatistics
uucp:     uunet!wucs1!wubios!david          v      660 South Euclid
Washington University (314) 36-23635               Saint Louis, MO 63110