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

Dave Crocker <dhc@dcrocker.net> Fri, 12 September 2014 12:22 UTC

Return-Path: <dhc@dcrocker.net>
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 11E7C1A0ACE for <ietf@ietfa.amsl.com>; Fri, 12 Sep 2014 05:22:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 7ok4dPSqBpcu for <ietf@ietfa.amsl.com>; Fri, 12 Sep 2014 05:21:59 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBB411A0864 for <ietf@ietf.org>; Fri, 12 Sep 2014 05:21:59 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s8CCLuhX018228 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 12 Sep 2014 05:21:59 -0700
Message-ID: <5412E49D.30406@dcrocker.net>
Date: Fri, 12 Sep 2014 05:18:37 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: dmarc damage, was gmail users read on... [bozo subtopic]
References: <20140911202058.3327.qmail@joyce.lan> <541208F6.1010302@dougbarton.us> <bb48b8f170074ddeb25cbb213f613892@DM2PR0301MB0655.namprd03.prod.outlook.com>
In-Reply-To: <bb48b8f170074ddeb25cbb213f613892@DM2PR0301MB0655.namprd03.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 12 Sep 2014 05:21:59 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ljoQYwBKuxycp3AF0pvfo0DCKLA
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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 12:22:01 -0000

On 9/11/2014 10:34 PM, Christian Huitema wrote:
> 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.

According to the criteria you list, sure.  According to what a recipient
sees, it works badly.  In terms of human communication, author
information is buried.


> 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.

This suggests defining a wrapping convention that is sufficiently
distinction so that receiving software can know it is this specific type
of wrapping and can choose to unwrap the message, without doing
unwrapping for other kinds of encapsulated mail.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net