Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id BAA07496; Wed, 29 Oct 1997 01:40:30 -0500 (EST) Received: by CS.UTK.EDU (bulk_mailer v1.7); Wed, 29 Oct 1997 01:38:33 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id BAA07382; Wed, 29 Oct 1997 01:38:32 -0500 (EST) Received: from CU.NIH.GOV (cu.nih.gov [128.231.160.111]) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id BAA07368; Wed, 29 Oct 1997 01:38:28 -0500 (EST) Message-Id: <199710290638.BAA07368@CS.UTK.EDU> To: kaih@khms.westfalen.de cc: drums@cs.utk.edu From: "Roger Fajman" Date: Wed, 29 Oct 1997 01:33:49 EST Subject: Re: Isolating one big problem. > (1) It is not yet clear that Group-Reply-To: is the right solution here. > It may be, but I think this needs more thought. Yes. > (2) The new solution will have to live alongside the old solution for > quite some time, while list servers and UAs slowly begin to implement the > new solution and, even more slowly, are being deployed. Absolutely. > Personally, I'm beginning to think the right solution may well be to > deprecate Reply-To: and do a new header for every Reply-To: function that > we want to support. > > That way, people can keep doing whatever they have been doing with Reply- > To: until the new solution is deployed, without sabotaging it in the > meantime, because that's what they _will_ do. > > MfG Kai I agree. I don't see how any other way could work.