4 innxmit \- send Usenet articles to a remote NNTP server
44 connects to the NNTP server at the specified
46 (validating itself via
49 and sends it the articles specified in the batchfile named
51 It is normally invoked by a script run out of
55 to lock the host name, followed by a
57 command to flush the batchfile.
61 is not an absolute pathname, it is taken relative to the
62 .I <pathoutgoing in inn.conf>
64 It is normally written by specifying the ``Wnm'' flags in the
67 Each line in the batchfile should be in one of the following formats:
78 field names the article to be sent.
81 field is not specified, it will be obtained by scanning the article.
86 fields are separated by a space.
88 If a communication error such as a
92 will stop sending and rewrite the batchfile to contain the current
93 article and any other unsent articles.
97 If all articles were sent successfully,
99 will remove the batchfile; otherwise it will rewrite it to contain the
100 list of unsent articles.
101 If no articles were sent or rejected, the file is left untouched.
102 This can cause the batchfile to grow excessively large if many articles
103 have been expired and there are communication problems.
104 To always rewrite the batchfile, use the ``\fB\-a\fP'' flag.
107 In streaming mode, a check of each message ID is still made to avoid sending
108 articles already on the server.
109 The ``\fB\-c\fP'' flag will, if streaming mode is supported,
110 result in sending articles without checking.
111 This results in slightly greater throughput and may be appropriate when
112 it is known that the site could not already have the articles such as in
113 the case of a "leaf" site.
116 Use the ``\fB\-d\fP'' flag to print debugging information on standard error.
117 This will show the protocol transactions between
119 and the NNTP server on the remote host.
122 If the ``\fB\-H\fP'' flag is given, then only headers are sent to
124 for all articles except control messages.
125 And Bytes: header is also included even if it does not exist in the original
126 article. ``\fB\-H\fP'' flag is useful for diablo reader.
129 The ``\fB\-l\fP'' flag is used to turn on logging of reasons the remote gives
130 for rejecting an article.
133 To specify a port number other than the default, use the ``\fB\-P\fP'' flag.
136 If the ``\fB\-p\fP'' flag is given, then no connection is made and the batchfile
137 is purged of entries that refer to files that no longer exist.
138 This implies the ``\fB\-a\fP'' flag.
141 If the remote server sends an unexpected reply code,
143 will requeue the article and proceed.
144 Use the ``\fB\-r\fP'' flag if the article should not be requeued.
148 will attempt to negotiate a streaming mode extension of the NNTP
149 protocol with the server at connect time.
150 If successful it will use a slightly different protocol that enhances
152 If the server does not recognize the streaming mode negotiation
154 will revert to normal NNTP transfer mode.
155 Use the ``\fB\-s\fP'' flag to disable the attempt to negotiate the streaming
159 To specify the total amount of time that should be allowed for article
160 transfers, use the ``\fB\-T\fP'' flag.
161 The default is to wait until an I/O error occurs, or all the articles have
163 If the ``\fB\-T\fP'' flag is used, the time is checked just before each
164 article is started; it will not abort a transfer that is in progress.
168 normally blocks until the connection is made.
169 To specify a timeout on how long to try to make the connection, use
176 reports transfer and CPU usage statistics via
178 If the ``\fB\-v\fP'' flag is used, they will also be printed on the standard
181 Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews.
183 This is revision \\$3, dated \\$4.
185 .R$ $Id: innxmit.8 5909 2002-12-03 05:17:18Z vinocur $