Re: Injecting agents and From (was: Re: Protocol changes in draft-allbery-usefor-usepro-00)

"Charles Lindsey" <chl@clerew.man.ac.uk> Wed, 03 January 2007 05:14 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H1ySW-00057Y-4w for usefor-archive@lists.ietf.org; Wed, 03 Jan 2007 00:14:40 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H1ySQ-00012r-B7 for usefor-archive@lists.ietf.org; Wed, 03 Jan 2007 00:14:40 -0500
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l035CXkn063924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Jan 2007 22:12:33 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l035CXZ3063915; Tue, 2 Jan 2007 22:12:33 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f
Received: from lon-mail-4.gradwell.net (lon-mail-4.gradwell.net [193.111.201.130]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l035CU44063862 for <ietf-usefor@imc.org>; Tue, 2 Jan 2007 22:12:31 -0700 (MST) (envelope-from news@clerew.man.ac.uk)
Received: from [80.175.135.89] ([80.175.135.89] helo=clerew.man.ac.uk country=GB ident=postmaster*pop3$clerew&man*ac#uk) by lon-mail-4.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.237) id 459b3b3a.2455.6 for ietf-usefor@imc.org; Wed, 3 Jan 2007 05:12:26 +0000 (envelope-sender <news@clerew.man.ac.uk>)
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id l035CPcW018048 for <ietf-usefor@imc.org>; Wed, 3 Jan 2007 05:12:25 GMT
Received: (from news@localhost) by clerew.man.ac.uk (8.13.7/8.13.7/Submit) id l035CPRK018045 for ietf-usefor@imc.org; Wed, 3 Jan 2007 05:12:25 GMT
To: ietf-usefor@imc.org
Xref: clerew local.usefor:23998
Path: clerew!chl
From: Charles Lindsey <chl@clerew.man.ac.uk>
Subject: Re: Injecting agents and From (was: Re: Protocol changes in draft-allbery-usefor-usepro-00)
Message-ID: <JB95By.KzA@clerew.man.ac.uk>
X-Newsreader: NN version 6.5.2 (NOV)
References: <JA8C4p.Anu@clerew.man.ac.uk> <873b7i9b2m.fsf@windlord.stanford.edu> <JAHJs5.FHC@clerew.man.ac.uk> <87odpmgzp3.fsf_-_@windlord.stanford.edu>
Date: Tue, 02 Jan 2007 17:45:34 +0000
Lines: 103
Sender: owner-ietf-usefor@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-usefor/mail-archive/>
List-Unsubscribe: <mailto:ietf-usefor-request@imc.org?body=unsubscribe>
List-ID: <ietf-usefor.imc.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86

In <87odpmgzp3.fsf_-_@windlord.stanford.edu> Russ Allbery <rra@stanford.edu> writes:

>Charles Lindsey <chl@clerew.man.ac.uk> writes:
>> Russ Allbery <rra@stanford.edu> writes:
>>> Charles Lindsey <chl@clerew.man.ac.uk> writes:

>>>> 3. [-1] (3.3.1,3.4,3.9.2) From not omittable in proto-article

>>>> There is existing usage where the injecting agent fills in From header
>>>> (not possible in NNTP, of course)

>>> Intentional change.

>>> What injecting agent supports this?

>> INN apparently (see below).

>> Newsreaders such as rn, trn, nn, and others of that generation had (and
>> still have) the capability to interact directly with the newspool
>> (either on the same host, or more likely NFS mounted from some server)
>> rather than going via NNTP (which did not exist when they were first
>> written). They injected articles by calling a program 'inews' which, in
>> the absence of an explicit From:, assumed the poster was the user who
>> had called 'inews'.

>inews as distributed with INN or the common news readers is a (part of a)
>posting agent, not an injecting agent.

Ah! So it boils down to a matter off semantics. Surely, when the first
newsreaders were written (RN and earlier, before NNTP came on the scene),
their final act when posting an article was to hand it off to 'inews',
which came with the software of the server (which would be BNews in those
days). What does the 'i' in 'inews' stand for, if not for 'inject'. For
sure, people using UNIX never configured individual pieces of software
with their own name and id, because they naturally assumed that the system
would pick it up from /etc/passwd and the fact that they were logged in as
their own id.

>  You can see this by observing what
>actions it takes and what agent it talks to.  It sends messages to an
>injecting agent via POST and expects that agent to do the injection;

Not so. 'inews' existed long before the POST command was invented. AFAICT
from the O'Reilly Book, which was the definitive tutorial on administering
Usenet from 1986 onwards, the principal interfaces to BNews were 'inews'
and 'rnews'. Inews had an amazing collection of parameters (you could
even create groups locally with it or issue control messages).

>Our agent distinctions are largely based on how INN and similar news
>servers work.  C News, being a much earlier implementation, may not have
>the same distinctions, or they may be much less clear.  Some
>implementations written prior to our standard will combine different
>agents into one program, so it's possible that in C News inews combines
>functions of a posting agent and an injecting agent.

In CNews, 'inews' IS the injecting agent, which performs all the relevant
checks, sends it to the moderator if needed, and otherwise puts it into
the input queue alongside stuff received via 'rnews', whence it eventually
gets stored locally and relayed onwards. If stuff arrives via the NNTP
POST command, then it merely generates a call on 'inews'. It is certainly
not regarded as a posting agent (a crude posting agent 'readnews' is
provided - not really suited to serious newsreading) and there is a script
'postnews' which prompts you for Newsgroup and Subject, lets you use your
favourite editor to construct the article (adding other headers, even
From:, as you wish), and finally calls 'inews'. So 'inews' is not regarded
in any sense as a posting agent, although it would likely be called
directly by scripts which generated articles automatically (such as
modbots).

For sure, fashions have changed since then. But I am sure there are still
people using updated versions of those early newsreaders (such as nn and
trn) which still call inews, taking advantage of the automatic fillng in
of From, and those will all work happily with Bnews, Cnews, INN, and for
all I know any other newsservers which provide the 'inews' interface.

So there is no reason not to recognise that, even if the usage is not so
common as it once was. The wording I put into USEPRO (when discussing
headers that could be omitted from proto-articles) was:

"...(and even From if the particular injecting agent can derive that
information from other sources.)"

which seems to me an accurate description of the situation I have
described. I see no reason why a similar wording should not continue to be
used.

>INN's inews used to redundantly perform a few (although not all by any
>means) of the functions of an injecting agent, such as mailing posts to
>the moderators of moderated newsgroups.

Sure, 'inews' used to have all sorts of Bells and Whistles, and even CNews
provides a cutdown version 'injnews' which it recommends for routine use.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5