Received: from localhost (daemon@localhost) 
        by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id PAA20826; Mon, 21 Apr 1997 15:03:35 -0400
Received: by CS.UTK.EDU (bulk_mailer v1.7); Mon, 21 Apr 1997 14:57:38 -0400
Received:  
        by CS.UTK.EDU (cf v2.9s-UTK)
	id OAA20147; Mon, 21 Apr 1997 14:57:36 -0400
Received: from koobera.math.uic.edu (qmailr@koobera.math.uic.edu [128.248.178.247]) 
        by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id OAA20137; Mon, 21 Apr 1997 14:57:31 -0400
Received: (qmail 18016 invoked by uid 666); 21 Apr 1997 19:04:52 -0000
Date: 21 Apr 1997 19:04:52 -0000
Message-ID: <19970421190452.18015.qmail@koobera.math.uic.edu>
From: "D. J. Bernstein" <djb@koobera.math.uic.edu>
To: drums@cs.utk.edu
Subject: Re: How Reply SHOULD Work

It is inexcusable for DRUMS to impose constraints on user interfaces.

> 1. Start by using Reply-To:, or, if that's missing, From:.

That's fine for reply-to-author. For followups I want something
completely different.

> 2. Offer to include the contents of any other mailbox-containing header
>    field.

Interactively? Ugh.

Yes, I want to see the entire message I'm responding to, including all
header fields. But many users don't.

Yes, I insist on being able to edit the entire message I'm sending,
including all header fields. But many users are satisfied for years with
nothing more than ``reply'' and ``followup.''

Yes, I'd like a convenient shortcut for pulling addresses out of the
original message. But I certainly don't want to suffer through _your_
favorite interface for this.

---Dan
Let your users manage their own mailing lists. http://pobox.com/~djb/qmail.html