Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: "Erik Schilling" <erik.schilling@linaro.org>
To: <tools@linux.kernel.org>
Subject: [BUG b4] encoding issues with single-patch series
Date: Fri, 16 Jun 2023 11:22:51 +0200	[thread overview]
Message-ID: <CTDYR84I395O.2UI69IKNO7B8A@fedora> (raw)

Earlier, I sent a patch where I tried to CC Alex Bennée. The generated
mail included the header:

    Content-Transfer-Encoding: 7bit

the CC header got correctly escaped, but the mail body contained the CC
with UTF-8 encoding:

    Cc: Alex Bennée <alex.bennee@linaro.org>


The mail got dispatched without any complaints, but then was rejected by
linux-gpio with:

    <linux-gpio@vger.kernel.org>: host 23.128.96.18[23.128.96.18] said: 550 5.7.1
        Content-Policy reject msg: Wrong MIME labeling on 8-bit character texts.
        BF:<H 5.99033e-10>; S229768AbjFPGtM (in reply to end of DATA command)

One can reproduce it with:

    git clone -b b4/msrv https://github.com/Ablu/libgpiod.git
    cd libgpiod
    b4 send -o /tmp/test/ --resend v1
    # The generated mail includes UTF-8 in the body,
    # but has a 7bit header

I did a quick hack to get it resent, but not sure if that is a proper
solution:

--- a/b4/ez.py
+++ b/b4/ez.py
@@ -1581,6 +1581,9 @@ def cmd_send(cmdargs: argparse.Namespace) -> None:
             else:
                 msg.add_header('Cc', b4.format_addrs(pcc))
 
+        msg.set_charset('utf-8')
+        msg.replace_header('Content-Transfer-Encoding', '8bit')
+
         send_msgs.append(msg)
 
     if endpoint:


The weird thing is that some past mails where I also CC'd him,
apparently were sent with the right encoding settings automatically [1]:

    Content-Type: text/plain; charset="utf-8"
    Content-Transfer-Encoding: 8bit

[1] https://lore.kernel.org/linux-gpio/20230612-crates_io_publish-v1-0-70988ee9a655@linaro.org/raw

It looks like it works for a series but not for a single patch?

- Erik

             reply	other threads:[~2023-06-16  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16  9:22 Erik Schilling [this message]
2023-06-16 16:53 ` [BUG b4] encoding issues with single-patch series Konstantin Ryabitsev
2023-06-16 16:55 ` Kernel.org Bugbot
2023-06-22 17:22 ` [BUG b4] " Konstantin Ryabitsev
2023-06-22 17:47 ` Kernel.org Bugbot

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=CTDYR84I395O.2UI69IKNO7B8A@fedora \
    --to=erik.schilling@linaro.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