From: Kevin Falcone <kevinfal@seas.upenn.edu>
Subject: Re: message forwarding and MIME
Date: 04 Dec 1999 00:30:40 -0500 [thread overview]
Message-ID: <m366yfi873.fsf@jibsheet.com> (raw)
In-Reply-To: Emerick Rogul's message of "03 Dec 1999 23:06:15 -0500"
>>>>> "ER" == Emerick Rogul <emerick@cs.bu.edu> writes:
Jim Davidson writes:
: I'm glad that the flag message-forward-as-mime made it into v .99.
ER> Yes, I am too. One thing that would be nice, in addition to this, is
ER> if you could somehow specify a set of reduced headers when forwarding
ER> a message. I know that sometimes the full set of headers is a Good
ER> Thing, but I think they're not wanted in the typical case.
look at message-forward-ignore-headers, it takes a regex of ignored headers.
-kevin
--
Kevin Falcone <kevinfal@seas.upenn.edu>
Lasciate ogni speranza, voi ch'entrate!
--Dante
next prev parent reply other threads:[~1999-12-04 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-04 0:59 Jim Davidson
1999-12-04 4:06 ` Emerick Rogul
1999-12-04 5:30 ` Kevin Falcone [this message]
1999-12-04 15:55 ` Emerick Rogul
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=m366yfi873.fsf@jibsheet.com \
--to=kevinfal@seas.upenn.edu \
/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).