Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!elroy!cit-vax!mangler
From: mangler@cit-vax.Caltech.Edu (System Mangler)
Newsgroups: news.misc
Subject: Re: A four-line-limit para-proposal
Message-ID: <3539@cit-vax.Caltech.Edu>
Date: Sun, 9-Aug-87 21:59:54 EDT
Article-I.D.: cit-vax.3539
Posted: Sun Aug  9 21:59:54 1987
Date-Received: Mon, 10-Aug-87 03:46:23 EDT
References: <479@unisoft.UUCP> <1171@rayssd.RAY.COM> <836@klipper.cs.vu.nl> <145@ers.UUCP>
Organization: California Institute of Technology
Lines: 20
Summary: supplying uucp routes

In article <145@ers.UUCP>, lyndon@ers.UUCP (Lyndon Nerenberg) writes:
> MOVED by lyndon@ncc.UUCP THAT signatures be removed from the next
>	release of Bnews.

I've always typed mine by hand, so I heartily approve.

It seems that most of the purpose of the signature is to suggest uucp
routes from well-known relays.	This is a property of the machine, not
of the individual poster.  Shouldn't this be something for the news
administrator to put in a configuration file, instead of each poster
being left to figure out a (typically rather poor) path for himself?
When routes change, it's easier for the administrator to edit one file
than to get everyone to update their .signature.

If signatures remain a part of Bnews, then at least they should have
hooks for inserting default information from files in /usr/lib/news.

If there is no signature, then this information should go in a header.

Don Speck   speck@vlsi.caltech.edu  {ll-xn,rutgers,amdahl}!cit-vax!speck