From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: pieter-l@vanoostrum.org, rms@gnu.org, michael_heerdegen@web.de,
"積丹尼 Dan Jacobson" <jidanni@jidanni.org>,
larsi@gnus.org, 38818@debbugs.gnu.org
Subject: bug#38818: jidanni's mail headers not perfect?!
Date: Mon, 06 Jan 2020 12:02:32 +0200 [thread overview]
Message-ID: <D70A9874-EA68-4B21-B71A-B4C030E9CC25@gnu.org> (raw)
In-Reply-To: <871rsdndku.fsf@hase.home>
On January 6, 2020 11:23:13 AM GMT+02:00, Andreas Schwab <schwab@linux-m68k.org> wrote:
> On Jan 06 2020, Eli Zaretskii wrote:
>
> > On January 6, 2020 10:30:55 AM GMT+02:00, Andreas Schwab
> <schwab@linux-m68k.org> wrote:
> >> On Jan 05 2020, Eli Zaretskii wrote:
> >>
> >> >> From: =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
> <jidanni@jidanni.org>
> >> >> ^^^^^^^^^^^
> >> >
> >> > Why do you think this arrives intact to people's MUA?
> >>
> >> Why do you think this does not arrive intact to people's MUA?
> >
> > Because some methods of fetching email auto-convert qp-encoded and
> base64 encoded parts.
>
> But that isn't the fault of the raw mail contents.
This isn't about assigning blame, this is about finding where that mojibake comes from and what triggers it, and hopefully figuring out how to avoid or fix that.
next prev parent reply other threads:[~2020-01-06 10:02 UTC|newest]
Thread overview: 59+ 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
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 [this message]
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-22 12:47 ` Lars Ingebrigtsen
2020-01-22 13:17 ` 積丹尼 Dan Jacobson
2020-01-22 13:19 ` Lars Ingebrigtsen
2020-01-04 6:16 ` 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
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=D70A9874-EA68-4B21-B71A-B4C030E9CC25@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 \
--cc=schwab@linux-m68k.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).