Re: [apps-discuss] Comments on Malformed Message BCP draft

Keith Moore <moore@network-heretics.com> Fri, 15 April 2011 17:38 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: apps-discuss@ietfc.amsl.com
Delivered-To: apps-discuss@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 3B5B6E067E for <apps-discuss@ietfc.amsl.com>; Fri, 15 Apr 2011 10:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ocPH1JuWlaz9 for <apps-discuss@ietfc.amsl.com>; Fri, 15 Apr 2011 10:38:53 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfc.amsl.com (Postfix) with ESMTP id E65F8E0678 for <apps-discuss@ietf.org>; Fri, 15 Apr 2011 10:38:52 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 519CC22585; Fri, 15 Apr 2011 13:38:52 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Fri, 15 Apr 2011 13:38:52 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=gVolGe0B/RpBt0ApHGJIZpy+PLk=; b=ZtKYFilYYikUPcHCKJN+VYKhPJd5jNJ5kgro4TWA/HGOp8FLVPOYjPIJrC0H4ihdlVHVGjgaZ3jcSNk6mGbXKnuzdFQRJ+SC6IpqLmvjn51yosZBA191YXe2U3ybI+nYRYRc9okZm0JJ+4Ar2gk3b6BBeuRnjgvqUKyeNLrCZC8=
X-Sasl-enc: 3JcWBXk1iJZwDwnffh53p4ThPetGZJjNU6wZnHvuyhLT 1302889131
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id ADDD84033B1; Fri, 15 Apr 2011 13:38:51 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4DA8542F.9040003@tana.it>
Date: Fri, 15 Apr 2011 13:38:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5FBD6703-40D0-482F-B6A5-4C17EC88B9D3@network-heretics.com>
References: <F5833273385BB34F99288B3648C4F06F1343319E22@EXCH-C2.corp.cloudmark.com> <CEDB17EC-80CE-49B5-91C1-FBCB0449BBA5@network-heretics.com> <4DA8542F.9040003@tana.it>
To: Alessandro Vesely <vesely@tana.it>
X-Mailer: Apple Mail (2.1084)
Cc: ietf-822 <ietf-822@imc.org>, apps-discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Comments on Malformed Message BCP draft
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: Fri, 15 Apr 2011 17:38:58 -0000

On Apr 15, 2011, at 10:20 AM, Alessandro Vesely wrote:

> On 15/Apr/11 14:50, Keith Moore wrote:
>> I'm strongly opposed to MTAs "fixing" malformed messages (other than
>> submission servers fixing a small number of known problems caused by
>> broken mail clients).
> 
> +1, standardizing fixes implies a standard status for malformed messages.
> 
>> If an MTA does anything at all when it thinks that a message is
>> malformed, it should be to bounce it _exactly as it received it
>> originally_.
> 
> Bouncing is not quite practical.  Rejecting is more viable, but it has
> to be coordinated with any backup MX.

Bouncing is absolutely what should happen if the message is merely malformed.  Otherwise, the sender has no idea that his message didn't arrive (or why), and nothing will ever be done to fix the problem.

Keith