unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Ed Sabol <esabol@milkyway.gsfc.nasa.gov>, 38200@debbugs.gnu.org
Subject: bug#38200: 26.2; sendmail.el needlessly munging headers by inserting backslashes
Date: Thu, 14 Nov 2019 16:30:04 +0900	[thread overview]
Message-ID: <b4msgmqrk3n.fsf@jpl.org> (raw)
In-Reply-To: <20191113215108.EA66E203EC@alderaan.gsfc.nasa.gov>

On Thu, 14 Nov 2019 05:59:37 +0100, Lars Ingebrigtsen wrote:
> But I'm not sure why this was added (in 2006).  Perhaps some MTAs/MUAs
> react negatively to having those characters unquoted in strings?  It
> looks like this was added by Katsumi, but the changelog doesn't say what
> problem it's trying to fix.

> Katsumi, do you remember?

I don't remember why I added the function
`rfc2047-quote-special-characters-in-quoted-strings' at all.  So
do I about `rfc2047-strip-backslashes-in-quoted-strings' either,
sorry.  But as for at least rfc2047-quote-*, it looks surely
needless.  With some brief tests, I verified the address-mime
encoder works without it.  Even if it is necessary for some cases,
it would probably be very rare, so I'd like to remove it now.
May I do that?

Thanks.





  reply	other threads:[~2019-11-14  7:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 21:51 bug#38200: 26.2; sendmail.el needlessly munging headers by inserting backslashes Ed Sabol via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-14  4:59 ` Lars Ingebrigtsen
2019-11-14  7:30   ` Katsumi Yamaoka [this message]
2019-11-14  7:34     ` Lars Ingebrigtsen
2019-11-14  8:05       ` Katsumi Yamaoka
2019-11-14  8:10         ` Lars Ingebrigtsen
2019-11-14  8:29           ` Katsumi Yamaoka
2019-11-15  1:05             ` Ed Sabol via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=b4msgmqrk3n.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=38200@debbugs.gnu.org \
    --cc=esabol@milkyway.gsfc.nasa.gov \
    --cc=larsi@gnus.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).