![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to inews.8 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDTahoe / new / news / man|
Return to inews.8 CVS log | Up to [CSRG BSD Unix] / 43BSDTahoe / new / news / man |
1.1 root 1: .if n .ds La '
2: .if n .ds Ra '
3: .if t .ds La `
4: .if t .ds Ra '
5: .if n .ds Lq "
6: .if n .ds Rq "
7: .if t .ds Lq ``
8: .if t .ds Rq ''
9: .de Ch
10: \\$3\\*(Lq\\$1\\*(Rq\\$2
11: ..
12: .TH INEWS 8 "October 14, 1986"
13: .ds ]W Version B 2.11
14: .SH NAME
15: inews \- submit news articles
16: .SH SYNOPSIS
17: .BR inews " [ " \-h " ]"
18: .BI \-t " title " \-n " newsgroups"
19: [
20: .BI \-e " expiration date"
21: ] [
22: .BI \-f " sender name"
23: ] [
24: .BI \-d " distribution"
25: ] [
26: .BI \-F " references"
27: ] [
28: .BI \-o " organization"
29: ] [
30: .BI \-M
31: ] [
32: .BI \-S
33: ] [
34: .BI \-a " approvedby"
35: ] [
36: .BI \-r " replyto"
37: ] [
38: .BI \-x " dontsentto"
39: ] [
40: .BI \-c " control-message"
41: ]
42: .PP
43: .BI "inews \-p " filename
44: .PP
45: .BI "inews \-C " newsgroup
46: .PP
47: .BI "rnews \-U"
48: .SH DESCRIPTION
49: .I Inews
50: submits news articles to the USENET news network.
51: It is a raw interface called by news-posting programs.
52: You should not use
53: .I inews
54: directly. Most people use
55: .IR postnews (1)
56: to post news articles. Ultimately, of course,
57: .IR postnews (1)
58: and other news-posting programs call inews to do the actual submission.
59: .PP
60: The first form (no
61: .BI \-p
62: or
63: .BI \-C
64: options) is for submitting ordinary articles.
65: The body of the article will be read from the standard input. A
66: .I title
67: (
68: .Ch Subject:
69: field)
70: must be specified (there is no default).
71: .PP
72: If
73: .IR expire (8)
74: is currently running or if
75: .B SPOOLBATCH
76: was specified at compilation time, the articles may be spooled to
77: .I /usr/spool/news/.rnews
78: for later processing. Running
79: .I "rnews \-U"
80: will unspool this articles.
81: .I "Rnews \-U"
82: is run automatically by expire when it is finished.
83: .PP
84: Each article is posted to one or more newsgroups. If the
85: .B \-n
86: flag is omitted, the list
87: will default to something like
88: .BR general .
89: If you wish to submit an article to multiple newsgroups, the
90: .I newsgroups
91: must be separated by commas and/or spaces.
92: .PP
93: The
94: .B \-e
95: flag is used to override the default expiration date. This is seldom
96: used.
97: .PP
98: The
99: .B \-f
100: flag specifies the article's sender. Without this flag, the sender
101: defaults to the user's name.
102: If
103: .B \-f
104: is specified, the real sender's name will be included as a ``Sender:'' line
105: to prevent forged articles.
106: .PP
107: The
108: .B \-d
109: flag allows you to specify the maximum geographic distribution of your
110: article; for example, a distribution of
111: .Ch aus
112: limits distribution to Australia, and a distribution of
113: .Ch nj
114: limits distribution to New Jersey. There is no way to send a message from
115: California for distribution only in New Jersey\(emyour machine must be in the
116: distribution that you ask for.
117: .PP
118: The
119: .B \-r
120: flag allows you to specify the ``Reply-To:'' line in the article header.
121: .PP
122: The
123: .B \-x
124: flag says not to forward this article to the specified site despite
125: what the
126: .I /usr/lib/news/sys
127: file says.
128: .PP
129: The
130: .B \-F
131: flag is used to attach a list of related articles that this
132: message references; it creates the
133: .Ch References:
134: field of the posted article.
135: .PP
136: The
137: .B \-o
138: is used to override the default organization name.
139: .PP
140: The
141: .B \-M
142: and
143: .B \-a
144: flags are to be used only by the moderator of a moderated newsgroup. The
145: .B \-M
146: flag causes the
147: .Ch From:
148: and
149: .Ch Path:
150: fields of the article to be set to correct values for a moderated newsgroup.
151: The
152: .B \-a
153: flag is used to add an
154: .Ch Approved:
155: line to the header. Note that if the
156: .B \-M
157: flag is used in conjuction with the
158: .B \-h
159: flag (see below), the article headers must not have a
160: .Ch Path:
161: field in them already.
162: .PP
163: The
164: .B \-h
165: flag specifies that headers are present at the beginning of the
166: article, and these headers should be included with the article
167: header instead of as text. Everything before the first blank line in the
168: article is taken as a header field, and everything after that blank line is
169: taken to be part of the body of the message.
170: (This mechanism can be used to edit headers and supply additional
171: nondefault headers, but not to specify certain information,
172: such as the sender and article ID, that
173: .I inews
174: itself generates.)
175: .I Inews
176: will ignore nonstandard and misspelled header fields entered with the \-h
177: option.
178: .PP
179: The
180: .I \-c
181: flag is used to send a control message.
182: .PP
183: The
184: .I \-S
185: flag is used to override the automatic spooling option (if enabled).
186: It shold never be specified directly. (It is normally used by
187: .IR "rnews \-U" .
188: .LP
189: When posting an article
190: .I inews
191: checks the environment for certain information about the sender. If
192: an environment variable
193: .B NAME
194: is defined,
195: .I inews
196: uses its value as the full name of the poster. If
197: .B NAME
198: is not defined,
199: \kx\f2$HOME\fP\h'|\nxu+2u'\f2$HOME/.name\fP
200: is checked and if it exists, its contents are used as the full name.
201: Otherwise, the system value (often in
202: .IR /etc/passwd )
203: is used.
204: This is useful if the system value cannot be set, or when
205: more than one person uses the same login.
206: If the environment variable
207: .B ORGANIZATION
208: is defined, then
209: .I inews
210: uses its value instead of the system
211: default organization name. If its value begins with a
212: .Ch / ,
213: then it is taken to be a file name, and
214: .I inews
215: takes the name of the organization from the contents of the file.
216: This is useful when a person uses a guest login and is
217: not primarily associated with the organization that owns the machine.
218: .LP
219: The second form (
220: .BI "inews \-p"
221: ) is used for receiving articles from other machines. If
222: .I filename
223: is given, the article will be read from the file of that name; otherwise
224: the article will be read from the standard input. An expiration date
225: need not be present and a reception date, if present, will be ignored.
226: .LP
227: When
228: .I inews
229: receives an article this way, it will check the history file to make sure
230: that the article is not already present, and it will make certain consistency
231: checks to make sure that the newsgroup names are legal and that the sys file
232: permits the article to be installed on the local machine. Once the article
233: passes those checks, it is installed in the appropriate directory on the
234: local machine. If the article fails those checks, it is installed in
235: newsgroup
236: .Ch junk
237: on the local machine. In any event,
238: .I inews
239: will then transmit the article to all systems that match in the sys file
240: and are not mentioned in the
241: .Ch Path:
242: field of the just-posted message. The details of this transmission are
243: determined by the contents of the sys file.
244: .LP
245: The third form (
246: .IB "inews \-C"
247: ) is for creating new newsgroups. The use of this feature is
248: limited to certain users such as the super-user or news administrator.
249: .SH FILES
250: .PD 0
251: .TP 25
252: /usr/spool/news/.sys.nnn
253: temporary articles
254: .TP 25
255: /usr/spool/news/.rnews
256: spooled articles not yet processed by rnews \-U
257: .TP 25
258: .RI /usr/spool/news/ newsgroups / article_no.
259: Articles
260: .TP 25
261: /usr/lib/news/active
262: List of known newsgroups and highest local article numbers in each.
263: .TP 25
264: /usr/lib/news/seq
265: Sequence number of last article
266: .TP 25
267: /usr/lib/news/history
268: List of all articles currently stored on this machine.
269: .TP 25
270: /usr/lib/news/sys
271: System subscription list
272: .TP 25
273: /usr/lib/news/distributions
274: Suggested distribution code names
275: .PD
276: .SH "SEE ALSO"
277: Mail(1),
278: binmail(1),
279: mailx(1),
280: checknews(1),
281: msgs(1),
282: postnews(1),
283: readnews(1),
284: vnews(1),
285: getdate(3),
286: news(5),
287: newsrc(5),
288: expire(8),
289: recnews(8),
290: sendnews(8),
291: uurec(8)
292: .SH AUTHORS
293: Matt Glickman
294: .br
295: Mark Horton
296: .br
297: Stephen Daniel
298: .br
299: Tom Truscott
300: .br
301: Rick Adams
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.