From: David Woodhouse <dwmw2@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
mark@msapiro.net
Cc: workflows@vger.kernel.org,
"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"MTD Maling List" <linux-mtd@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: Getting rid of infradead.org - corrupted subjects
Date: Wed, 25 May 2022 10:55:18 +0100 [thread overview]
Message-ID: <eb5ab9553c419b8259f5494664865597b6c5d4db.camel@infradead.org> (raw)
In-Reply-To: <CAMuHMdWL93+r0cofwHKj1k-gUo9nk3OzUf6gtY68sK4JNibyNg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2657 bytes --]
On Wed, 2022-05-25 at 10:34 +0200, Geert Uytterhoeven wrote:
> CC dwmw2
Thanks, Geert.
> On Wed, May 25, 2022 at 10:07 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>
> > The address list is semi-random as I don't know whom to approach.
> > Problem: infradead.org corrupts email subjects by changing:
> > s/,/, /
I found an old thread on mailman-users which appears to be claiming
that it's just standard folding as described in RFC2822 §2.2.3.
https://mail.python.org/pipermail/mailman-users/2007-May/057119.html
2.2.3. Long Header Fields
Each header field is logically a single line of characters comprising
the field name, the colon, and the field body. For convenience
however, and to deal with the 998/78 character limitations per line,
the field body portion of a header field can be split into a multiple
line representation; this is called "folding". The general rule is
that wherever this standard allows for folding white space (not
simply WSP characters), a CRLF may be inserted before any WSP. For
example, the header field:
Subject: This is a test
can be represented as:
Subject: This
is a test
But this is folding at a *comma*, not at whitespace. The original
subject line was (in a single line):
Subject: [PATCH v2] dt-bindings: mtd: jedec,spi-nor: remove unneeded properties
... and Mailman 'folded' it in the wrong place to:
Subject: [PATCH v2] dt-bindings: mtd: jedec,
spi-nor: remove unneeded properties
That *isn't* proper folding because it didn't happen at a whitespace.
I do need to upgrade to Mailman 3 at some point; I've been
procrastinating on the basis that it "ain't broke". For the time being
I've just disabled folding in MM2 with a trivial hack:
--- Message.py.orig 2022-05-25 02:51:05.917145192 -0700
+++ Message.py 2022-05-25 02:50:44.137142069 -0700
@@ -49,7 +49,7 @@ class Generator(email.Generator.Generato
Headers will by default _not_ be folded in attachments.
"""
def __init__(self, outfp, mangle_from_=True,
- maxheaderlen=78, children_maxheaderlen=0):
+ maxheaderlen=0, children_maxheaderlen=0):
email.Generator.Generator.__init__(self, outfp,
mangle_from_=mangle_from_, maxheaderlen=maxheaderlen)
self.__children_maxheaderlen = children_maxheaderlen
Looking at http://lists.infradead.org/pipermail/testlist/2022-May/subject.html
it seems to have had the desired effect. Please let me know if not (or
if there are other side-effects).
Thanks for the report.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
next prev parent reply other threads:[~2022-05-25 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 8:07 Getting rid of infradead.org - corrupted subjects Krzysztof Kozlowski
2022-05-25 8:34 ` Geert Uytterhoeven
2022-05-25 9:55 ` David Woodhouse [this message]
2022-05-25 14:30 ` Rob Herring
2022-05-25 15:16 ` David Woodhouse
2022-06-14 9:47 ` Chen-Yu Tsai
2022-05-25 19:23 ` Uwe Kleine-König
2022-05-31 19:59 ` Uwe Kleine-König
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=eb5ab9553c419b8259f5494664865597b6c5d4db.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=konstantin@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark@msapiro.net \
--cc=miquel.raynal@bootlin.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=workflows@vger.kernel.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).