Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id SAA05803; Mon, 14 Oct 1996 18:58:36 -0400 Received: by CS.UTK.EDU (bulk_mailer v1.7); Mon, 14 Oct 1996 18:58:15 -0400 Received: from SEARN.SUNET.SE (searn.sunet.se [192.36.125.4]) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id SAA05744; Mon, 14 Oct 1996 18:58:10 -0400 Message-Id: <199610142258.SAA05744@CS.UTK.EDU> Received: from SEARN.SUNET.SE by SEARN.SUNET.SE (IBM VM SMTP V2R3) with BSMTP id 4810; Tue, 15 Oct 96 00:55:16 +0200 Received: from SEARN.SUNET.SE (NJE origin ERIC@SEARN) by SEARN.SUNET.SE (LMail V1.2b/1.8b) with RFC822 id 0281; Tue, 15 Oct 1996 00:55:16 +0200 Date: Tue, 15 Oct 1996 00:37:06 +0200 From: Eric Thomas Subject: Re: CNAME/1123 breakage To: drums@cs.utk.edu In-Reply-To: Message of Mon, 14 Oct 1996 13:10:33 -0700 (PDT) from Mark Crispin I don't understand. What EXACTLY is going to break if we require all SMTP servers to handle a RCPT TO: that contains a CNAME, which all major implementations are already doing today? I can certainly see an improvement in robustness with this requirement, and a problem if we don't require it. Basically I'm fed up with this discussion, which is going nowhere due to many of the participants being more interested in looking at history books and pontificating about what they think is the One And Only Valid Use of CNAME than in actually solving real life problems. This group is a waste of my time and I'm just going to sign off. Wake me up when Gates has taken over the IETF and there is some hope for discussions centered on problem-solving in the real world. Meanwhile I have some productive work that needs to be done. Bye. Eric