Idea how to leave double-mails out?

Anthony E. Greene agreene@pobox.com
Thu Jun 6 04:03:02 2002


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05-Jun-2002/18:03 -0500, David T-G <davidtg-gnupg@justpickone.org> wrote:
>I don't know about the sig bit, but the Mail-Followup-To: header tells
>your MUA where you want followup email, as compared to direct reply
>email, to go.  Most folks subscribed to a list would set M-F-T: to the
>list while leaving Reply-To: set to themselves so that a "reply" would go
>to the poster and a "list reply" would go to the mailing list.  That
>sounds about like a "reply all" and some editing.

The M-F-T header was published as a recommendation in 1997 and expired in
1998. It was not included in RFC2822.

It might be a useful header if it was part of the spec and could therefore
become reliably supported by mail clients. But it's not and it isn't.

On a discussion list where the answers to questions are an integral part
of the list's function, setting Reply-To to the list address is entirely
appropriate. I've heard all the arguments and on a list where the majority
of the replies will be intended for the list, the list software should set
the Reply-To.

But I've gotten tired of debating this, so I set my procmail filters to
set a Reply-To for those lists where I think it's appropriate. So I just
use the Reply function of whatever mailer I'm using and the reply goes to
the list, as I almost always intend. On the exceptional occasion when I
want to reply off-list, I copy/paste the author's address. That's the
easiest way to do it and it works more than 90% of the time.


Tony
- -- 
Anthony E. Greene <mailto:agreene@pobox.com>
OpenPGP Key: 0x6C94239D/7B3D BD7D 7D91 1B44 BA26 C484 A42A 60DD 6C94 239D
AOL/Yahoo Chat: TonyG05         HomePage: <http://www.pobox.com/~agreene/>
Linux. The choice of a GNU generation <http://www.linux.org/>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Anthony E. Greene <mailto:agreene@pobox.com> 0x6C94239D

iD8DBQE8/sLopCpg3WyUI50RAmURAKDMh5IlfHQdoKvydkoa0zm7U+LmdACgz1RU
XuIJrFmGV/v4hCgpNIYGzs0=
=2oRV
-----END PGP SIGNATURE-----