Re: [ietf-smtp] Email explained from first principles
John R Levine <johnl@taugh.com> Thu, 27 May 2021 16:23 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 CA6303A006A for <ietf-smtp@ietfa.amsl.com>; Thu, 27 May 2021 09:23:21 -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 (2048-bit key) header.d=iecc.com header.b=f/mdDvvz; dkim=pass (2048-bit key) header.d=taugh.com header.b=DnCeawyE
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 N9-Osyy5zGG3 for <ietf-smtp@ietfa.amsl.com>; Thu, 27 May 2021 09:23:16 -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 AAB0D3A0063 for <ietf-smtp@ietf.org>; Thu, 27 May 2021 09:23:15 -0700 (PDT)
Received: (qmail 7214 invoked from network); 27 May 2021 16:23:13 -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=1c2c.60afc771.k2105; bh=G097sHBarso29SwaSmol9PQDfLboXvJUG1SkttJvFSo=; b=f/mdDvvzNtv692Ar/yq69mJLDgJk1O+xMiqaCGnszKGWgZwbLisHGLA5AE1qS4lBXqkVpe+hk5uRYKIjz4vdeh8YQ+w2yeeVTNeuRV0IgqdByAhzPS2RU+NU5HJiFRc47izcZq9pszCnq0wuUR/En8gLGprNC4WF8Jrp9sxKHQrzvsDDdP8OeGWn+l8+OZVdOqXk7DyCjiHc5bRyZgQuLHxcaHaxg++LwESnPViqLQOyNjqOFIVECW4ZZpQUQoZGfcmHupdtAhj//xfwyqqH9EqjLvIKD9ib7EOSzlH25zoRDV/n3KmWrsr5wJOYHFZ7vaheaVq0wSM/LXCC9jgMJA==
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=1c2c.60afc771.k2105; bh=G097sHBarso29SwaSmol9PQDfLboXvJUG1SkttJvFSo=; b=DnCeawyEFeDTt31vqbUJMqRpXgKHS3IGM0ziKvX9pbyZn24ceXObpgnbZ3cOnxleBc3LlCTTgryLNslScQXPd9SXZTPMGysELeTsjsJelYXDwXc+y21wVoBNdpkYLSbg54DZf6NfOHYE9Gff9EK2lLgPIrb1UqqcOMx26hKJStsCrGKvjxRMdJO5yJ3zNxs/jSUalKpGqXndhoL0IKsdvSn6uPSVFOPBTNX+Han+SDG3nN2sRWD5XvjjkYZQJBJxACIOQJp31xt3fM9W+wLBxfSIjh1AWx2qMClLt9//foV6tWcJXk2aMyDyYYCGvLuO3Cb7D1vS3LPUAQirEcvkOA==
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; 27 May 2021 16:23:12 -0000
Received: by ary.qy (Postfix, from userid 501) id 91B2F8D1C73; Thu, 27 May 2021 12:23:10 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id ACB218D1C55; Thu, 27 May 2021 12:23:10 -0400 (EDT)
Date: Thu, 27 May 2021 12:23:10 -0400
Message-ID: <e951c676-dada-121e-2f9e-80548965c916@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Kaspar Etter <kaspar@ef1p.com>, John Levine <johnl@taugh.com>
Cc: IETF SMTP Mailing List <ietf-smtp@ietf.org>
X-X-Sender: johnl@ary.qy
In-Reply-To: <6E17FD4E-C3D7-4703-8E5C-B0364D011418@ef1p.com>
References: <20210524140315.991E3890E35@ary.qy> <6E17FD4E-C3D7-4703-8E5C-B0364D011418@ef1p.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1369546713-1622132590=:35247"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/UNSVs3p9efZiFTOxm3xA61QHbfE>
Subject: Re: [ietf-smtp] 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: Thu, 27 May 2021 16:23:22 -0000
On Thu, 27 May 2021, Kaspar Etter wrote: > This conversation went off on a tangent, but I also want to comment on a couple of things: > >> On 24 May 2021, at 16:03, John Levine <johnl@taugh.com> wrote: >> >> It appears that Kaspar Etter <kaspar@ef1p.com> said: >>> 2. List-Name header field: Mailing lists shouldn’t rewrite the messages of others and break DKIM signatures in the process. >> >> Sorry, but this shows some serious misunderstandings about both DKIM and mailing lists. >> >> DKIM is a transport signature, which in this case shows that the message was sent from the author >> to the mailing list system. List apply their own DKIM signature on the mail they send. >> Mailing lists have been editing messages for 40 years, long before anyone >> ever thought of DKIM or DMARC. It is a well known DMARC failure that it doesn't work with mailing lists. >> Some people have tried to rewrite history and claim that it is the lists' fault but they are wrong. >> >> The whole point of ARC is to provide recipient systems with info to help recognize when they should >> ignore DMARC and deliver mail from lists and other legitimate senders that don't happen to match the >> assumptions that DMARC makes. > > I disagree. You're welcome to your opinion, but you don't get to rewrite 40 years of history. We've spent a decade with people insisting that the entire e-mail world has to change the way it works to conform to the lastest FUSSP. We saw it with SPF, we're seeing it with DMARC. It didn't hapen with SPF, and it's not happening with DMARC. For example, mailing lists have been editing messages for a long time, they have good reasons to do so, and they're not going to stop. I'm not guessing about the reasons for ARC, I know the people who developed it and I believe I am correctly describing the reason they invented it. It includes some of the largest mail providers in the world. They all use DMARC, and they understand that DMARC's limitations cause a lot of gratuitous pain for their users who've been using mailing lists for a long time. It's not a large fraction of the total amount of mail, but it's a large fraction of the mail they care about. Regards, John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly
- [ietf-smtp] Email explained from first principles Kaspar Etter
- Re: [ietf-smtp] Email explained from first princi… Bron Gondwana
- Re: [ietf-smtp] Email explained from first princi… Alessandro Vesely
- Re: [ietf-smtp] Email explained from first princi… Viktor Dukhovni
- Re: [ietf-smtp] Email explained from first princi… Viktor Dukhovni
- Re: [ietf-smtp] Email explained from first princi… Kaspar Etter
- Re: [ietf-smtp] Email explained from first princi… Peter J. Holzer
- Re: [ietf-smtp] Email explained from first princi… John Levine
- Re: [ietf-smtp] Email explained from first princi… Sam Varshavchik
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… John Levine
- Re: [ietf-smtp] Email explained from first princi… Dave Crocker
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Dave Crocker
- Re: [ietf-smtp] Email explained from first princi… John R Levine
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Sam Varshavchik
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… John Levine
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Sam Varshavchik
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Dave Crocker
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Sam Varshavchik
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Dave Crocker
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Sam Varshavchik
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Dave Crocker
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Matthias Leisi
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Sam Varshavchik
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Dave Crocker
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… John Levine
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Sam Varshavchik
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… Nathaniel Borenstein
- Re: [ietf-smtp] DKIM and DMARC, Email explained f… John C Klensin
- Re: [ietf-smtp] Email explained from first princi… Kaspar Etter
- Re: [ietf-smtp] Email explained from first princi… John R Levine
- Re: [ietf-smtp] Email explained from first princi… John R Levine
- Re: [ietf-smtp] Email explained from first princi… Kaspar Etter
- Re: [ietf-smtp] Email explained from first princi… John R Levine
- Re: [ietf-smtp] Email explained from first princi… Richard Clayton
- Re: [ietf-smtp] Email explained from first princi… Alessandro Vesely
- Re: [ietf-smtp] Email explained from first princi… John C Klensin
- Re: [ietf-smtp] the point of domain authentication John R Levine
- Re: [ietf-smtp] mailing lists are complicated, wa… John Levine
- Re: [ietf-smtp] the point of domain authentication Sam Varshavchik
- Re: [ietf-smtp] the point of domain authentication John Levine
- Re: [ietf-smtp] mailing lists are complicated, wa… Alessandro Vesely
- Re: [ietf-smtp] mailing lists are complicated, wa… John R Levine
- Re: [ietf-smtp] mailing lists are complicated, wa… Dave Crocker
- Re: [ietf-smtp] Email explained from first princi… Richard Clayton
- Re: [ietf-smtp] mailing lists are complicated, wa… Alessandro Vesely