----- Original Message ----- > From: "Alexey Melnikov" <aamelnikov@xxxxxxxxxxx> > To: "Brian E Carpenter" <brian.e.carpenter@xxxxxxxxx> > Cc: draft-ietf-dmarc-interoperability@xxxxxxxx, "Ned Freed" <ned.freed@xxxxxxxxxxx>, ietf@xxxxxxxx, dmarc@xxxxxxxx, > "alexey melnikov" <alexey.melnikov@xxxxxxxxx>, dmarc-chairs@xxxxxxxx > 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@xxxxxxxxx> > 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...