From: Malcolm Purvis <malcolmp@xemacs.org>
To: ding@gnus.org
Subject: Re: the trinity mailing list and problems with followups
Date: Thu, 13 Nov 2014 08:33:07 +1100 [thread overview]
Message-ID: <m2vbmk3y0c.fsf@xemacs.org> (raw)
In-Reply-To: <8761elmodz.fsf@mat.ucm.es> (Uwe Brauer's message of "Tue, 11 Nov 2014 22:13:44 +0100")
>>>>> "Uwe" == Uwe Brauer <oub@mat.ucm.es> writes:
Uwe> So when I use gnus-summary-followup-with-original the message is
Uwe> sent to the author and CC to the list, and some people complained,
Uwe> they want just mails sent to the mailing list.
The group parameters 'to-address', 'to-list' and 'subscribed' control
which addresses are used when you reply to. For example, for ding I
have the following group parameters.
("ding-gnus"
(to-address . "ding@gnus.org")
(to-list . "ding@gnus.org")
(subscribed . t)
(total-expire . t)
(expiry-target . delete)
)
Malcolm
--
Malcolm Purvis <malcolmp@xemacs.org>
next prev parent reply other threads:[~2014-11-12 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 21:13 Uwe Brauer
2014-11-12 12:29 ` Leonidas Tsampros
2014-11-12 14:04 ` Eric S Fraga
2014-11-12 21:33 ` Malcolm Purvis [this message]
2014-11-13 8:37 ` 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=m2vbmk3y0c.fsf@xemacs.org \
--to=malcolmp@xemacs.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).