From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Dan Jacobson <jidanni@jidanni.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 67520@debbugs.gnu.org
Subject: bug#67520: 29.1; Mention headers
Date: Mon, 04 Dec 2023 20:26:33 -0800 [thread overview]
Message-ID: <87bkb5qnpi.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <8a532628a05193a12e475af79a1a9934@jidanni.org> (Dan Jacobson's message of "Mon, 04 Dec 2023 11:30:10 +0800")
On 12/04/23 11:30 AM, Dan Jacobson wrote:
> OK, then ths is a feature request. Users are often asked to forward
> complete pristine emails to various abuse investigation departments.
> Gnus should offer such functionality.
Okay, that's clearer! message.el is fairly convoluted, but it comes down
to `message-remove-ignored-headers'. That consults several options,
most importantly `message-forward-ignored-headers' and
`message-forward-included-headers'. The ignored headers are removed, as
you'd expect, but if anything at all is in the included headers, *only*
those included headers are... included. You lose everything else.
So what you really want is the option to (perhaps temporarily) set
`message-forward-included-headers' to nil. (Please try it out and
confirm.)
And the real question is how to offer this option to the user.
Everything is already thoroughly overloaded...
next prev parent reply other threads:[~2023-12-05 4:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 3:49 bug#67520: 29.1; Mention headers Dan Jacobson
2023-11-29 12:56 ` Eli Zaretskii
2023-11-29 15:31 ` Eric Abrahamsen
2023-11-30 6:02 ` Dan Jacobson
2023-12-04 1:39 ` Eric Abrahamsen
2023-12-04 3:30 ` Dan Jacobson
2023-12-05 4:26 ` Eric Abrahamsen [this message]
2023-12-05 5:06 ` Dan Jacobson
2023-12-06 15:09 ` Eric Abrahamsen
2023-12-08 5:17 ` Dan Jacobson
2023-12-08 17:42 ` Eric Abrahamsen
2023-12-08 22:24 ` jidanni
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=87bkb5qnpi.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=67520@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.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).