Re: [openpgp] Encrypted emails with cleartext copies [was: Re: use of .well-known in WKD and HKP]

Wiktor Kwapisiewicz <wiktor@metacode.biz> Thu, 02 November 2023 11:26 UTC

Return-Path: <wiktor@metacode.biz>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7F6C151522 for <openpgp@ietfa.amsl.com>; Thu, 2 Nov 2023 04:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=metacode.biz
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SggixHruEWxz for <openpgp@ietfa.amsl.com>; Thu, 2 Nov 2023 04:26:19 -0700 (PDT)
Received: from out-177.mta1.migadu.com (out-177.mta1.migadu.com [95.215.58.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFAB0C151097 for <openpgp@ietf.org>; Thu, 2 Nov 2023 04:26:19 -0700 (PDT)
Message-ID: <24e4958f-7d07-4436-8400-35936a3313d2@metacode.biz>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metacode.biz; s=key1; t=1698924377; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qXqcXsgtrz0JR5Djc6iqsa0r6O6qpJKD0N7pCI2gXt0=; b=XmVwfOC/vGprWYDcQrX2Thc4SQRXgkVVX7k6E0tbF1d/2ckzu/2Etpu8ruDD0j2IVm8ak7 kBB6aMw0PWN/0ufEjEAXQGvlF0ostM7LqQxQnoJMMGo/F67MWI5k1aQMavDbibxkIy0OZz cihpkGeOYjP7O6jv+AWT7YEtR8MI9Pg=
Date: Thu, 02 Nov 2023 12:26:13 +0100
MIME-Version: 1.0
Content-Language: en-US, pl-PL
To: Daniel Huigens <d.huigens=40protonmail.com@dmarc.ietf.org>
Cc: Bart Butler <bart+ietf@pm.me>, openpgp@ietf.org
References: <emlSwBkDqOoXDPHDUKfqZImc8fIYRH0ZJhmMJJYmCtATIm0JDG19aqeqpPVv4fRh5olOsf2lU8qxNJOzU7iYreju2RgbXChVf0uuhr2HnPQ=@protonmail.com>
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
From: Wiktor Kwapisiewicz <wiktor@metacode.biz>
Organization: Metacode
In-Reply-To: <emlSwBkDqOoXDPHDUKfqZImc8fIYRH0ZJhmMJJYmCtATIm0JDG19aqeqpPVv4fRh5olOsf2lU8qxNJOzU7iYreju2RgbXChVf0uuhr2HnPQ=@protonmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Migadu-Flow: FLOW_OUT
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/_ZKp2wlpCd3QqTwkX_pFSj6qmio>
Subject: Re: [openpgp] Encrypted emails with cleartext copies [was: Re: use of .well-known in WKD and HKP]
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Nov 2023 11:26:25 -0000

Hi Daniel,

On 2.11.2023 12:10, Daniel Huigens wrote:
> Writing this email, I also note that your message came from 
> wiktor=40metacode.biz@dmarc.ietf.org, and so when responding to that, 
> Proton Mail also doesn't find any key, obviously. If all public mailing 
> lists did that for all senders (regardless of whether they have DMARC 
> enabled or not), it would also reduce this issue.

I think it works like that because the Mailing List software rewrites 
From. If I sent you e-mail directly *and* CC'd the list then you'd get 
two copies of the same e-mail: one with From me and one with rewritten From.

I'm not a big fan of rewriting e-mails. This sounds like a workaround 
instead of addressing the problem where it originated from (e.g. for 
DMARC signatures some mailing lists don't modify From e-mails and only 
append List-* headers. List-Unsubscribe exists and this plays well with 
DMARC).

Thanks for providing context to the "encrypt messages by default" feature!

Kind regards,
Wiktor