Re: [dmarc-ietf] Apropos of the de-munging draft

Alessandro Vesely <vesely@tana.it> Sun, 02 August 2020 17:07 UTC

Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC9C23A079B for <dmarc@ietfa.amsl.com>; Sun, 2 Aug 2020 10:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.447
X-Spam-Level:
X-Spam-Status: No, score=-3.447 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.949, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
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 JlmBNFhlLzCl for <dmarc@ietfa.amsl.com>; Sun, 2 Aug 2020 10:07:01 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (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 C79EB3A079E for <dmarc@ietf.org>; Sun, 2 Aug 2020 10:07:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1596388018; bh=cLehRzgleUnwaJYl21384ekFrDEtLe2bmHwTGaZOXAE=; l=2291; h=To:References:From:Date:In-Reply-To; b=Bxex0NoiDxPOyiBTOAANmgvCoY9vj8FS1rTb0GO+SSqYaCqgogQglGqDpC342p9x4 I6kP9HNObuAOgrtxFlxI5Name7CO2iWBitM2HbssSWTanKzo1HarjLE4MjyZVhtGwP qA8g6K1V/blk+GlSGgQ7QpDMozx7c79uQt4HmBHs7yDbA+GFuZaywoAm/U7rD
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [192.168.1.102] ([5.171.36.20]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC013.000000005F26F2B1.00004EA9; Sun, 02 Aug 2020 19:06:57 +0200
To: dmarc@ietf.org
References: <32bc14d3-81b8-4b49-8fb2-597eba19d1be@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <d4147037-701f-520b-4355-9a07fd708467@tana.it>
Date: Sun, 02 Aug 2020 19:06:56 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <32bc14d3-81b8-4b49-8fb2-597eba19d1be@taugh.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/E7IWQBigRfMCPfj3jNKHy1Phi8g>
Subject: Re: [dmarc-ietf] Apropos of the de-munging draft
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Aug 2020 17:07:03 -0000

On 2020-07-29 1:41 a.m., John R Levine (quoting Jesse) wrote:
> 
>> I think that draft-kucherawy-dkim-transform-02 is getting at what
>> I was originally thinking. In my opinion, MLMs will *always* need
>> to munge, because they will never know if an arbitrary receiver
>> will trust their non-munged mail.  Giving the receivers a way to
>> un-munge (if they can and/or want and/or trust) would be a
>> productive path forward out of this situation.> 
> We already have a couple of ways to do reversible message munging,
> starting with MIME message wrapping. In principle it works fine, in
> practice it's awful because MUAs don't show wrapped messages
> consistently and often in ways that are painful, e.g., you can see the
> original author address but there's no button you can push to respond
> to it.
> 
> Unwrapping a MIME attachment is a lot easier than the proposed DKIM
> unmunging but I doubt either is going to show up in MUAs any time
> soon. Perhaps you could do it in a mail gateway.


Looking at the steps required to carry out the proposed unmunging, "a lot easier" doesn't seem to be an accurate measurement.  Actually, reversing the tf=footer is simpler than unwrapping a message/rfc822 attachment.[*]  The major difficulty is for MLMs to produce modifications that consist of the allowed transformations _only_.  Perhaps, it is a lot easier to create a message/rfc822 without breaking its signatures...?

From: rewriting in particular should be added to the set of allowed transforms.  The MLM should make sure the Author: field mirrors the original From: exactly.  Then it rewrites From:.  It may seem redundant to set a tf= tag on the one hand and undo transforms on the other, since a munged From: is enough to pass.  However, if receivers send aggregate reports back to the MLM, we can hope that one day they'll all succeed and the MLM can stop rewriting From:.

In the interim, an MX which verified the original signature up to allowed transforms can replace the value of From: with that of Author:.  This action is legitimate if all agree that the only reason why MLMs rewrite From: is to pass DMARC checking.  I'd leave footers and subject tags in place.

Best
Ale
-- 

[*] https://mailarchive.ietf.org/arch/msg/dmarc/2ZN7DS5NktoyEPItZ5vzr-xd0Mc