# NEWS V6.0		2-Apr-1990
#
# NEWS.SYS Control file. This file describes which newsgroups are distributed
# to adjacent NEWS sites, and how this feed is set up.
#
# This file line has five fields, each separated by colons:
#
#	system-name:subscriptions:flags:queue-file:distributions
#
#     - system-name : REQUIRED
#	This field is the network name of the system. The system name
#	should match the name as used by the system in the Path: header
#	line, and contain no whitespace characters. Note that some systems
#	use fully qualified domain names, while other use only the node
#	name. There are entries for all remote systems and also one entry
#       for the local system.
#
#	An entry for the local system name is REQUIRED in the file. The local
#       system name can be referred to as "ME" instead of the local system
#       name.
#
#	Remote system names may also be specified with the syntax:
#
#		site-name/site1,site2{,...}
#
#	This syntax is interpreted as referring to site-name only if the
#	item being parsed does _NOT_ contain site1 OR site2 in the Path: line.
#	i.e., send to site-name only if the item has not been relayed through
#	site1 or site2 already.
#
#     - subscriptions : OPTIONAL
#	This field is the list of newsgroups to be transmitted to the
#	system. The list of newsgroups may be explicit group names, or may 
#	specify the top level hierarchy or hierarchies. The word "all" is
#	treated as the wildcard "*" character.
#
#	The subscriptions list may also contain entries of the form
#	"!newsgroup", indicating that this newsgroup is NOT accepted.
#
#	e.g., a subscription entry containing
#
#		"...,anu,!anu.students,.."
#
#	will accept all newsgroups matching both "anu" and "anu.*", but will
#	reject newsgroups matching "anu.student" and "anu.student.*".
#
#	Unless you have also defined the description field, the subscription
#	list is also used to check distribution: matches, so acceptable
#	distribution names are also used in the subscription list.
#
#	If the field is omitted or empty, the wildcard "*" subscription is used
#	as the default value.
#
#      
#     - flags : OPTIONAL
#	This field contains a set of letters describing how each item should be
#	transmitted. The acceptable fields for the flags are:
#
#        B  - batch files are created. A batch file contains the text of each
#             item to be transferred, separated by the string:
#
#                   #!rnews <byte-size>
#
#        BN - same as B format, but all lines are prefixed by 'N'. This format
#             is normally used to transfer the queue file through mail.
#
#        M  - a new version of the queue file is created for each item to be
#             transferred. When using this option ensure that the VMS file
#             version limit of the queue file is NOT set
#
#        MN - same as M format, with all lines prefixed by 'N'
#
#        N  - Store only the message id into the queue file. The resultant
#             queue file can be processed by a NNTP transfer utility or can
#             be transferred to the remote system's "to.system" newsgroup
#             with the "ihave" control header.
#
#        NX - Same as N format, but the queue file is organisaed as an indexed
#	      file to allow simultaneous reading and writing.
#
#	If the field is omitted or empty the value "B" is used.
#
#	A number may be appended to the flags in this field for the 'b' and
#       'n' flags indicating the max size of eqach batch file (in bytes). 
#	If unspecified, the value defaults to whatever NEWS_BATCH_SIZE is
#	defined as.  For example, to send one million byte batches to sitex,
#       and default batches to sitey:
#	
#	sitex:comp:B1000000:NEWS_MANAGER_DEV/[POST_UUCP$CMPRS_SITEX]NEWS.BATCH
#       sitey:comp:B:NEWS_MANAGER_DEV/[POST_UUCP$CMPRS_SITEY]NEWS.BATCH
#
#     - queue-file : REQUIRED for all REMOTE system entries. NOT REQUIRED for
#	the local system.
#       This field is used to determine the name of the file to use
#	as the queue file. NOTE that the ':' character that would normally
#	appear in a VMS file specification must be replaced by a '/' character
#	in this field [the ':' is already used as a field separator].
#
#     - distributions : OPTIONAL
#	This field is used to match against the distribution: header line to
#	determine if the system will accept the item. The field has the same
#	format as the subscriptions field. If omitted, the subscriptions
#	field is used instead to check for a successful match.
#
# The first active line in the sys file should be the entry for the local
# host system.
#
# A '#' as the first character in a line denotes a comment. A logical line
# may be continued to the next physical line by putting a '\' at the end of
# the line.
#
##------------------------------------------------------------------------
##   Here is a sample VMS NEWS.SYS file (from node FAC3)
##------------------------------------------------------------------------
## first entry is for THIS SITE
## and is a list of groups which will be accepted
##
#me:world,inet,to.fac3,anu,comp,sci,rec,news,misc,soc,talk,aus,\
#canb,alt,local,junk,control,general
#
#csc:to.csc1,anu,comp,sci,rec,news,\
#misc,soc,talk,aus,canb,alt,!anu.students:B:\
#NEWS_MANAGER_DEV/[POST_CSC]NEWS.BATCH:canberra,act,aus,world,inet
#
#fac:world,inet,to.fac0,anu,comp,sci,rec,news,\
#misc,soc,talk,aus,canb,alt:B:NEWS_MANAGER_DEV/[POST_FAC]NEWS.BATCH
#
#oddjob:world,inet,to.oddjob,anu,comp,sci,rec,news,\
#misc,soc,talk,aus,canb,alt:B:NEWS_MANAGER_DEV/[POST_ODDJOB]NEWS.BATCH
#
# The following entry is a feed to a Unix site - this site requires leading
# N characters in column 1
#
#anucsd:world,inet,dcs,to.ra,to.anucsd,anu,canb,teach,\
#comp,sci,rec,news,misc,soc,talk,aus,alt:BN:\
#NEWS_MANAGER_DEV/[POST_ANUCSD]NEWS.BATCH
#
# The following entry is a feed into a mailing list. The actual mailing of the
# files is performed by a separate dcl command file, but the requirement is
# that each posted item is a separate file.    
#
#postmasters:anu.network,aus.netstatus:M:\
#NEWS_MANAGER_DEV/[MAIL_POSTMASTERS]NEWS.POST:*
#
# The following entry is a feed to node arp using the ihave/send protocol.
# Note that the first entry is for the collection of message id's and the
# second entry is for the transfer of these ids to node arp
#
# The corresponding DCL command to send the ids is:
# $ SET DEF NEWS_MANAGER_DEV:[IHAVE_ARP]
# $ NEWS/NOSCREEN POST/NEWS=to.arp/SUBJ="ihave FAC3"/NOEDIT/CONTROL COLLECT.IDS
# $ DELETE COLLECT.IDS;
#
# The alternative method is to perform the feed using NNTP. In this case
# the DCL command is:
# $ NNTPFEED :== $ dev:[dir]NNTP
# $ NNTPFEED arp decnet news_manager_dev:[IHAVE_ARP]COLLECT.IDS
# -or- (using a TCP-based NNTP link)
# $ NNTPFEED arp tcp news_manager_dev:[IHAVE_ARP]COLLECT.IDS
#
#arp:world,inet,arp,anu,canb,comp,sci,rec,news,misc,soc,talk,aus,alt:N:\
#NEWS_MANAGER_DEV/[IHAVE_ARP]COLLECT.IDS
#arp:to.arp:B:NEWS_MANAGER_DEV/[POST_ARP]NEWS.BATCH