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

Franck Martin <franck@peachymango.org> Mon, 23 May 2016 17:07 UTC

Return-Path: <franck@peachymango.org>
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 BC9EE12D93A; Mon, 23 May 2016 10:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=peachymango.org
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 ry63kt7jKcOk; Mon, 23 May 2016 10:07:45 -0700 (PDT)
Received: from mx-out-1.zmailcloud.com (mx-out.zmailcloud.com [192.198.85.98]) by ietfa.amsl.com (Postfix) with ESMTP id BAB9812D9D0; Mon, 23 May 2016 10:07:44 -0700 (PDT)
Received: from smtp.01.com (smtp.01.com [10.10.0.43]) by mx-out-1.zmailcloud.com (Postfix) with ESMTP id 66EB7563D58; Mon, 23 May 2016 12:07:39 -0500 (CDT)
Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 53A43A0482; Mon, 23 May 2016 12:07:39 -0500 (CDT)
X-Virus-Scanned: amavisd-new at smtp-out-1.01.com
Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3X0IB5lKHf2T; Mon, 23 May 2016 12:07:39 -0500 (CDT)
Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 09986A0489; Mon, 23 May 2016 12:07:37 -0500 (CDT)
DKIM-Filter: OpenDKIM Filter v2.8.4 smtp-out-1.01.com 09986A0489
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=peachymango.org; s=61F775A4-4A7F-11E4-A6BB-61E3068E35F6; t=1464023257; bh=8TAHlJd9f/UZ00M3IAtClf1PS+AR09zPU5T7ImpLrzA=; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type: Content-Transfer-Encoding; b=b4SCEnKmaTSeJnCMgbqxFtii0OJpCAY1J1rkKn207iDXaO+pPono/meY488aRd7Ab nxponM0OMY/n4Lwj33LvGpJbHrBI5dLQIelu0TJfSgH/vE5IzRr3NSUgE/yCeHJB2Y KqxephcfIb7M0dVx1/2zZXncXJ0BqE7GUGxdfClk=
Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id D5DC9A0482; Mon, 23 May 2016 12:07:36 -0500 (CDT)
X-Virus-Scanned: amavisd-new at smtp-out-1.01.com
Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id jqVkRMznr48L; Mon, 23 May 2016 12:07:36 -0500 (CDT)
Received: from mail-2.01.com (mail.01.com [10.10.0.41]) by smtp-out-1.01.com (Postfix) with ESMTP id 8B473A047D; Mon, 23 May 2016 12:07:36 -0500 (CDT)
Date: Mon, 23 May 2016 12:07:36 -0500 (CDT)
From: Franck Martin <franck@peachymango.org>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <1916486689.52040.1464023256291.JavaMail.zimbra@peachymango.org>
In-Reply-To: <WM!7e8dbc088fb68472ed60a4fc1d168f626467eab14a113e6cd54dc84030fbb3fbb7903230d2bbe3519c1042b6b04544e0!@mailstronghold-3.zmailcloud.com>
References: <20160520134205.328.49041.idtracker@ietfa.amsl.com> <49148678-7c9b-c200-1862-b7ffaba68928@gmail.com> <3211644D-09A8-4969-B830-A62F9EBC593B@fastmail.fm> <WM!7e8dbc088fb68472ed60a4fc1d168f626467eab14a113e6cd54dc84030fbb3fbb7903230d2bbe3519c1042b6b04544e0!@mailstronghold-3.zmailcloud.com>
Subject: Re: [dmarc-ietf] Last Call: <draft-ietf-dmarc-interoperability-15.txt> (Interoperability Issues Between DMARC and Indirect Email Flows) to Informational RFC
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 8.0.5_GA_5839 (ZimbraWebClient - FF46 (Mac)/8.0.5_GA_5839)
Thread-Topic: Last Call: <draft-ietf-dmarc-interoperability-15.txt> (Interoperability Issues Between DMARC and Indirect Email Flows) to Informational RFC
Thread-Index: zSK/kzQbRfnxVoNyjCTaM+jE22Jfww==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/8yjCP7-ScydVIWS0Fp-iXVGLYdM>
Cc: draft-ietf-dmarc-interoperability@ietf.org, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org, dmarc@ietf.org, alexey melnikov <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: Mon, 23 May 2016 17:07:47 -0000

----- Original Message -----
> From: "Alexey Melnikov" <aamelnikov@fastmail.fm>
> To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> Cc: draft-ietf-dmarc-interoperability@ietf.org, "Ned Freed" <ned.freed@mrochek.com>om>, ietf@ietf.org, dmarc@ietf.org,
> "alexey melnikov" <alexey.melnikov@isode.com>om>, dmarc-chairs@ietf.org
> Sent: Sunday, May 22, 2016 4:00:19 AM
> Subject: Re: [dmarc-ietf] Last Call: <draft-ietf-dmarc-interoperability-15.txt> (Interoperability Issues Between
> DMARC and Indirect Email Flows) to Informational RFC
> 
> 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.

And "forward as attachment" that creates this message/rfc822 has disappeared from many clients...