nntppost is a NNTP (Net News Transfer Protocol) client that sends
articles to a remote NNTP server. It was written for AS225R2 but seems
to work fine with AmiTCP and the faked socket.library done by Henning
Schmiedehausen (also on Aminet).

There are two different method to feed articles into an NNTP news server.
You can be a NNTP user agent (news reader) that generates new articles,
the NNTP server will tag the message with a unique message id and transports
within a distribution area. You can also be a NNTP server yourself that
relays messages from news readers or other servers. These messages are
transmitted unchanged. Most NNTP servers restrict server access to a well
known set of feeds while most hosts in the same organization can originate
articles as a user agent.

Usage:

> nntpput ?
ARTICLES/A,AGAINLIST/K,NNTPSERVER/K/A,SLAVE/S,CPS/K/N: 

  ARTICLES         list of article file names (usually a 'togo'-file from a
                   C-News database). There is one file name per line, names
                   are treated as is, e.g. you either need absolute pathes
                   or start nntpput from the spool directory. Lines that
                   start with a '#' are ignored.

  AGAINLIST        a list of article file names of those articles that couldn't
                   be transferred. Rejected articles are preceded with a
                   comment that shows the numeric NNTP response code. You
                   can use this file as an ARTICLES file, but rejected
                   articles will probably be rejected again.

  NNTPSERVER       the name or IP number of your NNTP server machine

  SLAVE            send data as a slave NNTP server using the IHAVE command.
                   Without SLAVE nntpget will use the POST command.

  CPS num          bandwidth limitation. nntpget tries to keep traffic below
                   the given characters per second. This can only be an average
                   since there are bursts of at least one TCP segment which
                   are under control of the TCP protocol stack.
                   The bandwidth is just limited for article transfers and not
                   for the initial transfer of article MsgIDs but which is short.

While running nntpput will show you (part of) the NNTP traffic on stdout as well
as the average transfer rate.

Michael van Elst

 PERMSSN    UID  GID    PACKED    SIZE  RATIO     CRC       STAMP          NAME
---------- ----------- ------- ------- ------ ---------- ------------ -------------
[generic]                 4334    6916  62.7% -lh5- fbb6 Dec 19  1994 nntpput
[generic]                 1150    2467  46.6% -lh5- 8f70 Dec 19  1994 nntpput.readme
---------- ----------- ------- ------- ------ ---------- ------------ -------------
 Total         2 files    5484    9383  58.4%            Dec 20  1994