[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ietf
Subject:    Re: [dmarc-ietf] Last Call: <draft-ietf-dmarc-interoperability-15.txt> (Interoperability Issues Betw
From:       Franck Martin <franck () peachymango ! org>
Date:       2016-05-23 17:07:36
Message-ID: 1916486689.52040.1464023256291.JavaMail.zimbra () peachymango ! org
[Download RAW message or body]


----- 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>, ietf@ietf.org, dmarc@ietf.org, "alexey melnikov" \
>                 <alexey.melnikov@isode.com>, 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...


[prev in list] [next in list] [prev in thread] [next in thread]