Re: [dmarc-ietf] 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 14:20 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 21F3E12D095 for <ietf@ietfa.amsl.com>; Sun, 22 May 2016 07:20:38 -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 HTJL9uAHDbkh for <ietf@ietfa.amsl.com>; Sun, 22 May 2016 07:20:36 -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 423AB12B004 for <ietf@ietf.org>; Sun, 22 May 2016 07:20:36 -0700 (PDT)
Received: (qmail 76126 invoked from network); 22 May 2016 14:20:35 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 22 May 2016 14:20:35 -0000
Date: 22 May 2016 14:20:13 -0000
Message-ID: <20160522142013.48173.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [dmarc-ietf] Last Call: <draft-ietf-dmarc-interoperability-15.txt> (Interoperability Issues Between DMARC and Indirect Email Flows) to Informational RFC
In-Reply-To: <3211644D-09A8-4969-B830-A62F9EBC593B@fastmail.fm>
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/If_TLcaUmhalA-gOO86hGNl5TgQ>
Cc: aamelnikov@fastmail.fm
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 14:20:38 -0000

>> 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?
>
>Only message/rfc822. E.g. it took iOS a couple of years to start supporting it properly. And it is one of the better mobile email clients.

Brian sent me a message/rfc822 wrapped version of his message, so I
stuffed it into my Gmail, Yahoo, and Hotmail mailboxs after looking at
it in Apple mail and Thuderbird and of course Alpine.  Gmail flattens
it to look like a text forward, Yahoo loses the headers on the
wrappped message, Hotmail and Apple mail show it as an attachment you
can download, Thunderbird and Alpine show all the relevant bits, but
not in a particularly attractive way.

In practice it's worse than rewriting the From: line to the mailing
list's address, which is already far from good.

R's,
John