Re: [ietf-smtp] broken signatures, was Curious

Michael Richardson <mcr@sandelman.ca> Wed, 22 July 2020 18:33 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8743F3A0825 for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 11:33:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 9yqGsoXq0utR for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 11:33:09 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3B903A081C for <ietf-smtp@ietf.org>; Wed, 22 Jul 2020 11:33:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id E63C838A20; Wed, 22 Jul 2020 14:12:40 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id jHtM1muMxpgJ; Wed, 22 Jul 2020 14:12:38 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 472C338991; Wed, 22 Jul 2020 14:12:38 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 89FE11CC; Wed, 22 Jul 2020 14:33:04 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: "John Levine" <johnl@taugh.com>
cc: ietf-smtp@ietf.org
In-Reply-To: <20200722172939.891DE1D620A4@ary.qy>
References: <20200722172939.891DE1D620A4@ary.qy>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <30736.1595442784.1@localhost>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 22 Jul 2020 14:33:04 -0400
Message-ID: <30737.1595442784@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/LqwQygcvkXu86NHMoxvAcNBB2Ts>
Subject: Re: [ietf-smtp] broken signatures, was Curious
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2020 18:33:11 -0000

John Levine <johnl@taugh.com> wrote:
    > In article <6464.1595370330@localhost> you write:
    >> If the message goes through "mailman" or some other processor, then it seems
    >> like it ought to rip pretty much every X-FOO out.  The rest of them ought to
    >> be known headers at the time the processor was written, and it ought to
    >> either know what they are, or it does not, in which case, it shouldn't pass
    >> on things it does not know about.

    > That's not gpod advice. The point of the mystery headers is to tell
    > what happened to the message during its trip, and the part of the trip
    > before it hit the list manager is as important as the part after. When
    > I'm trying to figure out why something undesirable leaked through the
    > list manager, I need the original headers to figure out what happened.

Right. You need the standard "Received:" lines, which would be a known
header at this point, so it would remain.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [