Re: WG Review: Domain-based Message Authentication, Reporting & Conformance (dmarc)

"Murray S. Kucherawy" <superuser@gmail.com> Tue, 15 July 2014 19:10 UTC

Return-Path: <superuser@gmail.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 86ED11B2906 for <ietf@ietfa.amsl.com>; Tue, 15 Jul 2014 12:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 m1_G8b3XITpS for <ietf@ietfa.amsl.com>; Tue, 15 Jul 2014 12:10:37 -0700 (PDT)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCAC21B2900 for <ietf@ietf.org>; Tue, 15 Jul 2014 12:10:36 -0700 (PDT)
Received: by mail-we0-f171.google.com with SMTP id p10so3449922wes.30 for <ietf@ietf.org>; Tue, 15 Jul 2014 12:10:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=aQuDn8r6ldhFiigoc2fMkrUdXXHyh+ljmIQczqQ2h4s=; b=ifyO0WKs1aE4cBUU1dK8bOvm0D2xpMNSuQYF1yLKkkh9HVHjREhvgFWHdvSFGCGKIh vdpKPL4WSq0b28DvyKDKBoEBiFLn5fvZ8eHCkx8v7/xwvp0KOqtMJEX2reBsc9/4iuua GWl9JompARzq/+z8/pAIJ0kuWm23svUxqJJ4XtHEaBad+FpikZsgU8SDGbjwIKw2ZkEG lX/z+9OskXZi+E81S9jswApIIL+0Uo4Y0K/zit1eTgWNAtmH3Jc/MDrKdCOA8LzK4bVB lD7emLxWC1PlmAuNxEBMjcmhThN+Fd2RzdQlHIUWNqjsc0UoXNIMFyy1b5huqzjoFsP0 6T5g==
MIME-Version: 1.0
X-Received: by 10.194.186.178 with SMTP id fl18mr29053590wjc.83.1405451435333; Tue, 15 Jul 2014 12:10:35 -0700 (PDT)
Received: by 10.180.10.99 with HTTP; Tue, 15 Jul 2014 12:10:35 -0700 (PDT)
In-Reply-To: <20140715013308.GI2595@mournblade.imrryr.org>
References: <20140714164212.22974.20340.idtracker@ietfa.amsl.com> <53C413EB.5060408@dcrocker.net> <4450964.7UmRiHm4KW@scott-latitude-e6320> <20140715001549.GG2595@mournblade.imrryr.org> <6C10A695-8F29-4D94-8CF5-FAA0E975A33E@gmail.com> <20140715013308.GI2595@mournblade.imrryr.org>
Date: Tue, 15 Jul 2014 12:10:35 -0700
Message-ID: <CAL0qLwbqzcvv+8UT-0KZ1n0szH=o4YY-fz0sx+gXW+izRCTekg@mail.gmail.com>
Subject: Re: WG Review: Domain-based Message Authentication, Reporting & Conformance (dmarc)
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="047d7bb04dd28d608b04fe402976"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/49y7fm7md3hBKXkQFa4ttGcSC48
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: Tue, 15 Jul 2014 19:10:39 -0000

On Mon, Jul 14, 2014 at 6:33 PM, Viktor Dukhovni <ietf-dane@dukhovni.org>
wrote:

> On Mon, Jul 14, 2014 at 06:20:35PM -0700, Douglas Otis wrote:
>
> > > This is a solved problem, the "Rfc822.Sender" field should have
> > > from the outset trumped the "Rfc822.From" field when determining
> > > message origin, and the DMARC policy should be that of the "Sender"
> > > domain.  Some MUAs already expose "Sender != From" by displaying
> > > "From <sender> on behalf of <author>".  This needs to become standard
> > > MUA behaviour.
> >
> > Viktor,
> >
> > You are right, but this provides a domain not always seen by
> > recipients.  Only the From header field is surely displayed.
>
> That means that some corner cases will remain unsolved until MUAs
> evolve to catch up.  Pretending there is no elephant in the room
> is a poor long-term strategy.
>
> Work to improve the deficient MUAs.


I'd love to hear suggestions about how the IETF can do that.

I think, questions of expertise aside, MUA developers simply don't engage
here [anymore] and follow different paths or time scales than we do most of
the time.  This obvoiusly limits our solution space to what operators can
do, because they're here.

-MSK