GNU bug report logs - #45631
27.1; regression: message-forward-ignored-headers no longer applies when forwarding as MIME

Previous Next

Package: emacs;

Reported by: Daniel Kahn Gillmor <dkg <at> fifthhorseman.net>

Date: Sun, 3 Jan 2021 17:13:01 UTC

Severity: normal

Tags: fixed

Found in version 27.1

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #52 received at 45631 <at> debbugs.gnu.org (full text, mbox):

From: Daniel Kahn Gillmor <dkg <at> fifthhorseman.net>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: Robert Pluim <rpluim <at> gmail.com>, 45631 <at> debbugs.gnu.org
Subject: Re: bug#45631: 27.1; regression: message-forward-ignored-headers no
 longer applies when forwarding as MIME
Date: Mon, 18 Jan 2021 12:43:22 -0500
[Message part 1 (text/plain, inline)]
I'm getting a little confused here, so i'm going to back up and try to
simplify.  There are two distinct (yet somehow overlapping) variables:

 - message-forward-included-headers (an "allowlist")
 - message-forward-ignored-headers (a "blocklist")

Can we agree on that?

Either or both (or neither) of these variables might be applied in any
of the three scenarios.  If both are applied, i have no idea which order
they are applied in, so applying both is probably not a great idea. ☹

The simplest approach would be the following:

On Mon 2021-01-18 16:50:10 +0100, Lars Ingebrigtsen wrote:
> 1) Forward as non-MIME

apply the allowlist.

> 2) MIME, but `message-forward-show-mml'

apply the blocklist.

> 3) MIME, but not `message-forward-show-mml'

apply the blocklist.

What are the downsides to approaching it this way?

     --dkg
[signature.asc (application/pgp-signature, inline)]

This bug report was last modified 4 years and 118 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.