IETF Logo Mail Archive

Re: Syntax validation of articles by injecting agents

Russ Allbery <rra@stanford.edu> Thu, 07 January 2010 19:12 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 5471728C0F1 for <ietfarch-usefor-archive@core3.amsl.com>; Thu, 7 Jan 2010 11:12:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.038
X-Spam-Level:
X-Spam-Status: No, score=-5.038 tagged_above=-999 required=5 tests=[AWL=1.008, 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 85Myddxo4LqP for <ietfarch-usefor-archive@core3.amsl.com>; Thu, 7 Jan 2010 11:12:09 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 489B128C1B8 for <usefor-archive@ietf.org>; Thu, 7 Jan 2010 11:12:07 -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 o07JAQmx050249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Jan 2010 12:10:28 -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 o07JALtx050247; Thu, 7 Jan 2010 12:10:22 -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 smtp.stanford.edu (smtp5.Stanford.EDU [171.67.219.85]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o07JAFvX050232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-usefor@imc.org>; Thu, 7 Jan 2010 12:10:16 -0700 (MST) (envelope-from eagle@windlord.stanford.edu)
Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 0100418FC86 for <ietf-usefor@imc.org>; Thu, 7 Jan 2010 11:10:13 -0800 (PST)
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134]) by smtp.stanford.edu (Postfix) with ESMTP id 4DB2518FA93 for <ietf-usefor@imc.org>; Thu, 7 Jan 2010 11:10:12 -0800 (PST)
Received: by windlord.stanford.edu (Postfix, from userid 1000) id 48C212589A; Thu, 7 Jan 2010 11:10:12 -0800 (PST)
From: Russ Allbery <rra@stanford.edu>
To: ietf-usefor@imc.org
Subject: Re: Syntax validation of articles by injecting agents
In-Reply-To: <20100107175926.38C6A24232@panix5.panix.com> (Seth's message of "Thu, 7 Jan 2010 12:59:26 -0500 (EST)")
Organization: The Eyrie
References: <35100640C1C848E4A3267B6B4FD3B9ED@Iulius> <87aawzdj5e.fsf@windlord.stanford.edu> <Kvq2LJ.J2r@clerew.man.ac.uk> <873a2lz4dk.fsf@windlord.stanford.edu> <KvrvuC.F57@clerew.man.ac.uk> <7Ey9XHElGzQLFAQU@highwayman.com> <Kvu3Ht.BG1@clerew.man.ac.uk> <FD8718C15E1440E993AEFBF849934D82@Iulius> <KvvJz8.9EA@clerew.man.ac.uk> <20100107175926.38C6A24232@panix5.panix.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Date: Thu, 07 Jan 2010 11:10:12 -0800
Message-ID: <87y6k9g297.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

Seth <sethb@panix.com> writes:
> "Charles Lindsey" <chl@clerew.man.ac.uk> wrote:

>> Well that implies, to me, that if the message contains nothing that
>> purports to be "composed in compliance with this document", then there
>> is no obligation to inlcude the MIME-Version.

> Even if it is composed in compliance with the document, there is no
> obligation to *assert* that fact.

Actually, yes, there is.  I really don't see how RFC 2049 could possibly
be any clearer.

|    A mail user agent that is MIME-conformant MUST:
| 
|     (1)   Always generate a "MIME-Version: 1.0" header field in
|           any message it creates.

I don't think there's much need to go farther afield into other MIME
documents when RFC 2049 is as clear as crystal and when we explicitly
stated in RFC 5536 that all user agents complying with RFC 5536 MUST meet
the definition of MIME conformance in RFC 2049.

(This does not, as pointed out elsewhere in the thread, imply that servers
have to reject messages generated by non-conformant user agents.)

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

v2.23.0 | Report a Bug | By Email