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

Wiktor Kwapisiewicz <> Thu, 02 November 2023 11:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6E7F6C151522 for <>; Thu, 2 Nov 2023 04:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.107
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SggixHruEWxz for <>; Thu, 2 Nov 2023 04:26:19 -0700 (PDT)
Received: from ( []) (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 (Postfix) with ESMTPS id AFAB0C151097 for <>; Thu, 2 Nov 2023 04:26:19 -0700 (PDT)
Message-ID: <>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; 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 <>
Cc: Bart Butler <>,
References: <>
X-Report-Abuse: Please report any abuse attempt to and include these headers.
From: Wiktor Kwapisiewicz <>
Organization: Metacode
In-Reply-To: <>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Migadu-Flow: FLOW_OUT
Archived-At: <>
Subject: Re: [openpgp] Encrypted emails with cleartext copies [was: Re: use of .well-known in WKD and HKP]
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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 
>, 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 

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

Kind regards,