Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id MAA12841; Sat, 5 Jul 1997 12:54:25 -0400 Received: by CS.UTK.EDU (bulk_mailer v1.7); Sat, 5 Jul 1997 12:52:12 -0400 Received: by CS.UTK.EDU (cf v2.9s-UTK) id MAA12718; Sat, 5 Jul 1997 12:52:11 -0400 Received: from spot.cs.utk.edu (SPOT.CS.UTK.EDU [128.169.92.189]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id MAA12707; Sat, 5 Jul 1997 12:52:07 -0400 Received: from cs.utk.edu by spot.cs.utk.edu with ESMTP (cf v2.11c-UTK) id MAA18986; Sat, 5 Jul 1997 12:51:57 -0400 (EDT) Message-Id: <199707051651.MAA18986@spot.cs.utk.edu> X-Mailer: exmh version 2.0gamma 1/27/96 X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: "Jeff Stephenson" cc: "John C Klensin" , drums@cs.utk.edu, moore@cs.utk.edu Subject: Re: Sizes in draft-ietf-drums-smtpupd05.txt In-reply-to: Your message of "Thu, 03 Jul 1997 10:20:56 PDT." <199707031724.NAA21375@CS.UTK.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Jul 1997 12:51:56 -0400 Sender: moore@cs.utk.edu > Given the concern we all share about the consequences of raising the > limits, I think that 821bis should leave them as is but point out the > problem. Then we write an SMTP extension which either increases the limits > to something more reasonable or removes them entirely and details how > servers interact when there are no fixed limits. I'm not sure what the SMTP extension would buy us. What is the client MTA going to do (other than bounce the mail) if the EHLO result reveals that the server MTA won't accept a recipient address? If the server returns "5xx recipient address too long", all clients (not just those that support the SMTP extension) will do the right thing. 821bis could require that 821bis-compliant SMTPs support larger addresses than was required by 821, but it should also warn implementors about the smaller minimums in 821. Keith