INJNEWS(1)

NAME
injnews, inews - `user-friendly' news-posting front-ends for relaynews

SYNOPSIS
injnews [ -N ] [ -A ] [ -V ] [ -x excluded-site ]
inews [ -h ] [ -N ] [ -A ] [ -V ] [ -x excluded-site ] [ -W ] [ -M ] [ -a Approved:-contents ] [ -c Control:-contents ] [ -d Distribution:-contents ] [ -e Expires:-contents ] [ -f From:-contents ] [ -n Newsgroups:-contents ] [ -o Organization:-contents ] [ -r Reply-To:-contents ] [ -t Subject:-contents ] [ -C newsgroup ] [ -F References:-contents ] [ file ... ]
inews -p [ file ... ]

DESCRIPTION
Injnews and inews massage news articles to make them conform to DARPA RFC 1036, then inject them into the news flow. Injnews is the preferred interface. Inews is slower but handles all the old B News options, primarily for the benefit of old news readers.

Injnews injects an article, found on standard input, into the news flow, installing it locally and broadcasting it (if appropriate) onto the network. Injnews assumes the presence of at least Subject: and Newsgroups: headers in the article, then adds and alters headers, notably Message-ID:, From: and Path:, deletes invisible characters, and appends the first four lines of $HOME/.signature, if any, to the article, and hands the resulting article to relaynews(8), provided the newsgroup(s) are unmoderated. If any of the groups are moderated, the article will instead be mailed to the moderator of one of the moderated newsgroups in the Newsgroups: header. -N suppresses posting and produces on standard output the article that would have otherwise been posted; the resultant article will have been checked for illegalities as usual and will be suitable as input to relaynews(8). -A waits until enough space becomes free in /usr/spool/news. -V causes relaynews to emit a log file line on stdout after processing is complete, by having relaynews not redirect stdout and stderr to /usr/lib/news/log and /usr/lib/news/errlog. -x prevents transmission to site excluded-site.

Inews does everything that injnews does, plus some backwardly-compatible things. The article is read from files or standard input if none. Normal usage is inews -h, which assumes that the input article starts with headers; otherwise it starts the article body and the B News options described below must be given to supply the headers. -W waits for relaynews to complete, instead of running it in the background and not waiting. -M does nothing, for B News compatibility. The rest of the options are inherited from B News and exist only for backward-compatibility with news readers. They should not be used by humans, as they are equivalent to adding the obvious headers, with two small twists: -f generates From: From:-contents which generates a Sender: user@host header if there is no Sender: header in the input, and -C tells you to use addgroup for local group creations and tells you what to feed to injnews for global ones.

inews -p files is exactly equivalent to invoking relaynews -r files , where files may be an empty list; there is no automatic recovery of the input file(s) in case of errors, full disks or other problems.

EXAMPLES
injnews <article
Post article to Usenet.

injnews -N <article >/dev/null
Check article for obvious errors.

FILES
/usr/lib/news/active
    contains (un)moderated flag
/usr/lib/news/mailpaths
    routes to moderators, Internet gateway
/usr/lib/news/mailname
    the name of this cluster of machines for purposes of mail, including any domain
/usr/lib/news/server
    the hostname of this cluster's server
/usr/lib/news/whoami
    the name of this cluster for purposes of news
$HOME/.signature
    your name and network addresses (no line-printer graphics, please)
$HOME/dead.article
    saved article in case of errors or problems
/tmp/in*
    temporaries

SEE ALSO
mail(1), news(5), newsaux(8), relaynews(8)
DARPA RFC 1036

HISTORY
Written by Geoff Collyer as part of the C news project.

BUGS
Inews should be unnecessary; its only useful function is adding Message-ID: headers and most novices use Pnews, which could invoke relaynews directly.

Inews is a shell script currently and can fail if any of the underlying Unix tools fail. This typically happens with very long input lines.