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

Theodore Ts'o <tytso@mit.edu> Fri, 12 September 2014 13:27 UTC

Return-Path: <tytso@thunk.org>
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 A0E1C1A0658 for <ietf@ietfa.amsl.com>; Fri, 12 Sep 2014 06:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.553
X-Spam-Level:
X-Spam-Status: No, score=-3.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001] autolearn=ham
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 ZhFa2MKiSYOM for <ietf@ietfa.amsl.com>; Fri, 12 Sep 2014 06:27:47 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 056B91A069C for <ietf@ietf.org>; Fri, 12 Sep 2014 06:27:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org; s=ef5046eb; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=wWBUIYKwt00CpoiTK/dOJu+b9invxVIsNLFEoofWx3Q=; b=axFlSykMffwBbL0wfswCfZpNJs+hBlDPgDHuYm4X1JA0d5SnEu27k96fZAXd6bUtO+gDyoI8fWQvq5Y+P0kLcLFF2LTrsB83l7YTnPvmELmv9THXQXxPN4JqnMW/J2Nk5wTSF/l66l5GzlT1SSoT90keI3n7Q8Rdb3+hdqLq6AE=;
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1XSQt5-0005zz-MF; Fri, 12 Sep 2014 13:27:43 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id D6A355801C5; Fri, 12 Sep 2014 09:27:42 -0400 (EDT)
Date: Fri, 12 Sep 2014 09:27:42 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: dmarc damage, was gmail users read on... [bozo subtopic]
Message-ID: <20140912132742.GA5035@thunk.org>
References: <20140911202058.3327.qmail@joyce.lan> <541208F6.1010302@dougbarton.us> <bb48b8f170074ddeb25cbb213f613892@DM2PR0301MB0655.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <bb48b8f170074ddeb25cbb213f613892@DM2PR0301MB0655.namprd03.prod.outlook.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tkTSvOx0guqBJ2-mO1ywTvBkQAQ
Cc: "ietf@ietf.org" <ietf@ietf.org>
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: Fri, 12 Sep 2014 13:27:48 -0000

On Fri, Sep 12, 2014 at 05:34:06AM +0000, Christian Huitema wrote:
> 
> The big change with DMARC is a deprecation of the Sender/From
> differentiation, effectively requiring that these two will be the
> same. It seems that big systems have voted that the differentiation
> causes more harm (spam, phish) than good (remailers).
> 
> Of the responses listed, the one that clearly works is to ask
> forwarders to forward messages, what the wiki calls "message
> wrapping." It works in the sense that the mail system sees
> consistent headers that pass all verifications, and represent the
> actual action of the remailer while not relying on Sender/From
> differences.
> 
> At that point, the issue is mostly with the UI. If my reader did
> recognize the "simple forwarding" case from "authorized remailers,"
> then the message wrapping solution would be just fine. The good
> thing is that it is very much under my control.

But unfortunately, once the UI recognizes this case, would we not be
imposing harm vis-a-vis phishing in particular?  And then DMARC Mark
II (as it were) would have to prohibit the wrapping and require a wrap
of a wrap, etc.

There's no way of winning this.  But if we are going to go down this
path, it would be useful to discuss what the UI would look at that
meets the needs of mailing lists, but without potential harm of
phishing.

							 -Ted