Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <>
Subject: Re: mail/post forwarding now has an option to forward all original headers
Date: Wed, 13 Dec 2023 12:41:16 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Emanuel Berg's message of "Tue, 12 Dec 2023 19:37:07 +0100")

Emanuel Berg <> writes:

> Eric Abrahamsen wrote:
>> Just FYI, I've just added a symblic-prefix option ('a) to
>> `gnus-summary-mail-forward' and `gnus-summary-post-forward',
>> which temporarily sets `message-forward-included-headers'
>> to nil.
> Maybe related,
> People have sometimes been annoyed I don't keep the e-mails in
> a CC when I reply on mailing lists, I have never understood
> why this doesn't happen. Like in this case, I suppose these
>   <eric@ ... net>
>   <ding@ ... org>
> should appear in the CC? But the only headers I see after
> `gnus-article-followup-with-original' are
> Newsgroups: gmane.emacs.gnus.general
> Subject: Re: mail/post forwarding now has an option to forward all original headers
> To: 
> From: Emanuel Berg <incal@ ... org>
> Gcc: nnml:mail.sent
> I have `message-forward-ignored-headers' at its original
> value, and also tried `message-forward-included-headers' both
> at its original value and now nil, inspired by this post.

This has to do with replies, not forwarding. This stuff is governed by
the "wideness" of the reply, not the headers. The "wider" you make the
replies/followups (see the names of the commands), the more addresses
will get included into the outgoing reply.

  reply	other threads:[~2023-12-13 20:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 18:05 Eric Abrahamsen
2023-12-12 18:37 ` Emanuel Berg
2023-12-13 20:41   ` Eric Abrahamsen [this message]
2023-12-14 10:45     ` Emanuel Berg
2023-12-15  1:42       ` Eric Abrahamsen
2023-12-17 17:19         ` Emanuel Berg
2023-12-14 13:09   ` Eric S Fraga

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).