From: Bastien <bzg@altern.org>
To: info-gnus-english@gnu.org
Subject: Re: where does the * key store message to?
Date: Wed, 05 Dec 2007 21:26:51 +0000 [thread overview]
Message-ID: <87ve7c7rz8.fsf@bzg.ath.cx> (raw)
In-Reply-To: <v9ir3duet0.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 05 Dec 2007 20:22:51 +0100")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> [ @Bastien: please don't _silently_ redirect message from here to
> ding. ]
Sorry for that. Both info-gnus-english@ and ding@ arrive in a single
group having these parameters:
(to-address . "ding@gnus.org")
(to-list . "ding@gnus.org")
I wasn't clearly aware that `F' (gnus-summary-followup-with-original)
will send the reply to the `to-list' address rather than to the email
in the "To:" header.
Replying with `S W' is okay, though.
Does anyone store two mailing lists in a single group and have set the
parameters to handle only one of these two mailing lists, and does the
same mistake of replying with `F' instead of `S W' ?
Any advice of a better config?
Thanks,
--
Bastien
prev parent reply other threads:[~2007-12-05 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 10:15 David Rod
2007-12-05 19:22 ` Reiner Steib
2007-12-05 21:26 ` Bastien [this message]
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=87ve7c7rz8.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=info-gnus-english@gnu.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).