Re: SMTP RFC: "MUST NOT" change or delete Received header

John C Klensin <john-ietf@jck.com> Mon, 31 March 2014 12:41 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5AF71A083F for <ietf@ietfa.amsl.com>; Mon, 31 Mar 2014 05:41:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xhh_fzA9grtV for <ietf@ietfa.amsl.com>; Mon, 31 Mar 2014 05:41:21 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C597E1A083E for <ietf@ietf.org>; Mon, 31 Mar 2014 05:41:20 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WUbWS-0000I3-On; Mon, 31 Mar 2014 08:41:04 -0400
Date: Mon, 31 Mar 2014 08:40:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Cridland <dave@cridland.net>, Randy Bush <randy@psg.com>
Subject: Re: SMTP RFC: "MUST NOT" change or delete Received header
Message-ID: <08FB96C9740FB84D42C12290@JcK-HP8200.jck.com>
In-Reply-To: <CAKHUCzyznOsDBEi7KYipNrEpKLgBO6MfAqS=g0Nm2dGpbtgMvg@mail.gmail.com>
References: <20140330151432.2721.qmail@joyce.lan> <A3DE810811F791EDC532BDFB@JcK-HP8200.jck.com> <m28urr9rcp.wl%randy@psg.com> <CAKHUCzyznOsDBEi7KYipNrEpKLgBO6MfAqS=g0Nm2dGpbtgMvg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/IRiplw88eRIN7aGSDZBao6sxYhw
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Mar 2014 12:41:23 -0000

--On Monday, March 31, 2014 08:36 +0100 Dave Cridland
<dave@cridland.net> wrote:

> On 31 March 2014 00:52, Randy Bush <randy@psg.com> wrote:
> 
>> the truth is, i have not used received: headers to
>> authenticate/debug [0] since yesterday.  but it's not yet
>> 09:00, so there is still time today.

> I'm assuming you realise that nobody is arguing that all
> received header fields be stripped?
> 
> The problem I've run into is generally machine [~auto]
> submitted email, where the network itself is "sensitive"
> (let's pretend it's a big bank), and the administrators don't
>...
> If there's a problem with the mail, the big bank can track
> down what happened easily enough, and you can point your
> finger at the correct big bank.

As I pointed out earlier, this is precisely the case for which
there is language in the message submission spec.  It has
nothing to do with SMTP across the network.

   john