From: "Charles Phlip Chan" <cpchan@sympatico.ca>
Subject: Re: followup to mailing lists?
Date: Thu, 08 Apr 2004 05:41:03 -0400 [thread overview]
Message-ID: <m3n05mbyds.fsf@MagnumOpus.khem> (raw)
In-Reply-To: <87d66q41kd.fsf@ursine.ca>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
On 2 Apr 2004, baloo@ursine.ca wrote:
> How do I make GNUS follow up to a mailing list with F but not CC the
> person?
You will need to split the mail into a group and setup group
perameters. For example:
((to-address . "mailiglist_address.com")
(to-list . "mailinglist_address.com")
(subscribed . t))
Charles
--
"All language designers are arrogant. Goes with the territory..."
(By Larry Wall)
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2004-04-08 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 19:33 Paul Johnson
2004-04-08 9:41 ` Charles Phlip Chan [this message]
[not found] ` <87wu4o4czo.fsf@ursine.ca>
2004-04-10 16:02 ` David Z Maze
2004-04-11 4:04 ` Paul Johnson
[not found] ` <m33c7ajdcd.fsf@MagnumOpus.khem>
2004-04-12 1:40 ` Paul Johnson
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=m3n05mbyds.fsf@MagnumOpus.khem \
--to=cpchan@sympatico.ca \
/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).