Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Cc: ding@gnus.org
Subject: Re: Mail-Followup-To interaction with gnus-summary-followup
Date: 11 Feb 2001 14:38:49 -0500	[thread overview]
Message-ID: <m38zndc8m8.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: Paul J Collins's message of "11 Feb 2001 14:42:22 +0000"

Paul J Collins <sneakums@sto-kerrig.org> writes:
> I'm unsure of the semantics of Mail-Followup-To,

<URL:http://cr.yp.to/proto/replyto.html>

> I'm on a mailing list that I filter into a separate group, and one of
> the posters has a Mail-Followup-To header with the list's address in
> it.  I had already set the group's parameters for to-list and
> to-address to the address of list.

I think having to-address makes to-list unnecessary.

> When I type `f' to follow up to this person's posts, my new message is
> given a To field with the value of to-address, and a Cc field with the
> value of the original poster's Mail-Followup-To.

What is the value of message-use-followup-to?

> I want to disable this behaviour.  Honouring Mail-Followup-To in the
> case where the mail is already going to that address doesn't make
> much sense to me.

I think to-address is intended for a world without Mail-Followup-To,
and vice versa.  If the message you're following up to already tells
you where the followup should go, you don't need to-address.  Since
you can edit the addresses in the message either way, I think it's
best to prefer Mail-Followup-To (per-message, more specific) over
to-address (per-group, more general).  So message.el should be changed
around 19 lines into message-get-reply-headers:
    (if (or (not wide)
	    to-address)
should be:
    (if (and (not mft)
             (or (not wide)
                 to-address))

You can blame me for this, BTW.  I wrote the MFT code, but didn't
quite understand to-address at the time, I guess.


paul



  parent reply	other threads:[~2001-02-11 19:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-11 14:42 Paul J Collins
2001-02-11 15:02 ` ShengHuo ZHU
2001-02-11 15:12   ` Peter Makholm
2001-02-11 15:38   ` Paul J Collins
2001-02-11 18:05 ` Kai Großjohann
2001-02-11 19:38 ` Paul Jarc [this message]
2001-02-16 19:51   ` Paul J Collins
2001-02-17 20:34     ` Paul Jarc
2001-02-17 21:03       ` ShengHuo ZHU
2001-02-18  0:50         ` Paul J Collins
2001-02-18 15:38           ` Per Abrahamsen
2001-02-18 17:06         ` Paul J Collins
2001-02-18 23:14           ` Paul Jarc
2001-02-19  1:14             ` ShengHuo ZHU
2001-02-23 19:50             ` Paul J Collins
2001-02-11 14:49 Paul J Collins

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=m38zndc8m8.fsf@multivac.student.cwru.edu \
    --to=prj@po.cwru.edu \
    --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).