From: Ali Alnubani <alialnu@oss.nvidia.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "announce@dpdk.org" <announce@dpdk.org>,
"users@dpdk.org" <users@dpdk.org>, "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-web] DMARC mitigation in dpdk.org's mailing list
Date: Fri, 24 Sep 2021 14:01:42 +0000 [thread overview]
Message-ID: <DM4PR12MB51670314C175A77718AF40A1DAA49@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210923201306.3af6582c@sovereign>
> -----Original Message-----
> From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
> Sent: Thursday, September 23, 2021 8:13 PM
> To: Stephen Hemminger <stephen@networkplumber.org>
> Cc: Ali Alnubani <alialnu@nvidia.com>; announce@dpdk.org;
> users@dpdk.org; web@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@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.
next prev parent reply other threads:[~2021-09-24 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 9:15 [dpdk-users] " Ali Alnubani
2021-09-23 16:42 ` Dmitry Kozlyuk
2021-09-23 16:53 ` [dpdk-users] [dpdk-web] " Stephen Hemminger
2021-09-23 17:13 ` Dmitry Kozlyuk
2021-09-24 14:01 ` Ali Alnubani [this message]
2021-09-23 17:26 ` [dpdk-users] " St Leger, Jim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM4PR12MB51670314C175A77718AF40A1DAA49@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@oss.nvidia.com \
--cc=announce@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
--cc=web@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).