DPDK website maintenance
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Ali Alnubani <alialnu@oss.nvidia.com>,
	"announce@dpdk.org" <announce@dpdk.org>,
	"users@dpdk.org" <users@dpdk.org>, "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [dpdk-users] DMARC mitigation in dpdk.org's mailing list
Date: Thu, 23 Sep 2021 20:13:06 +0300	[thread overview]
Message-ID: <20210923201306.3af6582c@sovereign> (raw)
In-Reply-To: <20210923095352.10e9bc66@hermes.local>

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.

  reply	other threads:[~2021-09-23 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23  9:15 [dpdk-web] " Ali Alnubani
2021-09-23 16:42 ` [dpdk-web] [dpdk-users] " Dmitry Kozlyuk
2021-09-23 16:53   ` Stephen Hemminger
2021-09-23 17:13     ` Dmitry Kozlyuk [this message]
2021-09-24 14:01       ` Ali Alnubani
2021-09-23 17:26 ` [dpdk-web] " 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210923201306.3af6582c@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=alialnu@oss.nvidia.com \
    --cc=announce@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    --cc=web@dpdk.org \


* 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).