From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: "Kernel.org Tools" <tools@linux.kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: [BUG b4] misformatted email recipients
Date: Mon, 9 Jan 2023 14:15:16 +0000 [thread overview]
Message-ID: <20230109141516.ddljbbkzwk74bfwe@snowball.t-8ch.de> (raw)
Hi,
it seems in certain cases b4 will misfold/misformat email recipient.
The exact conditions are that a long address line pushes the comma
separating different addresses to a new line during folding and that
line contains unicode data that is encoded.
In this case the comma is also encoded.
The root cause is a bug in Python email module [0].
Such misformatted mails are rejected by some mail servers, for example
infradead.org.
Also it seems they are not indexed by public-inbox [1].
I hit this case in the wild [2].
Thanks,
Thomas
[0] https://github.com/python/cpython/issues/100884
[1] https://public-inbox.org/meta/20230108200233.y2zqecm3ob47gsdd@snowball.t-8ch.de/
[2] See thread-view on https://lore.kernel.org/lkml/Y7VxkG0ZsfJEyuFP@kernel.org/
next reply other threads:[~2023-01-09 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 14:15 Thomas Weißschuh [this message]
2023-01-09 17:15 ` [BUG b4] misformatted email recipients Konstantin Ryabitsev
2023-01-09 23:18 ` Konstantin Ryabitsev
2023-01-10 0:02 ` Thomas Weißschuh
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=20230109141516.ddljbbkzwk74bfwe@snowball.t-8ch.de \
--to=thomas@t-8ch.de \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.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 read-only IMAP folder(s) and NNTP newsgroup(s).