Re: Syntax validation of articles by injecting agents

"Charles Lindsey" <chl@clerew.man.ac.uk> Tue, 05 January 2010 12:14 UTC

Return-Path: <owner-ietf-usefor@mail.imc.org>
X-Original-To: ietfarch-usefor-archive@core3.amsl.com
Delivered-To: ietfarch-usefor-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 11EF33A688B for <ietfarch-usefor-archive@core3.amsl.com>; Tue, 5 Jan 2010 04:14:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.022
X-Spam-Level:
X-Spam-Status: No, score=-3.022 tagged_above=-999 required=5 tests=[AWL=3.024, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UPCYBzy2oXln for <ietfarch-usefor-archive@core3.amsl.com>; Tue, 5 Jan 2010 04:14:25 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id A72133A6850 for <usefor-archive@ietf.org>; Tue, 5 Jan 2010 04:14:20 -0800 (PST)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o05CC6Dq056765 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Jan 2010 05:12:06 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id o05CC6Ht056764; Tue, 5 Jan 2010 05:12:06 -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 v-smtp-auth-relay-4.gradwell.net (v-smtp-auth-relay-4.gradwell.net [79.135.125.43]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o05CC4kY056758 for <ietf-usefor@imc.org>; Tue, 5 Jan 2010 05:12:05 -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 v-smtp-auth-relay-4.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.290) id 4b432c91.340d.74 for ietf-usefor@imc.org; Tue, 5 Jan 2010 12:12:01 +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 o05CC3eJ020687 for <ietf-usefor@imc.org>; Tue, 5 Jan 2010 12:12:03 GMT
Received: (from news@localhost) by clerew.man.ac.uk (8.13.7/8.13.7/Submit) id o05CC3Au020681 for ietf-usefor@imc.org; Tue, 5 Jan 2010 12:12:03 GMT
To: ietf-usefor@imc.org
Xref: clerew local.usefor:25210
Path: clerew!chl
From: Charles Lindsey <chl@clerew.man.ac.uk>
Subject: Re: Syntax validation of articles by injecting agents
Message-ID: <KvrvuC.F57@clerew.man.ac.uk>
X-Newsreader: NN version 6.5.2 (NOV)
References: <35100640C1C848E4A3267B6B4FD3B9ED@Iulius> <87aawzdj5e.fsf@windlord.stanford.edu> <Kvq2LJ.J2r@clerew.man.ac.uk> <873a2lz4dk.fsf@windlord.stanford.edu>
Date: Tue, 05 Jan 2010 11:56:36 +0000
Lines: 60
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>

In <873a2lz4dk.fsf@windlord.stanford.edu> Russ Allbery <rra@stanford.edu> writes:

>"Charles Lindsey" <chl@clerew.man.ac.uk> writes:

>> Eh? How does it imply that? If there are no Content-* headers, then
>> there is no requirement for MIME-Version.

>See Julien's post:

>| NN for instance does not generate MIME-Version: header fields
>| although "user agents MUST meet the definition of MIME conformance"
>| ("a mail user agent that is MIME-conformant MUST always generate
>| a "MIME-Version: 1.0" header field in any message it creates").
>| I believe this sentence applies to news user agents too, otherwise
>| a reference to MIME is useless.

>The first quoted statement is from RFC 5536 section 2.3, with an
>accompanying reference to RFC 2049.  The second quoted statement is from
>RFC 2049 section 2.

But I don't think RFC 2049 ever intended to imply that MIME-Version was
needed for a message that did not actually use any of the MIME features.
As evidence of that, I can cite RFC 2047, which states:

   (4) A MIME-Version header field is NOT required to be present for
       'encoded-word's to be interpreted according to this
       specification.  One reason for this is that the mail reader is
       not expected to parse the entire message header before displaying
       lines that may contain 'encoded-word's.

>Now that I think about it, though, this only places a requirement on the
>user agent.  It doesn't require that the server reject the message, so I
>think the original problem isn't actually that significant of a problem.
>MIME-compliant agents, such as injecting agents, are allowed to accept
>non-MIME messages.

Exactly.

>> But aren't injecting agents allowed to remove a Path header that is
>> received?


>Injecting agents are specifically discouraged (SHOULD NOT) from fixing or
>remove any header fieldss other than Path.

Which is fair enough, but gives leeway for Paths to be removed, which
copes with the particular problem that was raised. For sure, many
injecting agents DO remove it regardless, because they regard it as an
"infringement of their rights" :-) .

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131            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