Re: [ietf-smtp] mailing lists are complicated, was Email explained from first principles

John Levine <johnl@taugh.com> Fri, 28 May 2021 18:18 UTC

Return-Path: <johnl@iecc.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 095C93A3098 for <ietf-smtp@ietfa.amsl.com>; Fri, 28 May 2021 11:18:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=v5JffC3p; dkim=pass (2048-bit key) header.d=taugh.com header.b=Y5m5Sewj
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 sjbvKYfFdJ7z for <ietf-smtp@ietfa.amsl.com>; Fri, 28 May 2021 11:18:23 -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 9C2D13A3097 for <ietf-smtp@ietf.org>; Fri, 28 May 2021 11:18:23 -0700 (PDT)
Received: (qmail 44884 invoked from network); 28 May 2021 18:18:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=af4e.60b133ee.k2105; bh=VnINII3ABTu5p5ngHmh9S5ojIgCMqR10SxSnG1otFvw=; b=v5JffC3pPU/HfsaFElU/PjSVq3VhLTodO4T/awxBZhrSzu0PTmuUbyDpJfUIMMvRqQgSdyzDlZFY/e6Pn/BcgtvweRVqyAlrpGp/6XEz+RwHcBaVGQKQ8ItAJu1trGa9l/+2xQc0NkbWQc1EQs7OGs+m/AO4XQ5UvsLzT6AskMta3LWPHLGzKjeQUbohfjJS0zwB24+Yumxsa7oXrgraKVjhUDzmXJUE6PQwoqLoDi2b0NgUwnRtX21348Zb7savvfy85Q8Vukb/B8yeVd+tmLyXAF/7S7FHEci3GZ+AL9mSaQJ3H00v0dT+1mgW0QAtlzzImIOkanEk+ETB6yS75w==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=af4e.60b133ee.k2105; bh=VnINII3ABTu5p5ngHmh9S5ojIgCMqR10SxSnG1otFvw=; b=Y5m5Sewjiyxd1vIWyMYetfBzqLDPojru9SRnXeReNwAn48S3cvI/8NMLhqx34/8EohamQQKOHXl1X1bKEPxugQ1uPVnMKGTYmNHHAxkBMYE9hOnGDvT94Jbr18UTdDJhFgIyjAaUGyprmeq0TWcczYJGFHSqHGS2VG7YJu3hvSHNb2psKWFGV7WRboCfN9uY/4cZEmq3BTWbfpsXDW+xiHPEQTTEfwhjsKE/6nnGegOaCS9kPfAbaUL2b/cOMqResG8+MPBBIfW2kVVbTCYxZFU1Mg0+2wJV418NNqSB39NPQwgO4iCuUa0ygxYB9VlognqO2eLJPZ4NZv5wXQnLaQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 28 May 2021 18:18:22 -0000
Received: by ary.qy (Postfix, from userid 501) id 943B08E0563; Fri, 28 May 2021 14:18:19 -0400 (EDT)
Date: Fri, 28 May 2021 14:18:19 -0400
Message-Id: <20210528181821.943B08E0563@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: vesely@tana.it
In-Reply-To: <d2e70837-14db-c9e9-9d7d-93e8498fbb45@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/lASTxyHfJ8x43BpBox0PXJ2zEWs>
Subject: Re: [ietf-smtp] mailing lists are complicated, was Email explained from first principles
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: Fri, 28 May 2021 18:18:29 -0000

It appears that Alessandro Vesely  <vesely@tana.it> said:
>Mailing lists often do keep DKIM signatures intact.  They only alter the rest 
>of the message, but the transformations they do are stylized enough to allow to 
>revert them and verify the original signatures. ...

We've been around this barn a few times before. What you say may seem
true if you have only seen a few lists handled by a single list
package. In reality, I have seen lists add headers and footers, add,
delete, and reorganize MIME parts while changing the MIME boundary
strings, rewrite URLs in message bodies, and flatten HTML bodies into
text. There is no way to list all of the common changes, much less
describe how to reverse them.

In any event, whatever you might want to do by reviving DKIM signatures is already
handled by ARC, so it'd be a lot more productive to encourage ARC adoption than
to invent yet another half-hearted DMARC workaround.

R's,
John