From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: larsi@gnus.org, yamaoka@jpl.org, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: `mail-encode-header' encodes encoded header
Date: Wed, 14 Mar 2012 19:04:05 +0200 [thread overview]
Message-ID: <83ipi7w1ve.fsf@gnu.org> (raw)
In-Reply-To: <E1S7jyX-0002rZ-BB@fencepost.gnu.org>
> Date: Wed, 14 Mar 2012 04:54:29 -0400
> From: Richard Stallman <rms@gnu.org>
> Cc: yamaoka@jpl.org, ding@gnus.org, emacs-devel@gnu.org
>
> There was definitely a bug that occurred in using sendmail.el
> without that change. But I don't recall the test case and
> I could not come up with one now. So I don't object
> to removing the change. But I think the problem will show
> up again.
When it does, please describe it. It can never be TRT to encode an
already encoded address. There must be some other bug in some other
place, which prevents the address from being encoded in the first
place.
prev parent reply other threads:[~2012-03-14 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 12:18 Katsumi Yamaoka
2012-03-13 22:14 ` Lars Magne Ingebrigtsen
2012-03-13 23:28 ` Katsumi Yamaoka
2012-03-14 8:54 ` Richard Stallman
2012-03-14 17:04 ` Eli Zaretskii [this message]
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=83ipi7w1ve.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
--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.
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 NNTP newsgroup(s).