Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Mail-{Followup,Reply}-To
Date: 27 Oct 2000 12:00:09 -0400	[thread overview]
Message-ID: <m3lmva1dgg.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: prj@po.cwru.edu's message of "27 Oct 2000 11:30:40 -0400"

A news followup to a message without a Followup-To goes to the same
newsgroups as the previous message.  This is usually what the poster
wants, so Followup-To is usually not set.  But for mail, without MFT,
a followup goes to the poster as well.  This is usually not what the
poster wants, so MFT will be set more often than FT.  So I think
obedience of these fields should be controlled by separate variables.
(I made MFT obedience depend on message-use-followup-to.)  To be sort
of parallel with that variable, I'm thinking something like:
message-use-mail-followup-to
  nil  always ignore MFT
  use  always use MFT
  ask  always ask
  t    use MFT if it matches To+Cc (not To+Cc+From), otherwise ask
Sound good?  I think the default should be t.


paul



  reply	other threads:[~2000-10-27 16:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-23 20:54 Mail-{Followup,Reply}-To Paul Jarc
2000-10-24  9:52 ` Mail-{Followup,Reply}-To Kai Großjohann
2000-10-24 12:45   ` Mail-{Followup,Reply}-To Per Abrahamsen
2000-10-24 13:52     ` Mail-{Followup,Reply}-To Paul Jarc
2000-10-24 17:42       ` Mail-{Followup,Reply}-To Per Abrahamsen
2000-10-24 22:48     ` Mail-{Followup,Reply}-To Paul Jarc
2000-10-25  9:16       ` Mail-{Followup,Reply}-To Kai Großjohann
2000-10-25 12:27       ` Mail-{Followup,Reply}-To Per Abrahamsen
2000-10-27 15:30   ` Mail-{Followup,Reply}-To Paul Jarc
2000-10-27 16:00     ` Paul Jarc [this message]
2000-10-28 10:06       ` Mail-{Followup,Reply}-To Per Abrahamsen
2000-11-03 15:42       ` Mail-{Followup,Reply}-To Toby Speight
2000-11-03 17:12         ` Mail-{Followup,Reply}-To Paul Jarc

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=m3lmva1dgg.fsf@multivac.student.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).