Gnus development mailing list
 help / color / mirror / Atom feed
From: Romain Francoise <romain@orebokech.com>
Subject: Re: bug in message.el, message-forward-make-body-plain
Date: Thu, 02 Dec 2004 10:09:58 +0100	[thread overview]
Message-ID: <878y8hxdzt.fsf@orebokech.com> (raw)
In-Reply-To: <b9yzn0xm7is.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 02 Dec 2004 17:25:15 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> I think your patch is the best solution.  I've installed it.

Thanks!

> It is likely if a user has set message-forward-as-mime as nil
> and uses the `C-c C-f' command.  I guess that was the mere copy
> of an old code.

Right, that's probably why.

> BTW, even for raw forwarding, isn't there a demand to remove
> some headers?  For instance, a lot of Received headers will
> usually be unnecessary.

I don't think we should remove them by default: they're useful when
forwarding spam to an abuse address, or for debugging mail loops, etc.
An inexperienced user might not know how to change the value of m-f-i-h
to get all headers back.

> Furthermore, if a header such as the following

> Xref: localhost trash:99999

> is forwarded, the person who wrote the message may be offended.
> Of course, we can remove them manually, though.

Yes, I usually remove all such headers manually.  But removing Xref
could be useful since it's internal to Gnus and not useful to anyone
apart from the sender.

-- 
Romain Francoise <romain@orebokech.com> | This is a man's man's man's
it's a miracle -- http://orebokech.com/ | world. --James Brown



  reply	other threads:[~2004-12-02  9:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 20:08 Ted Stern
2004-12-01  8:19 ` Katsumi Yamaoka
2004-12-01 19:15   ` Ted Stern
2004-12-01 19:48   ` Romain Francoise
2004-12-01 21:39     ` Ted Stern
2004-12-01 21:56       ` Romain Francoise
2004-12-02  8:25         ` Katsumi Yamaoka
2004-12-02  9:09           ` Romain Francoise [this message]
2004-12-19 22:26     ` Kai Grossjohann
2004-12-20 18:06       ` Ted Stern

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=878y8hxdzt.fsf@orebokech.com \
    --to=romain@orebokech.com \
    /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).