From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Simplify inline forward headers
Date: Tue, 26 Jun 2007 16:03:16 +0900 [thread overview]
Message-ID: <b4m1wfznqob.fsf@jpl.org> (raw)
In-Reply-To: <b4m4pkvvbol.fsf@jpl.org>
>>>>> In <b4m4pkvvbol.fsf@jpl.org> Katsumi Yamaoka wrote:
> In other words, removing it might break a message that has the
> CTE header originally and is forwarded in the raw form.
Please ignore this sentence. I overlooked that Gnus doesn't
remove any header from a forwarding part if it is in the raw
form. So, that the `message-forward-ignored-headers' variable
has "^Content-Transfer-Encoding:" by default is not a problem.
prev parent reply other threads:[~2007-06-26 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 2:27 Leo
2007-06-25 4:36 ` Katsumi Yamaoka
2007-06-25 9:05 ` Leo
2007-06-25 9:32 ` Leo
2007-06-25 10:36 ` Katsumi Yamaoka
2007-06-25 12:54 ` Bjørn Mork
2007-06-25 23:47 ` Katsumi Yamaoka
2007-06-26 7:03 ` Katsumi Yamaoka [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=b4m1wfznqob.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@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.
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).