unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: 45631@debbugs.gnu.org
Subject: bug#45631: 27.1; regression: message-forward-ignored-headers no longer applies when forwarding as MIME
Date: Tue, 05 Jan 2021 14:06:54 +0100	[thread overview]
Message-ID: <87y2h71qj5.fsf@gmail.com> (raw)
In-Reply-To: <87mtxq7xmd.fsf@fifthhorseman.net> (Daniel Kahn Gillmor's message of "Sun, 03 Jan 2021 12:12:42 -0500")

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

> I've been using emacs as my MUA for years.
>
> When I upgraded from emacs 26.3 to emacs 27.1, i noticed that
> message-forward-as-mime now defaults to nil.  I prefer to forward as
> MIME generally, so i set it back to t.
>
> The only downside to forwarding as MIME is the inclusion of some headers
> that the received message has accumulated in transit, which might have
> privacy-sensitive implications. I've been using
> message-forward-ignored-headers for a while now to trim out headers like
> Received and Delivered-To when forwarding.
>
> But as of 27.1, message-forward-ignored-headers doesn't work when
> forwarding as MIME.  indeed, the help text for the variable now says
>
>  >> This variable is only consulted when forwarding "normally", not when
>  >> forwarding as MIME or the like.
>
> But this is a regression from 26.3.  I'd expect it to keep working.
>
> Please restore the functionality so that i can automatically strip
> privacy-sensitive headers when forwarding.

Iʼve compared emacs-26 and emacs-27, and the code is the same, which
leads me to suspect something different in your
configuration. 'message-forward-ignored-headers' is applied even when
forwarding as MIME (despite the docstring), except when
'message-forward-show-mml' is nil, or when itʼs 'best' and the
forwarded message is either signed or encrypted. Or maybe youʼre
forwarding from inside the *Article* buffer, I think Gnus behaves
differently then.

Robert





  reply	other threads:[~2021-01-05 13:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 17:12 bug#45631: 27.1; regression: message-forward-ignored-headers no longer applies when forwarding as MIME Daniel Kahn Gillmor
2021-01-05 13:06 ` Robert Pluim [this message]
2021-01-05 23:25   ` Daniel Kahn Gillmor
2021-01-06 10:31     ` Robert Pluim
2021-01-10 15:18       ` Lars Ingebrigtsen
2021-01-10 17:25         ` Eli Zaretskii
2021-01-11 15:04           ` Lars Ingebrigtsen
2021-01-10 21:41         ` Daniel Kahn Gillmor
2021-01-11 15:09           ` Lars Ingebrigtsen
2021-01-12 14:57             ` Daniel Kahn Gillmor
2021-01-13  9:25               ` Robert Pluim
2021-01-13 17:35                 ` Daniel Kahn Gillmor
2021-01-18 15:50               ` Lars Ingebrigtsen
2021-01-18 17:43                 ` Daniel Kahn Gillmor
2021-01-19  3:12                   ` Lars Ingebrigtsen
2021-01-19 16:19                     ` Daniel Kahn Gillmor
2021-01-20 16:17                       ` Lars Ingebrigtsen
2021-01-20 19:31                         ` Daniel Kahn Gillmor
2021-01-21 15:46                           ` Lars Ingebrigtsen

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=87y2h71qj5.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=45631@debbugs.gnu.org \
    --cc=dkg@fifthhorseman.net \
    /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).