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

"Murray S. Kucherawy" <msk@cloudmark.com> Wed, 14 March 2012 19:49 UTC

Return-Path: <msk@cloudmark.com>
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 1951721F8629 for <apps-discuss@ietfa.amsl.com>; Wed, 14 Mar 2012 12:49:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level:
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 FI9r1kwqfGKw for <apps-discuss@ietfa.amsl.com>; Wed, 14 Mar 2012 12:49:05 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 66FA221F8617 for <apps-discuss@ietf.org>; Wed, 14 Mar 2012 12:48:59 -0700 (PDT)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Wed, 14 Mar 2012 12:48:58 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Thread-Topic: [apps-discuss] Malformed mail guidance document (draft-ietf-appsawg-malformed-mail)
Thread-Index: AQHM92cFazIv3ot2y0mMzxumQABBTpZqR4nQ
Date: Wed, 14 Mar 2012 19:48:58 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392808B2E2@exch-mbx901.corp.cloudmark.com>
References: <9452079D1A51524AA5749AD23E00392806D278@exch-mbx901.corp.cloudmark.com> <2183832.0qjo89hoBY@scott-latitude-e6320>
In-Reply-To: <2183832.0qjo89hoBY@scott-latitude-e6320>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 14 Mar 2012 19:49:06 -0000

> -----Original Message-----
> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Scott Kitterman
> Sent: Wednesday, February 29, 2012 8:52 PM
> To: apps-discuss@ietf.org
> Subject: Re: [apps-discuss] Malformed mail guidance document (draft-ietf-appsawg-malformed-mail)
> 
> 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.

That's certainly a concern but I'm not sure it's on topic for this draft.  Altering header field name cases is not strictly a malformation, it's a questionable handling choice that doesn't really alter the semantics or interpretation of the message in a meaningful way.  And DKIM does have a way (relaxed header canonicalization mode) to deal with it.

A separate document that lists annoying MTA habits which don't actually result in non-compliant messages would quite possibly be a lot larger than this one.  :-)

-MSK