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

Alexey Melnikov <aamelnikov@fastmail.fm> Sun, 22 May 2016 10:54 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 8606A12D550; Sun, 22 May 2016 03:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=Pn/m4sZb; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=OZAZNFjs
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 lYCoztm0FR9E; Sun, 22 May 2016 03:54:05 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6CD212D537; Sun, 22 May 2016 03:54:05 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 585F520385; Sun, 22 May 2016 06:54:03 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Sun, 22 May 2016 06:54:03 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=TKBkmV6Pm2OY1zFH4KmbPPJDpiQ=; b=Pn/m4s Zbzd5gMz3YVCx6zDmh+7XOesbAD9hzoO1pW2SbsmwFtPgtQnhQWWYOBVuF3EUFLp H8ifiSzsuqzQ+AZRosG7mgfmcr89yNCquirZS1kpmBSAMgYfsEIfSGvU2LoMMNfl A9Pfdu4gNAqEZZtVpqXCK/tFeXv7bya0Kby2E=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=TKBkmV6Pm2OY1zF H4KmbPPJDpiQ=; b=OZAZNFjszYNV6Ip/qbGA817Ubpxlw3oxmKBJ4rYOs6vy8G+ VzBv9h25/qMolUo0PR+IsXgL9pio1IMpFXX4iZhvSbkXAUxmxD6glzXjB1e9pY2Y FtW+6NJSmYxxDBu5Ejk8RGyLDkGJnV874bhU0quxN3O2ON43i8qaukMuQaHA=
X-Sasl-enc: qCrjKigNfqMvivVjz8YydWmifFJOwFIiYDkwhpJSp/9+ 1463914442
Received: from [10.9.97.168] (unknown [85.255.234.174]) by mail.messagingengine.com (Postfix) with ESMTPA id E7790F29E5; Sun, 22 May 2016 06:54:02 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: [dmarc-ietf] Last Call: <draft-ietf-dmarc-interoperability-15.txt> (Interoperability Issues Between DMARC and Indirect Email Flows) to Informational RFC
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13E238)
In-Reply-To: <49148678-7c9b-c200-1862-b7ffaba68928@gmail.com>
Date: Sun, 22 May 2016 12:00:19 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3211644D-09A8-4969-B830-A62F9EBC593B@fastmail.fm>
References: <20160520134205.328.49041.idtracker@ietfa.amsl.com> <49148678-7c9b-c200-1862-b7ffaba68928@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/A60w0Q5ISylrYxUh5ytweRHJEkw>
Cc: draft-ietf-dmarc-interoperability@ietf.org, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org, dmarc@ietf.org, alexey.melnikov@isode.com, dmarc-chairs@ietf.org
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 10:54:08 -0000

On 22 May 2016, at 00:08, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

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

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.