unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lin Jian via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56906@debbugs.gnu.org
Subject: bug#56906: 28.1; attachment names containing Chinese characters are handled wrong by default
Date: Thu, 04 Aug 2022 14:48:04 +0800	[thread overview]
Message-ID: <874jysa3dq.fsf@linj.tech> (raw)
In-Reply-To: <87pmhgse25.fsf@gnus.org>


Lars Ingebrigtsen <larsi@gnus.org> writes:

> I'm unable to reproduce this.

I am willing to help you to reproduce this issue. Feel free to ask me
for information you need.

> It looks to me like something has double-encoded the header, so probably
> an SMTP server somewhere that's mishandling the mail?

I don't think it has something to do with SMTP server because I can see
the double-encoded header locally before sending an email if I add some
"print" command around message-encode-message-body and
mail-encode-encoded-word-buffer in message-send-mail like:

(message "debug1: before message-encode-message-body\n%s" (buffer-string))
(message-encode-message-body)
(message "debug1: after message-encode-message-body\n% (buffer-string))

(message "debug2: before mail-encode-encoded-word-buffer\n%s" (buffer-string))
(mail-encode-encoded-word-buffer)
(message "debug2: after mail-encode-encoded-word-buffer\n%s" (buffer-string)))

In the *Message* buffer, after "debug1: after message-encode-message-body", I can see:

Content-Disposition: attachment;
 filename="=?utf-8?B?5rWL6K+VMTIzYWJjLnRhcg==?="

and after "debug2: after mail-encode-encoded-word-buffer", I can see

Content-Disposition: attachment;
 =?us-ascii?Q?filename=3D=22=3D=3Futf-8=3FB=3F5rWL6K+VMTIzYWJjLnRhcg=3D=3D?=
 =?us-ascii?Q?=3F=3D=22?=






  reply	other threads:[~2022-08-04  6:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03  2:23 bug#56906: 28.1; attachment names containing Chinese characters are handled wrong by default Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04  6:44 ` Lars Ingebrigtsen
2022-08-04  6:48   ` Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-04  7:25     ` Lars Ingebrigtsen
2022-08-04  7:35       ` Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04  7:46       ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=874jysa3dq.fsf@linj.tech \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56906@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=me@linj.tech \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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