From: Lars Ingebrigtsen <larsi@gnus.org>
To: Katsumi Yamaoka <yamaoka@jpl.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 08:34:24 +0100 [thread overview]
Message-ID: <87h836oqrj.fsf@gnus.org> (raw)
In-Reply-To: <b4msgmqrk3n.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 14 Nov 2019 16:30:04 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> 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.
I seem to vaguely recall there perhaps being a problem with things
like
From: "Foo, Bar" <foo@zot.com>, zot@foo.com
being tokenized into three email addresses
Foo
Bar <foo@zot.com>
zot@foo.com
But on the other hand, if there's anything that broken out there, you'd
think that adding a backslash before the comma wouldn't help, either.
> 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?
Sure, go ahead. If there's any interoperability problems here, we'll
find out. But I think it's pretty unlikely.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-11-14 7:34 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
2019-11-14 7:34 ` Lars Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h836oqrj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=38200@debbugs.gnu.org \
--cc=esabol@milkyway.gsfc.nasa.gov \
--cc=yamaoka@jpl.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.