|
|
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 1 "February 2, 1986" ! 13: .ds ]W Version B 2.10.3 ! 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 \-a " approvedby" ! 33: ] ! 34: .PP ! 35: .BI "inews \-p " filename ! 36: .PP ! 37: .BI "inews \-C " newsgroup ! 38: .SH DESCRIPTION ! 39: .I Inews ! 40: submits news articles to the USENET news network. ! 41: It is a raw interface called by news-posting programs. ! 42: You should not use ! 43: .I inews ! 44: directly. Most people use ! 45: .IR postnews (1) ! 46: to post news articles. Ultimately, of course, ! 47: .IR postnews (1) ! 48: and other news-posting programs call inews to do the actual submission. ! 49: .PP ! 50: The first form (no ! 51: .BI \-p ! 52: or ! 53: .BI \-C ! 54: options) is for submitting ordinary articles. ! 55: The body of the article will be read from the standard input. A ! 56: .I title ! 57: ( ! 58: .Ch Subject: ! 59: field) ! 60: must be specified (there is no default). ! 61: Each article is posted to one or more newsgroups. ! 62: .B \-n ! 63: flag is omitted, the list ! 64: will default to something like ! 65: .BR general . ! 66: If you wish to submit an article to multiple newsgroups, the ! 67: .I newsgroups ! 68: must be separated by commas and/or spaces. ! 69: .PP ! 70: The ! 71: .B \-e ! 72: flag is used to override the default expiration date. This is seldom ! 73: used. ! 74: .PP ! 75: The ! 76: .B \-f ! 77: flag specifies the article's sender. Without this flag, the sender ! 78: defaults to the user's name. ! 79: If ! 80: .B \-f ! 81: is specified, the real sender's name will be included as a ``Sender:'' line ! 82: to prevent forged articles. ! 83: .PP ! 84: The ! 85: .B \-d ! 86: flag allows you to specify the maximum geographic distribution of your ! 87: article; for example, a distribution of ! 88: .Ch aus ! 89: limits distribution to Australia, and a distribution of ! 90: .Ch nj ! 91: limits distribution to New Jersey. There is no way to send a message from ! 92: California for distribution only in New Jersey\(emyour machine must be in the ! 93: distribution that you ask for. ! 94: .PP ! 95: The ! 96: .B \-F ! 97: flags is used to attach a list of related articles that this ! 98: message references; it creates the ! 99: .Ch In-reply-to: ! 100: field of the posted article. ! 101: .PP ! 102: The ! 103: .B \-o ! 104: is used to override the default organization name. ! 105: .PP ! 106: The ! 107: .B \-M ! 108: and ! 109: .B \-a ! 110: flags are to be used only by the moderator of a moderated newsgroup. The ! 111: .B \-M ! 112: flag causes the ! 113: .Ch From: ! 114: and ! 115: .Ch Path: ! 116: fields of the article to be set to correct values for a moderated newsgroup. ! 117: The ! 118: .B \-a ! 119: flag is used to add an ! 120: .Ch Approved: ! 121: line to the header. Note that if the ! 122: .B \-M ! 123: flag is used in conjuction with the ! 124: .B \-h ! 125: flag (see below), the article headers must not have a ! 126: .Ch Path: ! 127: field in them already. ! 128: .PP ! 129: The ! 130: .B \-h ! 131: flag specifies that headers are present at the beginning of the ! 132: article, and these headers should be included with the article ! 133: header instead of as text. Everything before the first blank line in the ! 134: article is taken as a header field, and everything after that blank line is ! 135: taken to be part of the body of the message. ! 136: (This mechanism can be used to edit headers and supply additional ! 137: nondefault headers, but not to specify certain information, ! 138: such as the sender and article ID, that ! 139: .I inews ! 140: itself generates.) ! 141: .I Inews ! 142: will ignore nonstandard and misspelled header fields entered with the \-h ! 143: option. ! 144: .LP ! 145: When posting an article ! 146: .I inews ! 147: checks the environment for certain information about the sender. If ! 148: an environment variable ! 149: .B NAME ! 150: is defined, ! 151: .I inews ! 152: uses its value as the full name of the poster. If ! 153: .B NAME ! 154: is not defined, ! 155: .I inews ! 156: checks ! 157: \kx\f2$HOME\fP\h'|\nxu+2u'\f2$HOME/.name\fP ! 158: is checked and if it exists, its contents are used as the full name. ! 159: Otherwise, the system value (often in ! 160: .IR /etc/passwd ) ! 161: is used. ! 162: This is useful if the system value cannot be set, or when ! 163: more than one person uses the same login. ! 164: If the environment variable ! 165: .B ORGANIZATION ! 166: is defined, then ! 167: .I inews ! 168: uses its value instead of the system ! 169: default organization name. If its value begins with a ! 170: .Ch / , ! 171: then it is taken to be a file name, and ! 172: .I inews ! 173: takes the name of the organization from the contents of the file. ! 174: This is useful when a person uses a guest login and is ! 175: not primarily associated with the organization that owns the machine. ! 176: .LP ! 177: The second form ( ! 178: .BI "inews \-p" ! 179: ) is used for receiving articles from other machines. If ! 180: .I filename ! 181: is given, the article will be read from the file of that name; otherwise ! 182: the article will be read from the standard input. An expiration date ! 183: need not be present and a reception date, if present, will be ignored. ! 184: .LP ! 185: When ! 186: .I inews ! 187: receives an article this way, it will check the history file to make sure ! 188: that the article is not already present, and it will make certain consistency ! 189: checks to make sure that the newsgroup names are legal and that the sys file ! 190: permits the article to be installed on the local machine. Once the article ! 191: passes those checks, it is installed in the appropriate directory on the ! 192: local machine. If the article fails those checks, it is installed in ! 193: newsgroup ! 194: .Ch junk ! 195: on the local machine. In any event, ! 196: .I inews ! 197: will then transmit the article to all systems that match in the sys file ! 198: and are not mentioned in the ! 199: .Ch Path: ! 200: field of the just-posted message. The details of this transmission are ! 201: determined by the contents of the sys file. ! 202: .LP ! 203: The third form ( ! 204: .IB "inews \-C" ! 205: ) is for creating new newsgroups. The use of this feature is ! 206: limited to certain users such as the super-user or news administrator. ! 207: Please note that ! 208: .I "inews \-C" ! 209: creates a newsgroup \fIon all machines that the message reaches\fR, and not ! 210: just the local machine. If you accidentally create a newsgroup with ! 211: .I "inews \-C," ! 212: without specifying a distribution, it will be created worldwide. If you want ! 213: to create a newsgroup locally on your machine, it is safer to edit the active ! 214: file by hand. ! 215: .LP ! 216: If the file ! 217: .I /usr/lib/news/recording ! 218: is present, it is taken as a list of ! 219: \&\*(Lqrecordings\*(Rq to be shown to users posting news. ! 220: (This is named after the recording you hear when you dial ! 221: .Ch information ! 222: in some parts of the U.S., asking you to stop and think if you really want do ! 223: do this, but not actually preventing you.) ! 224: The recording file contains lines of the form: ! 225: .PP ! 226: newsgroup-specifier \fB\s-2TAB\s0\fP filename ! 227: .PP ! 228: for example: ! 229: .PP ! 230: net.all net.recording ! 231: .br ! 232: local.all,!local.test local.recording ! 233: .PP ! 234: Any user posting an article to a newsgroup matching the pattern on ! 235: the left will be shown the contents of the file on the right. ! 236: The file is found in the ! 237: .B LIB ! 238: directory (often ! 239: .IR /usr/lib/news ). ! 240: The user is then told to hit \s-2DEL\s0 to abort or \s-2RETURN\s0 to proceed. ! 241: The intent of this feature is to help companies keep proprietary ! 242: information from accidently leaking out. ! 243: .SH FILES ! 244: .PD 0 ! 245: .TP 25 ! 246: /usr/spool/news/.sys.nnn ! 247: temporary articles ! 248: .TP 25 ! 249: .RI /usr/spool/news/ newsgroups / article_no. ! 250: Articles ! 251: .TP 25 ! 252: /usr/lib/news/active ! 253: List of known newsgroups and highest local article numbers in each. ! 254: .TP 25 ! 255: /usr/lib/news/seq ! 256: Sequence number of last article ! 257: .TP 25 ! 258: /usr/lib/news/history ! 259: List of all articles currently stored on this machine. ! 260: .TP 25 ! 261: /usr/lib/news/sys ! 262: System subscription list ! 263: .TP 25 ! 264: /usr/lib/news/distributions ! 265: Suggested distribution code names ! 266: .PD ! 267: .SH "SEE ALSO" ! 268: Mail(1), ! 269: binmail(1), ! 270: mailx(1), ! 271: checknews(1), ! 272: msgs(1), ! 273: postnews(1), ! 274: readnews(1), ! 275: vnews(1), ! 276: getdate(3), ! 277: news(5), ! 278: newsrc(5), ! 279: expire(8), ! 280: recnews(8), ! 281: sendnews(8), ! 282: uurec(8) ! 283: .SH AUTHORS ! 284: Matt Glickman ! 285: .br ! 286: Mark Horton ! 287: .br ! 288: Stephen Daniel ! 289: .br ! 290: Tom Truscott ! 291: .br ! 292: Rick Adams
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.