From: Lars Ingebrigtsen <larsi@gnus.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: ding@gnus.org
Subject: Re: customize TO in group, gnus-summary-followup-with-original does not work
Date: Thu, 26 Dec 2013 17:22:45 +0100 [thread overview]
Message-ID: <87d2kjfup6.fsf@building.gnus.org> (raw)
In-Reply-To: <87iov8lyb2.fsf@mat.ucm.es> (Uwe Brauer's message of "Sun, 01 Dec 2013 10:23:29 +0100")
Uwe Brauer <oub@mat.ucm.es> writes:
> I receive emails from somebody, who uses two different email address E1
> and E2 two say. I only posses a public key for address E1.
>
> So I set the TO: field in the gnus-group-customize buffer, to the
> address E1. So whenever I receive email from E1 or E2, I always reply to
> E1.
>
> However when I receive and email from E2 with CC and use
> gnus-summary-followup-with-original, then the other addresses are
> *ignored*!
> Is this a bug or did I miss something in the set up?
Does `S W' do the right thing, or does it do the same thing as `F'?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2013-12-26 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 9:23 Uwe Brauer
2013-12-26 16:22 ` Lars Ingebrigtsen [this message]
2013-12-26 17:00 ` Uwe Brauer
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=87d2kjfup6.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=oub@mat.ucm.es \
/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).