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

John R Levine <johnl@taugh.com> Thu, 23 July 2020 00:33 UTC

Return-Path: <johnl@taugh.com>
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 27A053A0A86 for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 17:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=MTE3vlj0; dkim=pass (1536-bit key) header.d=taugh.com header.b=l5pOAcLV
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 6YZAg1QRX_ch for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 17:33:06 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 824213A0A84 for <ietf-smtp@ietf.org>; Wed, 22 Jul 2020 17:33:06 -0700 (PDT)
Received: (qmail 95851 invoked from network); 23 Jul 2020 00:33:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=17668.5f18dac0.k2007; i=johnl-iecc.com@submit.iecc.com; bh=ANbEW2UnInd4artKN3zGp0k1Nm5y/n174TbhkablAK8=; b=MTE3vlj0utNari6bH81EAq4KzT3BP3TaDNIqxUsob3CYuy2F/8Z1Ujjq9bTR29svTGc8saQYoqaSL9lBWEowCBQu+HevMKeJg8YT69vbo6ilouheepij3NejGwqxyHHvZcm4UFIS3381JEmGNQ9TPuFWjCVoXzWkcQCRUI3rSGah28+7gI4kr8Kd+97Fq5XVmQwlb5+tDC6TdIBMkbZa0MAidxuqsCAmIngLSAcDEcEE2Al+bXEIGp3uexIALiEZ
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=17668.5f18dac0.k2007; olt=johnl-iecc.com@submit.iecc.com; bh=ANbEW2UnInd4artKN3zGp0k1Nm5y/n174TbhkablAK8=; b=l5pOAcLVnazY3UVt+hx76+fM/G+IyXkWFjyIYRcgEWJsZfUXgO+B95v6y8ufq8kpXKF9RzSezGL8eRhk75Rwe2AB4jCS/DlFWsQn9ANkL/BufPzpyeLV7wOfy2YOJv1w5ehKHSFobq++JvX/ua7r0x6vVuIpe70X5jB4AiuAb9kmVhnM4aBUhoo4buEZu/LatuiI1WoqZQYSSJm3W8uHB8Da2oqysr4fEx0U6MkOiu1V56xHgjZGem/lt7t9EajW
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 23 Jul 2020 00:33:04 -0000
Date: 22 Jul 2020 20:33:03 -0400
Message-ID: <e76b9ff-63d4-6482-db9b-39fd404a649d@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "e sam" <e2009@hey.com>, "Michael Richardson" <mcr@sandelman.ca>
Cc: "ietf-smtp" <ietf-smtp@ietf.org>
In-Reply-To: <f0f5d3501740e334b5ee38f5b17c5c927396092d@hey.com>
References: <f0f5d3501740e334b5ee38f5b17c5c927396092d@hey.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/OA5A9arpEt_9iGvO-jgOMCnLOgo>
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: Thu, 23 Jul 2020 00:33:08 -0000

> I personally think that if there is enough time for it in EMAILCORE, then junk mail headers can be addressed.

Once again, it would be useful to understand what problem you believe 
needs to be solved.  I don't see one, and based on the discussion to date, 
I don't think I'm unusual in that.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly