Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Mail-{Followup,Reply}-To
Date: 25 Oct 2000 14:27:30 +0200	[thread overview]
Message-ID: <rj66mht8b1.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <m34s21ama1.fsf@multivac.student.cwru.edu>

prj@po.cwru.edu (Paul Jarc) writes:

> Per Abrahamsen <abraham@dina.kvl.dk> writes:
> > I don't think it would be hard to teach message.el to obey the two
> > headers.  It could also generate the two headers based on group
> > parameters.  If "broken-reply-to" is set, generate "mail-reply-to".
> 
> Is broken-reply-to currently used for anything?  I wonder if this
> should be handled separately.

Yes, it mean ignore the "Reply-to" field for messages in this folder.
It is intended for mailing lists who insert the list address in the
reply-to field.  Which happen to be the exact same lists where is
makes sense to create a Mail-Reply_to header.

So I don't think these should be handled separately.



  parent reply	other threads:[~2000-10-25 12:27 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       ` Per Abrahamsen [this message]
2000-10-27 15:30   ` Mail-{Followup,Reply}-To Paul Jarc
2000-10-27 16:00     ` Mail-{Followup,Reply}-To Paul Jarc
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=rj66mht8b1.fsf@ssv2.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).