[dpdk-users] [dpdk-web] DMARC mitigation in dpdk.org's mailing list

[Ali Alnubani]

> -----Original Message-----
> From: Dmitry Kozlyuk <dmitry.kozliuk at gmail.com>
> Sent: Thursday, September 23, 2021 8:13 PM
> To: Stephen Hemminger <stephen at networkplumber.org>
> Cc: Ali Alnubani <alialnu at nvidia.com>; announce at dpdk.org;
> users at dpdk.org; web at dpdk.org
> Subject: Re: [dpdk-web] [dpdk-users] DMARC mitigation in dpdk.org's
> mailing list
> 
> 2021-09-23 09:53 (UTC-0700), Stephen Hemminger:
> > On Thu, 23 Sep 2021 19:42:24 +0300
> > Dmitry Kozlyuk <dmitry.kozliuk at gmail.com> wrote:
> >
> > > 2021-09-23 09:15 (UTC+0000), Ali Alnubani:
> > > > [...]
> > > > - Disable conversion of text/html to plain text.
> > > >   Mailman currently strips MIME attachments and does text/html to
> plain text conversion.
> > >
> > > Why not just reject HTML messages?
> >
> > Because too much of the world uses Outlook.
> 
> That's the reason for my concern. Outlook's handling of quotes in HTML
> mode is unbelievably poor. Prolonged discussion, started by a message with
> several points, inevitably becomes a mix of colored text inside(!) the quote;
> or top-posting at best. More often than not it ends with an offline discussion
> by voice or whatever. Which defeats the purpose of a public mailing list: to
> preserve discussions. Outlook can send plain text, so its users are not limited
> by forbidding HTML. Hopefully, dev@ will remain as-is anyway, because
> threads are usually started by a plain text patch, and Outlook inherits this
> property for replies.

DMARC authentication will still fail for plain text messages if we don't change anything for dev,
because the mailing list will still alter the Subject and the Sender headers causing signature breakage.
Let's see how disabling the conversion from html to plain text goes, and we'll continue discussing
completely rejecting html messages with the techboard.