#
# this file specifies outgoing feed information.
#
# the format is:
# <hostname_or_address> <port> <connection_flags> <host_and_group_info> [<MaxBackLog>]
#
# where:
# 
# <hostname_or_address> is the hostname (e.g. news.maxwell.syr.edu)
#
# <port> is the port to connect to on the remote host (usually 119)
#
# <connection_flags> is a set of characters, where each character
#                    indicates that a connection should be made, and
#                    how that connection should be used.
# These are the possibilities for connection_flags:
#     s  --  feed only articles <50k
#     S  --  feed only articles <10k
#     m  --  feed only articles <500k
#     M  --  feed only articles <250k
#     b  --  feed only articles >=50k
#     B  --  feed only articles >=500k
#     l  --  latency feed, skip to head if more than 1000 articles 
#            behind, feed only articles <50k
#     L  --  latency feed, skip to head if more than 100 articles 
#            behind, feed only articles <10k
#     f  --  full feed
#
# All feeds are bounded by the MaxBacklog parameter (in config.txt), or the optional
# MaxBacklog specified as a 5th parameter.
#
# Keep in mind that files cannot be deleted while they're being fed
# from, so make sure you have enough disk space to deal with the number
# of files that will be held open by your feeder threads.
#     
# each character in the string will create a connection (and a thread).
#
# <host_and_group_info> specifies how to decide which articles get 
#		        fed to this host
# This should be a comma separated list of patterns, optionally 
# preceeded by flags.
#
# the patterns are regexp like:
# * matches anything
# ? matches any single character
# 
# the simplest example would a single group name:
# news.software.nntp
#
# The patterns can be preceeded by flag characters:
#
#  @ indicates this pattern should be matched against the path line,
#    and the article should not be sent to this host if a match is found
#  ! negates the pattern (i.e. don't send anything that matches this)
#    may only be applied to group patterns.
#  ~ poison: if this a entry is found, do not send the article to this 
#    host.  
#
# some examples:
#
# news.host.com 119 lf @*news.host.com*,!comp.lang.java*,~*binaries*,comp.*
#
# this entry will send all of comp, excepting comp.lang.java, and excepting
# anything that is posted into a group that has the string "binaries" in
# it's name.  The @*news.host.com* will prevent you from feeding anything
# to news.host.com that it has already processed.
#
# the "lf" for the connection_flags will create two connections, one 
# that always sends the latest news, and another fills in the rest.
#
# news.host.com 119 lf @*news.host.com*,@*spammers.r.us.com*,*
#
# this will send everything, but will not send any posts that have 
# gone through the news host "spammers.r.us.com"
#
# Now, a note about ordering the patterns.  The patterns are searched 
# in order from left to right, starting with a false match assumption.
# Each pattern is applied to each group in the Newsgroups: line until
# a positive match, poison, or the end of the patterns is 
# encountered.  A negative (!) match will cause the search to 
# move to the next group on the line, or terminate if there are
# no more groups.  So:
#
# comp.*,!comp.lang.*
#
# will send all comp groups, including comp.lang.* because the
# positive match occurs before the negative.
# It should be reversed:
#
# !comp.lang.*,comp.*
#
# Host specifiers are compared with the entire path line, rather than
# breaking it up element by element.  This means you will almost 
# always use a form like @*news.host.com*
#
# You can use host specifiers anywhere in the line, and this might be
# to your advantage, assuming you know something about the topology
# of newsflow (or you want to create a known topology).  For instance:
#
# @*news.host.com*,rec.*,alt.*,@*news.fastcomp.com*,comp.*
#
# would always send rec.* and alt.* articles, but would only send 
# comp.* articles if they had not passed through news.fastcomp.com 
# (which presumably is fast and peers directly with news.host.com).
#
# I'm not sure this is useful, but it is available as a consequence
# of the way that the filtering is done.  Please drop an email if
# you think of ways that this is useful, or if you can think of
# modifications to make it more so.
#
# cmsedore@maxwell.syr.edu 6/12/97

news.host.com 119 lf @*news.host.com*,*
news.important.com 119 ff @*news.important.com*,* 50000

