Path: utzoo!utgpu!NDSUVM1!NETNWS-L
Date:	Fri, 23 Feb 90 13:05:59 EST
Reply-To: NETNWS-L Netnews List <NETNWS-L@NDSUVM1.bitnet>
Sender: NETNWS-L Netnews List <NETNWS-L@NDSUVM1.bitnet>
From:	Irwin Tillman <IRWIN@PUCC.bitnet>
Subject:      Re: Proposal for Listserv gateway to Netnews
To:	UofToronto LAN redistribution <NETNWS-L@UTORGPU.uucp>
Message-ID: <90Feb23.132034est.57352@ugw.utcs.utoronto.ca>
Newsgroups: list.netnws-l
Distribution: ut
Approved: devnull@gpu.utcs.toronto.edu

If you're not worried about forgeries, you can get away without
a file at the gateway.  You can rely on the Newsgroups header, and
not gateway stuff if you can't convince the list owner to add
a Newsgroups definition.  If you do that, you don't need to
put the newsgroup name into a gateway file.  (This in fact was
a major reason for the creation of the 'Newsgroup' header in
Listserv.)

If you want to provide some protection against forgeries, then
you can use a file at the gateway specifying some characteristics
of the incoming files before accepting them as valid.  I use this
at my site; my gateway file contains lines of the form:

originid class form name type dist

here are some sample entries:

VMMAIL   M  QUIET    BIOMED-L MAIL     NDSUVM1
VMMAIL   M  QUIET    COCO     MAIL     PUCC
VMMAIL   M  QUIET    *        MAIL     RPIECS
*        M  QUIET    AIX-L    MAIL     BITNIC