Re: [apps-discuss] Malformed mail guidance document (draft-ietf-appsawg-malformed-mail)

Alessandro Vesely <vesely@tana.it> Mon, 05 March 2012 10:44 UTC

Return-Path: <vesely@tana.it>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA1921F855F for <apps-discuss@ietfa.amsl.com>; Mon, 5 Mar 2012 02:44:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.65
X-Spam-Level:
X-Spam-Status: No, score=-4.65 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I-rvwFWfQZ4Q for <apps-discuss@ietfa.amsl.com>; Mon, 5 Mar 2012 02:44:38 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 124E321F852A for <apps-discuss@ietf.org>; Mon, 5 Mar 2012 02:44:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1330944276; bh=0fv1z78pY7x1eyqM/C8pPu7h0VJjaip93QSMkdLK25I=; l=908; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=DhYkzs5wQZRSursQd1qwx8UTp/Bv7SL/aV6qDCVSWosGQJUZGWaYE9CPr2qyTeClQ iucq5s8qRtt96Ge2qh/xAtOFVV7TggFSw8Z4Qq4ZG0ejlX4QU5/hEMNh/hGWRaY7Of fz+8X3Iyqp7oTtcLBzPX3xRLyNVq6pUrmS6uNms0=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Mon, 05 Mar 2012 11:44:36 +0100 id 00000000005DC039.000000004F549914.0000454B
Message-ID: <4F549914.2020907@tana.it>
Date: Mon, 05 Mar 2012 11:44:36 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: apps-discuss@ietf.org
References: <9452079D1A51524AA5749AD23E00392806D278@exch-mbx901.corp.cloudmark.com> <2183832.0qjo89hoBY@scott-latitude-e6320>
In-Reply-To: <2183832.0qjo89hoBY@scott-latitude-e6320>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: [apps-discuss] Malformed mail guidance document (draft-ietf-appsawg-malformed-mail)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 10:44:40 -0000

On 01/Mar/12 05:51, Scott Kitterman wrote:
> On Wednesday, February 29, 2012 07:56:41 PM Murray S. Kucherawy wrote:
>> Hi all,
> ...
>> When it reappears, I'd love to see some additional review comments,
>> especially the submission of new cases that should be included in the first
>> version.  I imagine there are many.
> 
> One thought that immediately came to mind is that it might be useful to 
> mention case changes in header fields in paragraph 7.  "Helpful" MTAs doing 
> this have been responsible for more than a few hard to troubleshoot DKIM 
> failures.

More non-malformation cases occur on MIME rewriting.  It may be
helpful to encourage tool developers to stick to the original choice
of token / quoted-string in MIME parameters (format="flowed" vs.
format=flowed see http://tools.ietf.org/html/rfc2045#section-5.1 )
as well as keeping the original boundaries, if at all possible.