From: Eli Zaretskii <eliz@gnu.org>
To: Pieter van Oostrum <pieter-l@vanoostrum.org>
Cc: michael_heerdegen@web.de, larsi@gnus.org, jidanni@jidanni.org,
rms@gnu.org, 38818@debbugs.gnu.org
Subject: bug#38818: jidanni's mail headers not perfect?!
Date: Mon, 06 Jan 2020 12:09:17 +0200 [thread overview]
Message-ID: <D76A5F66-2F7E-49C6-A37D-C7C3A16E3850@gnu.org> (raw)
In-Reply-To: <lxk1643o3h.fsf@cochabamba.vanoostrum.org>
On January 6, 2020 11:56:18 AM GMT+02:00, Pieter van Oostrum <pieter-l@vanoostrum.org> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> OK, then I probably didn't understand you.
> You asked about =?utf-8?B?56mN5Li55bC8?=
> "Why do you think this arrives intact to people's MUA?"
>
> So I thought you meant there is something wrong with that part.
> Apparently you did not mean that. So what did you mean? Dan seems to
> want that part (some CJK characters) to show up in the email, and it
> does for me. And that is how it should be.
I'm saying that if the original mail had some suitable MIME charset in its headers, the problem would be less likely to happen. Because email messages that rely on implicit encoding specifications are more likely to hit subtle problems.
And btw, no one can rely on having the exact same encoded name in response email, MUA and MTA are free to change the representation at will, as long as the content is transferred without losses.
next prev parent reply other threads:[~2020-01-06 10:09 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 16:09 bug#38818: Dired: mention deleting buffers, not just windows 積丹尼 Dan Jacobson
2019-12-30 17:53 ` martin rudalics
2019-12-30 18:11 ` 積丹尼 Dan Jacobson
2019-12-31 7:59 ` martin rudalics
2019-12-31 17:33 ` Michael Heerdegen
2020-01-01 2:14 ` 積丹尼 Dan Jacobson
2020-01-01 2:47 ` Michael Heerdegen
2020-01-01 3:07 ` 積丹尼 Dan Jacobson
2020-01-01 3:45 ` Michael Heerdegen
2020-01-01 3:59 ` 積丹尼 Dan Jacobson
2020-01-01 4:53 ` Michael Heerdegen
2020-01-01 5:11 ` 積丹尼 Dan Jacobson
2020-01-01 5:31 ` Michael Heerdegen
2020-01-01 6:53 ` Drew Adams
2020-01-01 14:38 ` Noam Postavsky
2020-01-01 23:18 ` Richard Stallman
2020-01-02 3:29 ` Drew Adams
2020-01-02 21:59 ` Richard Stallman
2020-01-11 9:40 ` Eli Zaretskii
2020-01-01 16:46 ` Pieter van Oostrum
2020-01-02 4:14 ` Michael Heerdegen
2020-01-03 15:10 ` 積丹尼 Dan Jacobson
2020-01-03 23:18 ` Pieter van Oostrum
2020-01-03 23:31 ` 積丹尼 Dan Jacobson
2020-01-03 23:51 ` Pieter van Oostrum
2020-01-04 0:13 ` 積丹尼 Dan Jacobson
2020-01-04 13:58 ` Pieter van Oostrum
2020-01-04 23:48 ` Richard Stallman
2020-01-05 7:39 ` Pieter van Oostrum
2020-01-05 22:18 ` Richard Stallman
2020-01-05 8:06 ` Pieter van Oostrum
2020-01-05 15:31 ` Eli Zaretskii
2020-01-05 18:19 ` 積丹尼 Dan Jacobson
2020-01-05 18:48 ` Eli Zaretskii
2020-01-05 19:09 ` bug#38818: jidanni's mail headers not perfect?! 積丹尼 Dan Jacobson
2020-01-05 19:33 ` Eli Zaretskii
2020-01-05 20:48 ` Pieter van Oostrum
2020-01-06 3:26 ` Eli Zaretskii
2020-01-06 9:56 ` Pieter van Oostrum
2020-01-06 10:09 ` Eli Zaretskii [this message]
2020-01-06 10:16 ` Andreas Schwab
2020-01-06 8:30 ` Andreas Schwab
2020-01-06 8:50 ` Eli Zaretskii
2020-01-06 9:23 ` Andreas Schwab
2020-01-06 10:02 ` Eli Zaretskii
2020-01-06 10:13 ` Andreas Schwab
2020-01-05 22:19 ` bug#38818: Dired: mention deleting buffers, not just windows Richard Stallman
2020-01-05 23:30 ` 積丹尼 Dan Jacobson
2020-01-06 3:32 ` Eli Zaretskii
2020-01-06 23:08 ` Richard Stallman
2020-01-07 15:42 ` Bad RFC 2047 decoding in Rmail Eli Zaretskii
2020-01-07 17:35 ` Stefan Monnier
2020-01-07 23:49 ` Richard Stallman
2020-01-22 12:47 ` bug#38818: Dired: mention deleting buffers, not just windows Lars Ingebrigtsen
2020-01-22 13:17 ` 積丹尼 Dan Jacobson
2020-01-22 13:19 ` Lars Ingebrigtsen
2020-01-05 22:21 ` improvement in functions.texi Richard Stallman
2020-01-11 9:49 ` Eli Zaretskii
2020-01-04 6:16 ` bug#38818: Dired: mention deleting buffers, not just windows Michael Heerdegen
2020-01-04 13:57 ` Pieter van Oostrum
2020-01-05 18:20 ` 積丹尼 Dan Jacobson
2020-01-04 13:26 ` Noam Postavsky
2020-01-01 6:47 ` Drew Adams
2020-01-22 12:51 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D76A5F66-2F7E-49C6-A37D-C7C3A16E3850@gnu.org \
--to=eliz@gnu.org \
--cc=38818@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
--cc=pieter-l@vanoostrum.org \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.