Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!deimos.cis.ksu.edu!rutgers!psuvax1!psuhcx!wcf
From: wcf@psuhcx.psu.edu (Bill Fenner)
Newsgroups: news.admin
Subject: Re: List of sites with broken Followup (No References) Software
Message-ID: <1220@psuhcx.psu.edu>
Date: 11 May 89 21:06:48 GMT
References: <3222@looking.UUCP> <649@marob.MASA.COM>
Reply-To: wcf@psuhcx (Bill Fenner)
Organization: Engineering Computer Lab, Penn State University
Lines: 22

In article <649@marob.MASA.COM> cowan@marob.masa.com (John Cowan) writes:
|I am currently lobbying the Fidonet Technical Standards Association and the
|author of the Fidonet<->Usenet/uucp gateway to handle Message-Id: and
|In-Reply-To:/References: lines "correctly" by maintaining this information
|internally to Fidonet messages.  Don't expect too much too soon, though;
|still, at least there should soon at least >exist< a way of handling this
|problem within Fidonet, even if it will be a long time before Fidonet
|message-generators actually generate correct information.

There's no way you're going to get all of FidoNet to change to a USENET
capable BBS system.  I'm writing one (very slowly), but not everyone will
like it.  Not every software author will want to make the changes necessary
in their software, and not every sysop will want to run the new software.
It's possible, I suppose, to make USENET-capable a requirement before passing
the groups along; however, that's definitely not going to happen soon.

  Bill
-- 
   Bitnet: wcf@psuhcx.bitnet     Bill Fenner       | "Yesterday starts
  Internet: wcf@hcx.psu.edu                        |  tomorrow; tomorrow
 UUCP: {gatech,rutgers}!psuvax1!psuhcx!wcf         |  starts today"
Fido: Sysop at 1:129/87 (814/238 9633) \hogbbs!wcf |       -- Marillion