Re: Last Call: <draft-ietf-dmarc-interoperability-15.txt> (Interoperability Issues Between DMARC and Indirect Email Flows) to Informational RFC

"John Levine" <johnl@taugh.com> Sun, 22 May 2016 03:05 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D83312D0A7 for <ietf@ietfa.amsl.com>; Sat, 21 May 2016 20:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 8hJp_m3RxKtq for <ietf@ietfa.amsl.com>; Sat, 21 May 2016 20:05:58 -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-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5C4D12B054 for <ietf@ietf.org>; Sat, 21 May 2016 20:05:57 -0700 (PDT)
Received: (qmail 37804 invoked from network); 22 May 2016 03:05:56 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 22 May 2016 03:05:56 -0000
Date: 22 May 2016 03:05:34 -0000
Message-ID: <20160522030534.45958.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-dmarc-interoperability-15.txt> (Interoperability Issues Between DMARC and Indirect Email Flows) to Informational RFC
In-Reply-To: <49148678-7c9b-c200-1862-b7ffaba68928@gmail.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/0GDIBnuqoYsAlp8JsXH2goaUjnY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 22 May 2016 03:05:59 -0000

>>    [RFC6377] provides some guidance on using DKIM with Mailing lists.
>>    The following mitigation techniques can be used to ease
>>    interoperability issues with DMARC and Mailing lists:
>
>It should probably be indicated whether these techniques would be applied
>to all messages, or only to messages sent from domains with a DMARC
>policy other than "p=none". (I prefer the latter.)

It's an implementation issue, depending on whether the list software
can get the DMARC policy from a DNS query or from an
Authorization-Results header.  My MTA puts an A-R header on incoming
mail so I have a shim after the list manager that looks at the A-R
header and rewrites the From: address (into dmarc.fail addresses,
which some people imagine are not deliverable) if it sees a DMARC
policy.


>>    o  Configuring the MLM to "wrap" the message in a MIME message/rfc822
>>       part and to send as the Mailing List email address.  Many email
>>       clients (as of the publication of this document), especially
>>       mobile clients, have difficulty reading such messages and this is
>>       not expected to change soon.
>
>This seems like a quite elegant solution. I'm very surprised by the second
>sentence - are these clients that have difficulty with many Content-Types
>or is it a specific issue for message/rfc822?

It's a one-entry MIME digest, so it looks like a digest, not an
individual message.

R's,
John