Re: dmarc damage, was gmail users read on... [bozo subtopic]

"John Levine" <johnl@taugh.com> Mon, 15 September 2014 21:06 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B789E1A8772 for <ietf@ietfa.amsl.com>; Mon, 15 Sep 2014 14:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.762
X-Spam-Level:
X-Spam-Status: No, score=0.762 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
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 mOrQEYvxNXQl for <ietf@ietfa.amsl.com>; Mon, 15 Sep 2014 14:06:52 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3A8F1A877B for <ietf@ietf.org>; Mon, 15 Sep 2014 14:06:48 -0700 (PDT)
Received: (qmail 82094 invoked from network); 15 Sep 2014 21:06:47 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 15 Sep 2014 21:06:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=a75.541754e6.k1409; i=johnl@user.iecc.com; bh=ZVmykikExrWa3yPHUHHscxKuzMDlQALyycN222I7pF8=; b=siM/RsQ3JKoeWNqT7rZHu8oiq4f8OIgfTIbhtzqgujIt57uQobPnD1RXzwV9uSSPoHfxxaK44Cu9fIlc73Krqfr32+mjLBjPgseF69MyQFQt4CS87gO7bDfm1Nr/AwxXq2ob1AmEHSc8Xfp+ldLp2bFOzuXHJSHqaXThRqdE9+rYYfCkRCFGXRyvk2hyLFbviww6WMgGkF0yBNXtnrTP/tWVQFQ1ikeNRrTByJKbSMvuVmmMQJu54Md8v+j1vDRu
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=a75.541754e6.k1409; olt=johnl@user.iecc.com; bh=ZVmykikExrWa3yPHUHHscxKuzMDlQALyycN222I7pF8=; b=zXLhTkLiNsdocIc7Jw7WDE1zcyFheTrvxeDBpbHFO6ygafRgD5DOMrGjTBEe+oQNzLLXZzWqhw0kpWgWtMTGXMtFVJHPNpYQy/WbhxDqKmjmC3yhSSSPRatbTUF6Hlq3z3Tl2AbzjnsayOynvv2V6pd84XCx3H6mKBo/s5YvNinRX7UnNmmPhBeful0TtcNlAr+jpZdTdRUsO0bgNIV2Crcp63DSxaxhdf9AqgbGM/JDkFk0sbh8KEqcFTkFwtVW
Date: Mon, 15 Sep 2014 21:06:24 -0000
Message-ID: <20140915210624.2676.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Cc: ietf@ietf.org
Subject: Re: dmarc damage, was gmail users read on... [bozo subtopic]
In-Reply-To: <alpine.LRH.2.01.1409142034180.30233@egate.xpasc.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DKmXkeJunl8mtRbyhmoYQJBxfl0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 21:06:53 -0000

In article <alpine.LRH.2.01.1409142034180.30233@egate.xpasc.com> you write:
>
>It seems to me that the wrapped original mail could be signed by the
>forwarding list processor so that the DMARC recipient would accept the
>forwarded mail as coming from the forwarder and the ultimate MUA would
>be able to verify that the wrapped messaged was indeed wrapped by the
>forwarding list processor and transparently unwrap the original
>email.

Well, yes, but you don't need to wrap mail to re-sign it.  By design,
any host that relays a message can add a DKIM signature.  Well run
mailing lists sign mail now.  Look at any IETF list mail for an
example.

The problem with wrapped mail is basically a UI problem, and the IETF
has a long history of knowing less than nothing about UI (as in, much
of what we think we know is wrong.)

Anything a list can do to wrap mail, a bad guy can do, too.  Work out
a few scenarios and you'll find that wrapping isn't very attractive as
a long term solution to anything.

R's,
John