Mail-Followup-To

[Ben Finney]

--oj4kGyHlBMXGt3Le
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 01-Jul-2003, Xavier Nodet wrote:
> On Tue, 01 Jul 2003 16:15:05 +0200 Werner Koch <wk@gnupg.org> wrote:
> > If you want to avoid getting extra copies, set your MFT
> > (Mail-Followup-To) header to the list name for the first posting.
>=20
> Why not simply using Reply-To? Stating the sender's preferences for
> where the replies should go seems to me exactly what this header is
> for (this list does not add Reply-To headers, fortunately)...

Mail-Followup-To targets "followups" intended to be read by all the
original recipients as well.  Reply-To targets "replies" directly to the
author.

E.g., if I wanted replies directly to me to be addressed to
"bignose@example.org", and I wasn't subscribed to the list, I might set
the following headers:

    Reply-To: bignose@example.org
    Mail-Followup-To: gnupg-users@gnupg.org, bignose@example.org

On the other hand, if I *was* subscribed to the list:

    Reply-To: bignose@example.org
    Mail-Followup-To: gnupg-users@gnupg.org

In both instances, the Reply-To and Mail-Followup-To headers should be
set differently to each other.  They serve discrete purposes.  (And, as
you point out, neither should be set by the list software, since that
would deny their use to the author of the message.)

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

--=20
 \     "For every complex problem, there is a solution that is simple, |
  `\                            neat, and wrong."  -- Henry L. Mencken |
_o__)                                                                  |
bignose@zip.com.au  F'print 9CFE12B0 791A4267 887F520C B7AC2E51 BD41714B

--oj4kGyHlBMXGt3Le
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iEYEARECAAYFAj8CJJMACgkQt6wuUb1BcUtaWACggvDLxck17HxW/oekzHweMZMm
eKkAmwbdJ/MB76XC3I6ufHZzCF0dWFuV
=EY/Z
-----END PGP SIGNATURE-----

--oj4kGyHlBMXGt3Le--