Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: ding@gnus.org
Subject: Re: mail/post forwarding now has an option to forward all original headers
Date: Sun, 17 Dec 2023 18:19:05 +0100	[thread overview]
Message-ID: <87jzpcn3w6.fsf@dataswamp.org> (raw)
In-Reply-To: <8734w4gs11.fsf@ericabrahamsen.net>

Eric Abrahamsen wrote:

>> I use `gnus-article-followup-with-original', should you use
>> something else?
>
> When you reply via newsgroup posting (which is implied by
> the "followup"), then headers don't come into play, only the
> "newsgroups" header, and the message is sent via NNTP to
> those groups. There's no CC to anybody else.

Ah, that's the reason, mystery solved.

> If you reply via mail, then you will send an email to
> everyone in the To/CC/BCC headers, and there's where you'll
> see commands with "reply" and "(very) wide" in the name.
>
> It only gets a bit confusing because if you reply to an
> article that originally arrived via NNTP, often the email
> goes to an email address that can transport the message over
> to the NNTP newsgroup, so it looks like you did both
> a followup (to the group) and a reply (to individual
> posters). The whole thing gets a little strange.

Yes, I put it there manually this time. I don't do
that usually.

Now that this little issue makes sense, I don't think there is
a need to do anything about it. Let it be.

-- 
underground experts united
https://dataswamp.org/~incal



  reply	other threads:[~2023-12-18 20:02 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
2023-12-14 10:45     ` Emanuel Berg
2023-12-15  1:42       ` Eric Abrahamsen
2023-12-17 17:19         ` Emanuel Berg [this message]
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:
  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=87jzpcn3w6.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --cc=ding@gnus.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.
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).