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 17:05:34 +0900 [thread overview]
Message-ID: <b4mlfsirigh.fsf@jpl.org> (raw)
In-Reply-To: <20191113215108.EA66E203EC@alderaan.gsfc.nasa.gov>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On Thu, 14 Nov 2019 08:34:24 +0100, Lars Ingebrigtsen wrote:
> 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.
Sure. Mail agents do not know what backslashes like to do.
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> 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.
Done in master. Thanks. Ed, a patch for Emacs 26.2 is attached.
Regards,
[-- Attachment #2: remove-rfc2047-quote-special-characters-in-quoted-strings.patch.gz --]
[-- Type: application/x-gunzip, Size: 1374 bytes --]
next prev parent reply other threads:[~2019-11-14 8:05 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
2019-11-14 8:05 ` Katsumi Yamaoka [this message]
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=b4mlfsirigh.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).