Re: [ietf-smtp] Testing From-Munging

dkg <dkg@protonmail.com> Wed, 30 March 2022 16:36 UTC

Return-Path: <dkg@protonmail.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 735E43A1325 for <ietf-smtp@ietfa.amsl.com>; Wed, 30 Mar 2022 09:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=protonmail.com
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 B4C7zsS1dw-l for <ietf-smtp@ietfa.amsl.com>; Wed, 30 Mar 2022 09:36:24 -0700 (PDT)
Received: from mail-4318.protonmail.ch (mail-4318.protonmail.ch [185.70.43.18]) (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 515663A1319 for <ietf-smtp@ietf.org>; Wed, 30 Mar 2022 09:36:24 -0700 (PDT)
Date: Wed, 30 Mar 2022 16:36:15 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1648658180; bh=8ZNZONTY+bziXuBSNgyU0l6wM/GhE+Ah7EPKuOtt0ws=; h=Date:To:From:Reply-To:Subject:Message-ID:In-Reply-To:References: From:To:Cc:Date:Subject:Reply-To:Feedback-ID:Message-ID; b=aZPJICW8v2Ap3alL6mUHdBpsTBEi/a/eJ2kPLrhPu6EB5e0AwVfrQcY8+UPQxIepg ZIlXlcPGBORAbaa/4FR9i0qFmQadjR9HoYT+AfmFW6eL77r0SMty8npSB4EKZDXYt2 Mden5a7yyKnbjzxdfDGrxxYn5CO3VcMSVqxRuaoGOI7PfI92fsX1FkijT+oTB9SMMq NQgn8XzxAV0tIZvXTXkmQchwn7sS0Noq5R8+d4MIzhLNTLgFvuzfAa76HgPJYQge2T ScRGxf55woIFD2QcSuwADUn5MIiv77MDM3udSJKvCQEWFTAjql0mlua/JKEio+Q5t9 Cxop9bJhONNPA==
To: "ietf-smtp@ietf.org" <ietf-smtp@ietf.org>
From: dkg <dkg@protonmail.com>
Reply-To: dkg <dkg@protonmail.com>
Message-ID: <BM7YT092MMqf5RO5rnoXeFHzAPT3LxvRlwaIiVI9v06Wq0tc23ha8s43n3gqkBmVQPsLat91gqwJKD6QkqMfgM38xtXf4LbnTwibL1l6RRc=@protonmail.com>
In-Reply-To: <CAHej_8meARhJWHeJEMwNkkqCp8idQehiO=bb9SkqbatHUOsZ9g@mail.gmail.com>
References: <wOeAYHU0t0oidcJI13rpJxWmHK39s6RYg7QOr3xuxv0_Rm2P2rIgYtoKNot74IvLpIlGybJhHGmE_TgI0YgEbaxCrLLMwr4Wk6b_Dq5UK_g=@protonmail.com> <CAHej_8meARhJWHeJEMwNkkqCp8idQehiO=bb9SkqbatHUOsZ9g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_AhI9gbg60MZoc7IEoOwAeHG7DKluaT61I2Jj9UZhQQ"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/_z3Rc9dIe1bLnZ6830SQSfKx0Z0>
Subject: Re: [ietf-smtp] Testing From-Munging
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: Wed, 30 Mar 2022 16:36:30 -0000

heh -- there are multiple forms of From-munging, i guess. This test wasn't about the "From:" header field (which i think is what you're talking about). This test was about the "From " in the body of the message getting prefixed with a ">" character, which it did.

It's a relic of the old mbox format, where each message started with a line with "From ", so the message bodies that had that got a > prepended to them so that they wouldn't start a new message. This shouldn't really be happening on modern systems for new messages, though, since there are much better formats than mbox available today. (and, if you are for some reason obliged to use mbox, there are known reversible ways to from-munge, so that when messages transit through an mbox they don't come out modified.)

If you're interested in helping diagnose or fix this on IETF infrastructure, it's probably best to follow up on https://github.com/ietf-tools/mailarch/issues/3487

--dkg

Sent with [ProtonMail](https://protonmail.com/) secure email.

------- Original Message -------
On Wednesday, March 30th, 2022 at 11:18 AM, Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org> wrote:

> On Wed, Mar 30, 2022 at 1:04 AM dkg <dkg=40protonmail.com@dmarc.ietf.org> wrote:
>
>> Sorry for the noise. I'm just confirming that From-munging still happens on IETF mailing lists (see https://github.com/ietf-tools/mailarch/issues/3487)
>>
>>>From protonmail, this is an unsigned message.
>
> My understanding has always been that the munging happens if the original Author Domain has published a DMARC policy that isn't p=none, like protonmail.com has done:
>
>> $ dig +short _dmarc.protonmail.com txt
>>
>> "v=DMARC1; p=quarantine; fo=1; aspf=s; adkim=s;"
>
> --
>
> Todd Herr  | Technical Director, Standards and Ecosysteme: todd.herr@valimail.comm: 703.220.4153
>
> This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.