Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: MFT on nntp (was: PGP/GPG and AOL)
Date: Wed, 28 Nov 2001 15:26:30 -0500	[thread overview]
Message-ID: <m3adx6myk3.fsf_-_@multivac.cwru.edu> (raw)
In-Reply-To: <86vgfuk69n.fsf@duchess.twilley.org> (Jack Twilley's message of "Wed, 28 Nov 2001 12:08:36 -0800")

Jack Twilley <jmt+usenet@twilley.org> wrote:
> I read ding gnus from quimby.  What do I need to do to add whatever
> header is necessary to keep folks from emailing responses to the
> ding list and to me?  I feel at a loss -- I don't know if I need
> "Mail-Followup-To: never" or what, let alone where to fix gnus to
> automatically stick it in with each ding message.

ITYM "Mail-Copies-To: never".  You could add that to
message-default-headers or your posting style.  That would probably be
the safest thing.  Getting MFT right in this case would be harder;
getting it *almost* right would be easy, but, well, not right.  Since
practically eveybody here uses Gnus, MCT ought to be enough.


paul



  reply	other threads:[~2001-11-28 20:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 22:37 PGP/GPG and AOL Jack Twilley
2001-11-22 15:56 ` Simon Josefsson
2001-11-27 20:09   ` Jack Twilley
2001-11-28 13:08     ` Simon Josefsson
2001-11-28 20:08       ` Jack Twilley
2001-11-28 20:26         ` Paul Jarc [this message]
2001-11-28 21:55           ` MFT on nntp (was: PGP/GPG and AOL) Matt Christian
2001-11-29  8:28           ` Kai Großjohann
2001-11-29 17:19             ` Paul Jarc
2001-11-30  8:36               ` Kai Großjohann
2001-11-30 15:31                 ` Josh Huber
2001-11-30 17:15                   ` Paul Jarc
2001-11-28 20:54         ` PGP/GPG and AOL Simon Josefsson
2001-11-28 21:39           ` Jack Twilley
2001-11-29  8:31           ` Kai Großjohann
2001-11-29 10:33             ` Simon Josefsson

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=m3adx6myk3.fsf_-_@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).