From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Change in rmail-start-mail
Date: Sat, 12 Mar 2011 15:28:42 +0200 [thread overview]
Message-ID: <83mxl0sc1h.fsf@gnu.org> (raw)
This change:
revno: 100059.1.49
committer: Kenichi Handa <handa@m17n.org>
branch nick: 23-build
timestamp: Tue 2011-02-22 00:19:08 +0000
message:
Decode "encoded-words" of header components on replying.
breaks rmail-reply for me: the outgoing message has a garbled header
for each header that was RFC 2047 encoded in the original message to
which I reply.
Why was this change made? What was the problem it was supposed to
solve?
It is quite clear that the assumption was that some other code will
RFC 2047 encode these headers before the message is sent, but what
code is supposed to do that? I use sendmail-user-agent and
smtpmail-send-it, and these do not encode those headers. Should the
decoding introduced with the above revision be conditioned on some
specific MUA?
next reply other threads:[~2011-03-12 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 13:28 Eli Zaretskii [this message]
2011-03-12 20:57 ` Change in rmail-start-mail Stefan Monnier
2011-03-12 21:16 ` 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=83mxl0sc1h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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).