Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: to-address and F and a?
Date: Thu, 18 Oct 2001 11:13:19 -0700	[thread overview]
Message-ID: <m1d73klsu8.fsf@reader.newsguy.com> (raw)
In-Reply-To: <vafwv1t2zdt.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Thu, 18 Oct 2001 09:14:38 +0200")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Norman Walsh <ndw@nwalsh.com> writes:
>
>> I'm using Gnus 5.8.8. On many of my nnml groups, I've set the
>> (to-address) in the group properties. I find this very convenient for
>> standard replies and for creating new mail with 'a'.
>
> For `a', maybe to-list is better?  But then, `F' always sends a Cc to
> the author.  

On the `F' comment: Not when (to-address) is specified.

> . . . . . . . . . But OTOH, the author can turn off receiving Cc's by
> putting a Mail-Followups-To header in the message.

One safe guard I use to avoid sending to author when (to-address) is
not set is to set "(setq message-generate-headers-first t )" so at
least I get a shot at seeing an unintended Cc or other header while
still in the composition buffer.

You (OP) seem to want the reverse effect, but maybe seeing the headers
while still in composition buffer will help you too.



  reply	other threads:[~2001-10-18 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-17 20:37 Norman Walsh
2001-10-17 20:50 ` Nevin Kapur
2001-10-18  7:14 ` Kai Großjohann
2001-10-18 18:13   ` Harry Putnam [this message]
2001-10-18 21:11   ` Norman Walsh
2001-10-18 21:20     ` Paul Jarc
2001-10-19  9:07     ` Kai Großjohann

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=m1d73klsu8.fsf@reader.newsguy.com \
    --to=reader@newsguy.com \
    /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).