From: Konstantin <reich-cv@yandex.ru>
To: 74624@debbugs.gnu.org
Subject: bug#74624: 29.4.50; Gnus cannot parse some filenames(UTF8) in an attachment
Date: Sat, 30 Nov 2024 18:59:25 +0300 [thread overview]
Message-ID: <87v7w44srm.fsf@localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]
From time to time i get emails with attachments from my colleges, which they send from
"Roundcube" web-interface.
Often, i cannot open these attachments by =RET=(gnus-article-press-button)
or save them =o=(gnus-mime-save-part) with correct name.
(interestingly =X-m=(gnus-summary-save-parts) works correctly)
The reason is gnus cannot parse correctly some attached filenames.
The example of such attachment (I took it from gnus-summary-show-raw-article)
--=_d38c0abddd645077f401d42fa430d9d5
Content-Transfer-Encoding: base64
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document;
name="=?UTF-8?Q?=D0=9E=D0=B1=D0=B7=D0=BE=D1=80_2024_=28=D0=BD=D0=B0_=2Ed?=
=?UTF-8?Q?ocx?="
Content-Disposition: attachment;
filename*0*=UTF-8''%D0%9E%D0%B1%D0%B7%D0%BE%D1%80%202024%20%28%D0%BD%D0;
filename*1*=%B0%20.docx;
size=10
c2Rmc2FmYXNmCg==
--=_d38c0abddd645077f401d42fa430d9d5--
I have tried to examine the reason. As i see it,
gnus-data for such attachment is formed incorrectly:
(#<buffer *mm*-480444>
("application/vnd.openxmlformats-officedocument.word..."
(name . "Обзор 2024 (на .docx"))
base64 nil
("attachment" (size . "10")
(filename . "Обзор 2024 (н\320")) nil nil nil)
One can see that the filename is broken.
It should be "Обзор 2024 (на .docx" just like the name.
I have attached the example of the mail(one can open it with nndoc)
Please, could you fix this bug.
[-- Attachment #2: mail.test --]
[-- Type: application/octet-stream, Size: 805 bytes --]
Return-path: <test@test.com>
Envelope-to: test@test.com
Delivery-date: Sat, 30 Nov 2024 11:04:35 +0300
MIME-Version: 1.0
Date: Sat, 30 Nov 2024 11:04:35 +0100
From: reich <test@test.com>
To: test@test.com
Subject: test
Message-ID: <1aac7676a838f3ec7a16820f65e6ff4c@test.com>
Content-Type: multipart/mixed;
boundary="=_d38c0abddd645077f401d42fa430d9d5"
--=_d38c0abddd645077f401d42fa430d9d5
Content-Transfer-Encoding: base64
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document;
name="=?UTF-8?Q?=D0=9E=D0=B1=D0=B7=D0=BE=D1=80_2024_=28=D0=BD=D0=B0_=2Ed?=
=?UTF-8?Q?ocx?="
Content-Disposition: attachment;
filename*0*=UTF-8''%D0%9E%D0%B1%D0%B7%D0%BE%D1%80%202024%20%28%D0%BD%D0;
filename*1*=%B0%20.docx;
size=10
c2Rmc2FmYXNmCg==
--=_d38c0abddd645077f401d42fa430d9d5--
next reply other threads:[~2024-11-30 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 15:59 Konstantin [this message]
2024-11-30 16:20 ` bug#74624: 29.4.50; Gnus cannot parse some filenames(UTF8) in an attachment Eli Zaretskii
2024-12-01 6:24 ` Visuwesh
2024-12-01 7:52 ` Konstantin
2024-12-01 8:17 ` Eli Zaretskii
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=87v7w44srm.fsf@localdomain \
--to=reich-cv@yandex.ru \
--cc=74624@debbugs.gnu.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.
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).