----- Original Message -----
From: "Alexey Melnikov" <aamelnikov(_at_)fastmail(_dot_)fm>
To: "Brian E Carpenter" <brian(_dot_)e(_dot_)carpenter(_at_)gmail(_dot_)com>
Cc: draft-ietf-dmarc-interoperability(_at_)ietf(_dot_)org, "Ned Freed"
<ned(_dot_)freed(_at_)mrochek(_dot_)com>, ietf(_at_)ietf(_dot_)org,
dmarc(_at_)ietf(_dot_)org,
"alexey melnikov" <alexey(_dot_)melnikov(_at_)isode(_dot_)com>,
dmarc-chairs(_at_)ietf(_dot_)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(_dot_)e(_dot_)carpenter(_at_)gmail(_dot_)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...