This part may appear difficult to understand for the novice user. If you simply want to send your local posts to the provider, then there is no need to read any further. You may select the next page or return to the table of contents.
A file named newsfeeds specifies where to send incoming articles, local posts as well as articles transfered from other servers. Changi expects this file to live in CHANGIWORKDIR and parses it during the startup phase. If the file doesn't exist, then feeding other sites is performed in a default way, which may be sufficient for most implementations. For each locally posted article Changi will create a set of spool files in CHANGISPOOLDIR to be sent to the site specified by NNTPNEIGHBOR.
The file is interpreted line by line. Each line represents a feed entry. Continuation lines are possible by adding a backslash at the end of the previous line. Blank lines and lines starting with # are ignored.
Each line is divided into fields separated by colons and optional sub-fields separated by slashes. Some fields may contain several items separated by commas.
The general format of each entry is
site[/exclist]:patterns[/distribs]:flags:param
site
The full domain name of the site to send articles to. If this
name appears in the path line of any article's header, that article
will not be sent to this site. This field is not case
sensitive, excepting an entry named ME, which is treated
specially (see below).
exclist
A comma separated list of additional site names. If any of these
names appear in the path line of an article's header, that article
will not be sent to this site.
patterns
This is a comma separated list of wildcat expressions
and defines the site's subscriptions. The site will receive
all newsgroups matching this list. Note that any pattern
specified in the ME entry is prepended to this list. A typical
setup might set the pattern in ME to match all default groups
and use the pattern field of all other sites to exclude
some defaults and include special groups.
distribs
With this optional list you may further specify which
articles the site should receive, based on the distribution
line in the article header. Use an exclamation mark to exclude
distributions.
For further explanations refer to the chapter titled Limiting Distribution of Posts.
flags
This is a comma separated list of flags, used to switch on or
off miscellaneous options. Note that some flags require values,
which should immediately follow the flag character without any
separating whitespace.
There are two general feed types, which are mutually exclusive.
Both general types may be combined with any the following modifiers.
In addition to the two general types there is a special file feed for UUPC support.
param
The meaning of this field depends on the feed's type.
If the site is fed by a file, then this field specifies the name of the file, either with an absolute path or relative to CHANGIWORKDIR. When a site is flushed, Changi will write all queued articles to this file. If this field is left blank, then Changi will create UUCP spool files when flushing the site.
If the site is fed by a program, then this field is interpreted as the name of a program to be started when the site is flushed. If this is a batch feed (flag Tb), then it must contain a single %s, which will be converted to the path name of the batch file. If the site is flushed, then Changi will run the program concurrently. After the program has finished processing the batchfile, it must remove it. Changi will not flush a site unless the previous batch has been removed.
If the site is fed by a program but is not a batch feed, then Changi will call this program for each article and write the contents of the article to the program's standard input.
If the site is named ME, then the entry is handled in a special way. This entry should be the first and only one. If not given, it defaults to
ME:*,!control,!control.*,!junk,!local,!local.*/!local::
ME:*,!control,!control.*,!junk,!local,!local.*/!local:: <remote>::L:where <remote> is the name of the site found in the environment, either NNTPNEIGHBOR or NNTPSERVER. This will store all locally posted articles in uucp spool files, where Chanx will find them for transmission to the remote host.
If you're exchanging news using UUPC/extended, then you should create the following newsfeeds file:
ME:*,!control,!control.*,!junk,!local,!local.*/!local:: <remote>::L,TU:
If you're connected to a push feed, then you can use rnews to transmit your local posts to the remote server:
ME:*,!control,!control.*,!junk,!local,!local.*/!local:: <remote>::L,Tp:rnews -H<remote>Changi will call Rnews on each local post it receives and write the article immediately to the standard input of Rnews. In turn, Rnews will transmit the article to <remote> using the IHAVE protocol.
URL: changi/manual/newsfeed.html Created: 3 August 1996 Revised: 21 December 1996 Author: harald@os2point.ping.de |